Schedule and trigger reverse ETL syncs
This guide explains how to schedule reverse ETL integrations and trigger syncs manually. For concepts, see Reverse ETL overview.
Where to Set the Trigger
Open the reverse ETL integration → Settings tab → Trigger type. You can change it at any time.
Trigger Types
- Manual: The integration does not run on a schedule. Start a sync only by clicking Sync now from the integration header or using an API call.
- By interval: Set a replication frequency (e.g. every 30 minutes, 6 hours, 24 hours). You can set a base time so the first run and subsequent runs align to a fixed time.
- Cron: Enter a cron expression for custom schedules (e.g. weekdays at 8 AM).
The same options are available for ETL integrations. Choose the option that matches when your source data is ready and when the destination needs updates.
Tip
Schedule reverse ETL to run after your dbt job so you sync transformed, business-ready data. If dbt Cloud is connected, you can trigger the integration when a dbt Cloud job completes (configure in the integration flow or Settings where supported).
Run a Sync Manually
- From the integrations table: Use the Sync button on the row, or open the integration and click Sync now in the header.
- From the integration details page: Click Sync now next to the header. Progress and results appear on the Status tab.
After a Sync
On the Status tab you see changed records (inserts, updates, deletes) and per-run breakdowns: Successful, Rejected (with API request/response for debugging), and Invalid (e.g. duplicate primary key). Use these to troubleshoot failed or invalid records.
For sync modes and destination behavior, see Sync modes and destinations.