How to use multiple automations on one database
Run multiple 2sync automations on the same Notion database. Prevent duplicates with filters and Ignore Linked, set up work and personal calendars, and merge multiple sources into one view
2sync lets you run multiple automations on the same Notion database to sync different calendars, task lists, or contact sources into one place. The key to avoiding duplicates is using filters and the Ignore Linked setting. This guide covers the strategies, filter patterns, and best practices that keep your data clean when multiple automations target the same database.
What is the problem with multiple automations?
When two or more automations point at the same Notion database without proper configuration, items can be processed by more than one automation. A calendar event might sync twice, a task might appear in duplicate, or an item created by one automation gets picked up by another.
This happens because each automation independently scans the database. Without filters, every automation sees every item.
How to prevent duplicates with filters and ignore linked
The solution combines two features: filters that give each automation a distinct scope, and the Ignore Linked setting that tells an automation to skip items already managed by another automation.
Step 1: Add a filtering property
Create a Notion Select property (e.g., "Type" or "Source") that categorizes each item. Set values like "Work", "Personal", or a specific calendar name.
Use a Select property rather than a Text property for filtering. Select properties prevent typos and guarantee consistent values, which is critical when filters must match exactly. You can also set a default value so new items created in Notion automatically get the right filter value.
Step 2: Configure non-overlapping filters
Each automation gets a filter matching only its own items.
| Automation | Filter | Logic |
|---|---|---|
| Work Calendar | Type equals "Work" | All conditions |
| Personal Calendar | Type equals "Personal" | All conditions |
| Shared Calendar | Type equals "Shared" | All conditions |
Step 3: Enable ignore linked
In each automation's settings, turn on Ignore Linked Items. This tells the automation to skip any Notion page already linked to a different automation.
What filter strategies are available?
| Strategy | Behavior | Best for |
|---|---|---|
| All conditions (AND) | Item must match every condition | Precise, narrow scope |
| Any condition (OR) | Item must match at least one condition | Broader inclusion |
| No filtering | Everything syncs | Single automation only |
Never run multiple automations on the same database without filters. This is the primary cause of duplicate items.
See Filters for the full reference on filter conditions, operators, and examples for each integration type.
How to sync work vs personal events
- Create a Notion Select property called "Type" with options "Work" and "Personal".
- Automation 1 (Work): Set a filter where Calendar Name equals your work calendar. Map Calendar Name to "Type" and set a default value of "Work".
- Automation 2 (Personal): Set a filter where Calendar Name equals your personal calendar. Map Calendar Name to "Type" and set a default value of "Personal".
- Enable Ignore Linked on both automations.
- New items created from Notion route to the correct calendar based on the Type property. Set a default asset to control which calendar receives items when no Type value is set.
For a full walkthrough, see Sync multiple calendars to one database.
How to merge multiple calendars into one database
- Connect each calendar account and create a separate automation for each calendar.
- Add a "Source Calendar" Select property in Notion and map each automation's Calendar Name to it.
- Enable Ignore Linked on every automation so they don't interfere with each other.
- Create Notion views filtered by Source Calendar to separate events visually while keeping them in one database.
For more details on this setup, see Sync multiple calendars and Default asset.
How to merge multiple task lists into one database
You can sync Todoist and Google Tasks, or multiple lists from the same app, into a single Notion database.
- Create a Select property called "Source" with values like "Todoist" and "Google Tasks" (or your list names).
- Set up a separate automation for each task source.
- Add a filter on each automation so it only manages items where Source matches its own value. Set a default value so new items from each source are tagged automatically.
- Enable Ignore Linked on every automation.
See the integration guides for Todoist and Google Tasks for field mapping details.
How to merge contacts from multiple sources
Combine Google Contacts and Outlook Contacts into one Notion CRM database.
- Create a Select property called "Source" with values like "Google" and "Outlook".
- Set up a separate automation for each contact source.
- Filter each automation by its Source value and set default values so new contacts are tagged on creation.
- Enable Ignore Linked on every automation.
See the integration guides for Google Contacts and Outlook Contacts for field mapping details.
What are the best practices?
- Always enable Ignore Linked on every automation sharing a database. Without it, automations can claim each other's items and create duplicates.
- Use Select properties for filter values: Select properties enforce consistent values and prevent the typos that break filter matching.
- Test with Dry Run before activating a new automation. Dry Run shows you what would sync without making changes, so you can catch filter mistakes early.
- Design non-overlapping filters so no item matches two automations. If a single item matches multiple automations, both will try to sync it.
- Plan for unmatched items: Items that match no filter sit in Notion without syncing. Decide whether that's acceptable or if you need a catch-all automation.
- Map Sync Status to a Notion property so you can see which items are Synced, Ignored, or Removed at a glance. See Sync item statuses for details.
How to handle existing data
Before adding a second automation to a database that already has synced items, ensure every existing item has a value for the filter property. Items with empty filter values may be picked up by the wrong automation or ignored entirely.
Always pause all automations before reconfiguring filters or adding new automations to a shared database. Changing filters while automations are running can cause items to be picked up by the wrong automation or missed entirely.
- Pause all automations
- Fill in the filter property for every existing row
- Configure filters on each automation
- Enable Ignore Linked on each automation
- Resume automations one at a time
How to troubleshoot common issues
Items appearing in multiple places: Filters overlap. Review each automation's filter conditions and ensure they are mutually exclusive.
Items not syncing at all: The item doesn't match any automation's filter. Check the filter property value and confirm it matches at least one automation.
Duplicate items after enabling filters: Existing items synced before filters were added may have created duplicates. Use Dry Run to identify them, then remove duplicates manually.
Map Sync Status to a Notion property to see whether each item is Synced, Ignored, or Removed. This makes it much easier to diagnose which automation owns an item and why it ended up in the wrong state.
What should I do next?
- Learn how filters work in detail
- Sync multiple calendars to one database
- Set default values for new items
- Set up a default calendar or list
Related
- Filters for the complete filtering reference with conditions and operators
- Sync multiple calendars for calendar-specific multi-source setup
- Default asset for choosing where new Notion items go
- Default values for setting automatic property values on new items
- Sync item statuses for monitoring which items sync, are ignored, or removed
- Delete behavior for understanding what happens when items are removed
- Set up team sync for shared workspace configurations
FAQ
Can I run unlimited automations on one database?
Yes, as long as each automation has distinct filters and Ignore Linked is enabled. The number of automations depends on your plan limit.
What does Ignore Linked actually do?
It tells an automation to skip any Notion page that is already linked to a different automation. This prevents one automation from overwriting or duplicating items managed by another.
Do I need filters if I only have one automation?
No. Filters are only necessary when multiple automations share the same database. A single automation can sync everything without filters.
What happens if an item matches no automation?
Items that don't match any filter remain in Notion but are not synced by any automation. They become orphaned unless you update their filter property.
Can I use Text properties instead of Select for filtering?
Technically yes, but Select properties are strongly recommended. They prevent typos and ensure consistent values, which is critical for reliable filtering.
Can I mix different integration types on one database?
Yes. You can sync Google Calendar and Outlook Calendar to the same database, or Google Contacts and Outlook Contacts. Each integration gets its own automation with its own filters. The key is non-overlapping filters and Ignore Linked enabled on all automations.
What if I add a new automation later?
Pause all existing automations first. Fill in the filter property value on every existing row so the new automation doesn't claim them. Configure filters on the new automation, enable Ignore Linked, then resume all automations one at a time.
Does Ignore Linked work across different integration types?
Yes. Ignore Linked works on any automation targeting the same Notion database, regardless of whether the source is Google Calendar, Todoist, Outlook Contacts, or any other supported app.