sync-builder-skill

Incremental syncing in Nango captures only data changes since the last execution, whereas full syncing periodically retrieves all records. You configure this behavior using the syncType parameter within the createSync pattern, ensuring efficient data synchronization workflows based on your specific update frequency requirements.

When creating a Nango data integration sync, you need to define the description, endpoints, frequency, syncType, models, and execution logic. Explicit model schemas and versioned configurations are required alongside proper end-of-execution cleanup to prevent deprecated feature usage and ensure reliable data synchronization.

Nango handles deletion detection during periodic data synchronization by applying specific patterns within the createSync execution logic. This ensures that records removed from the source system are accurately identified and processed during both full and incremental syncs, maintaining data consistency across integrated systems.

Yes, you should invoke the integration-patterns-skill first to establish foundational integration patterns before configuring your Nango sync models. This ensures proper parameter naming, type safety, and lifecycle handling when you subsequently create a new sync using the createSync pattern with your defined endpoints.

You avoid deprecated features when setting up Nango sync workflows to ensure proper lifecycle handling and stable execution logic. Using current createSync patterns enforces explicit parameter naming and type safety, preventing sync failures and ensuring proper end-of-execution cleanup for reliable data synchronization.