Overview
Scheduling lets your flows run automatically at regular intervals, so you do not have to trigger syncs manually. You can set up multiple scheduling rules, each controlling when and how often specific flows run.
You can find this page under Configure > Scheduling in the left sidebar.
Creating a scheduling rule
Click + Add scheduling rule to create a new rule. Each rule requires:
Action — select which flow this rule controls (e.g., an order export flow)
Schedule type — choose how the rule triggers:
- Time schedule — runs at a fixed interval (e.g., every 15 minutes, every hour, once daily) - Trigger after another job — runs automatically after another flow completes. This is useful for chaining flows, like exporting customers immediately after orders.
Interval — for time schedules, set how often the flow runs
After creating a rule, it appears in the Scheduling Settings list and starts running immediately.
Managing rules
Each scheduling rule in the list shows:
The flow it controls
The schedule type and interval
An on/off toggle
You can pause a rule by toggling it off. This stops the automatic syncing but preserves the rule configuration so you can re-enable it later.
To delete a rule, click the rule and use the delete option.
Common scheduling setups
Different data types typically benefit from different sync frequencies:
| Data type | Suggested interval | Reason | |---|---|---| | Orders | Every 15 minutes | Orders are time-sensitive and customers expect quick processing | | Products/Articles | Once or twice daily | Product data changes less frequently | | Stock/Inventory | Every 30–60 minutes | Balances between accuracy and API load | | Customers | Once daily | Customer records rarely change frequently | | Payouts | Once daily | Payment provider payouts are typically settled once per day |
These are suggestions — adjust based on your order volume and business needs.
Scheduling and webhooks
Scheduling and Webhooks are complementary approaches to triggering syncs:
Scheduling runs at fixed intervals regardless of whether anything has changed. It is reliable and predictable but may sync even when there is nothing new.
Webhooks trigger immediately when an event happens in the source platform (e.g., a new order is created). They are faster but depend on the platform supporting webhook events.
Many integrations use both: webhooks for time-sensitive data like orders, and scheduling as a safety net to catch anything webhooks might miss.
Tips
Start with longer intervals (e.g., every hour) and decrease them if you need faster syncing.
If you see high error rates after setting up scheduling, check the Logs page — the issue is likely a configuration problem rather than a scheduling problem.
Remember that each scheduled run counts toward your monthly transaction volume. Very frequent schedules on high-volume integrations will process more tasks.
If a flow is not syncing at all, verify that it has at least one active scheduling rule or webhook subscription.