Advanced sync settings
Fine-tune sync behavior with advanced configuration options
2sync provides advanced settings that control sync behavior beyond basic field mapping and filters. These settings let you preview changes before they happen, manage deletions, handle edge cases, and customize how your automation processes data.
What advanced settings are available?
Every setting is accessible from your automation's Sync Settings panel.
| Setting | What it does |
|---|---|
| Dry Run | Preview sync behavior without making changes |
| Allow Deletion | Control if deletions sync or just unsync items |
| Sync Existing | Include Notion items created before the automation |
| Ignore Linked | Skip items already connected to other automations |
| Bypass Halt | Override safety limits for large data changes |
| Include Notion Link | Add a link back to the Notion page in synced items |
| Reset Sync History | Start fresh for email syncs |
| Default Duration | Event length when Notion only has a start time |
How does each setting work?
Dry run
Runs a full sync cycle but does not write any changes. The activity log shows what would have been created, updated, or deleted. Use this when testing a new automation or after changing filters.
Run a Dry Run after every major configuration change. Review the activity log to confirm the automation behaves as expected before enabling real syncing.
Allow deletion
When disabled (default), deleting an item in one app only unsyncs it from the other. The item remains on both sides but the link is broken. When enabled, deletions propagate: delete in one app and the item is removed from both.
See Delete Behavior for full details.
Sync existing
By default, 2sync only syncs Notion items created after the automation is set up. Enabling this includes all existing items in the database that match your filters and time window.
Use case: You have a Notion database with 200 tasks and want them all pushed to Todoist when you create the automation.
Sync Existing processes items within your configured time window and filter conditions. Set your time window and filters first, then enable Sync Existing to avoid processing more items than intended.
Ignore linked
Skips Notion items that are already linked to another automation. This prevents the same Notion page from syncing to multiple destinations, which can cause conflicting updates.
Use case: You have one automation syncing to Google Calendar and another to Outlook Calendar. Enable this to prevent double-syncing.
Bypass halt
2sync pauses automatically when it detects a sync would delete more than half of your synced items. Bypass Halt overrides this safety check.
Only enable Bypass Halt when you have verified that the large-scale change is intentional. Disable it again after the operation completes.
Include Notion link
Adds a URL back to the Notion page in the external app item (e.g., in the event description or task notes). This makes it easy to jump from a calendar event to its Notion source.
Reset sync history
Available for email automations only. Clears the record of which emails have been synced, causing the next sync to re-process all emails within the time window. Useful if you changed your database structure and want to re-import.
Default duration
For calendar automations. When a Notion page has a start date but no end date, this setting defines how long the event lasts. The default is typically 30 minutes or 1 hour.
Use case: You create tasks in Notion with only a date. Default Duration ensures they appear as timed blocks on your calendar rather than all-day events.
Related
- Delete behavior for a deep dive on Allow Deletion and un-sync behavior
- Calendar invitations for controlling invitation sending during sync
- Default values for setting static values on new items
- Filters for controlling which items sync
- Activity logs for reviewing Dry Run results and sync history
FAQ
Should I always run a Dry Run first?
It is recommended for new automations or after significant configuration changes. For ongoing automations with minor tweaks, it is optional but still a good practice.
What is the difference between Allow Deletion and Unsync?
Unsync is the default behavior: items disconnect but remain in both apps. Allow Deletion makes it so deleting in one app removes from both. Unsync is safer; deletion is more convenient if you want synchronized cleanup.
Does Sync Existing process all items at once?
Yes, on the next sync cycle after enabling it. For large databases, this may take several cycles due to rate limits. All items within your time window and filter conditions are processed.
Can I change Default Duration after events are created?
Changing Default Duration only affects new events created going forward. Existing events keep their current duration. To update existing events, edit them in Notion with explicit end times.
What happens if I Reset Sync History?
All previously synced emails are re-evaluated on the next cycle. Emails already in your Notion database are matched and updated rather than duplicated, as long as the database structure has not changed significantly.
What sync settings are specific to Google Calendar?
Google Calendar automations include additional settings: syncing timeframe (how far back and ahead to look for events), default calendar event duration (used when a Notion item has only a start time), and guest invitation preferences (control when attendees receive calendar invitations). These appear in Sync Settings when editing a Google Calendar automation.