Default asset configuration
Control where new Notion items go when syncing multiple calendars or lists
When an automation syncs more than one calendar, task list, or project, two separate controls decide what happens to your items. A checkbox next to each row decides whether that calendar or list syncs at all. A green Default chip on one row decides where a new Notion item goes when nothing else says where it belongs.
This article is about the second one. The first section explains how to tell them apart, because most "my sync is broken" reports come down to selection, not the default.
Selection and default are two different things
Open your automation and expand the connections card for the provider (Calendar Connections, Todoist Connections, and so on). Every calendar, list, or folder from the connected account appears as a row with a checkbox.
- The checkbox decides what syncs. Only checked rows are part of the automation. If you uncheck everything, the automation has nothing to sync and stops with a "No asset is selected" error.
- Default decides where new Notion items go. It matters only when a new item created in Notion does not say which calendar or list it belongs to. It never breaks a sync on its own.
If nothing is syncing at all, check the checkboxes first. If items sync but land in the wrong calendar, that is routing, and the rest of this article covers it.
There is no section or field named "Default asset" in 2sync. On screen you see a green Default chip on one row and a small Set as default link on the others.
What is a default asset?
An asset is a calendar, task list, project, or contact group connected to your automation. When you sync several of them (e.g., "Work" and "Personal" calendars), new Notion pages need a destination.
The default is the asset that receives new items when no explicit destination is set.
When does the default asset apply?
The default is used when a new Notion page:
- Has no asset field mapped (e.g., no "Calendar" Select property)
- Has an empty asset field (the property exists but no value is selected)
- Has a value that does not match any connected asset name
In all three cases, 2sync routes the item to the asset carrying the Default chip.
How to set the default asset
- Open your automation
- Expand the connections card for the provider (for example Calendar Connections)
- Find the row for the calendar, list, or folder you want
- Click Set as default on that row
- The green Default chip moves to it
Clicking Set as default also ticks that row's checkbox if it was not ticked, because an asset cannot receive items unless it is syncing.
Changes save automatically a moment after you click. There is no Save button on the edit page. The new routing applies from the next sync cycle.
If you never set one, 2sync picks a default for you: your primary calendar or list when it is selected, otherwise the last row you checked. Setting it yourself gives you predictable routing.
Which integrations have a default?
Calendar, task, and contact integrations all show the chip and the link: Google Calendar, Outlook Calendar, Google Tasks, Todoist, Google Contacts, and Outlook Contacts.
Gmail and Outlook Mail do not. Those automations sync one way, from your mailbox into Notion, so nothing is ever created on the mail side and there is no destination to choose. If you are looking at a Gmail or Outlook Mail automation, the Default chip and the Set as default link are simply not there. The checkboxes still work as usual and still decide which labels or folders sync.
How to route items to specific assets
To control which asset each Notion page syncs to, map a Select property in your Notion database to the asset field. Each option in the Select dropdown should match an asset name.
| Notion select value | Destination |
|---|---|
| Work | Work calendar |
| Personal | Personal calendar |
| (empty) | Asset with the Default chip |
| (unrecognized) | Asset with the Default chip |
This gives you per-item control over routing while the default acts as a safety net.
What happens with read-only assets?
Some assets are read-only (e.g., shared calendars where you only have view access). 2sync cannot write to them, so those rows are tagged (Read only) and show neither the Default chip nor the Set as default link. You can still tick their checkbox to pull their items into Notion.
If all your other assets are read-only, the one carrying the Default chip must have write access. Otherwise, new items from Notion cannot be created in the external app.
If no asset has write access, new Notion items cannot sync to the external app. Ensure at least one connected asset allows write operations.
What are the best practices?
Check your selection first: Before touching the default, confirm the calendars and lists you expect to sync actually have their checkbox ticked. An empty selection stops the automation outright.
Set the default yourself: Relying on the automatic pick can lead to unexpected routing if you add, remove, or reorder assets.
Name assets clearly: Use descriptive names that match your Notion Select options exactly. "Work Calendar" in Google must match "Work Calendar" in the Notion dropdown.
Audit routing periodically: Check that new items are landing in the expected asset, especially after adding or removing calendars.
Related
- Sync multiple calendars for managing multiple calendars in one automation
- Default values for setting static values on new items
- Sync direction for understanding how direction affects new item creation
- Filters for controlling which items sync from each asset
FAQ
I was told to open the default asset setting and I cannot find it. Where is it?
There is no setting by that name. Open your automation, expand the connections card for the provider, and look at the asset rows: one carries a green Default chip and the others show a Set as default link. That link is the control.
My sync stopped working. Will setting a default fix it?
Almost certainly not. The default only decides where new Notion items go, it never stops a sync. A sync that produces nothing usually means no asset is selected: check that at least one calendar or list has its checkbox ticked in the connections card.
What happens if I remove the default asset?
2sync picks one automatically: your primary calendar or list when it is selected, otherwise the last row you checked. Click Set as default on the asset you actually want to avoid unexpected routing.
Can I have different defaults for different automations?
Yes. Each automation keeps its own default. Configure them independently based on each automation's purpose.
Does changing the default affect existing synced items?
No. It only affects where new Notion items are routed. Existing items stay linked to their current asset.
How do I know which asset is the default?
It carries a green Default chip in the automation's asset list. If no chip is visible, no explicit default is set and 2sync picks one for you.
Why is there no Set as default link on my Gmail or Outlook Mail automation?
Those integrations sync one way, from your mailbox into Notion, so nothing is created on the mail side and there is no destination to pick. Neither the Default chip nor the Set as default link appears there. The checkboxes still control which labels or folders sync.
Do I need to save after changing the default?
No. The asset list saves on its own a moment after you click, and the edit page has no Save button. The new routing applies from the next sync cycle.
How do I set the default automation for a task or event in Notion?
When multiple automations share the same Notion database, new items created in Notion go to the default automation. To control this, use the Source property that 2sync adds to your database. Set a filter like 'Source is not [calendar name]' to route items to the correct automation.
Why are my events being automatically reassigned to a different project?
This happens when the Calendar Name or Project field is mapped to a value that does not exist in the automation's asset list. When the value is missing or blank, the event falls back to the asset carrying the Default chip. Verify that each project or calendar name in your mapping matches an entry in your automation's connected assets.