Default asset configuration
Control where new Notion items go when syncing multiple calendars or lists
When an automation syncs multiple calendars, task lists, or projects, 2sync needs to know where new items created in Notion should go. The default asset setting designates one asset as the destination for new Notion items that do not specify a target. It is shown with a green chip on your dashboard.
What is a default asset?
An asset is a calendar, task list, project, or contact group connected to your automation. When you sync multiple assets (e.g., "Work" and "Personal" calendars), new Notion pages need a destination.
The default asset is the one that receives new items when no explicit destination is set.
When does the default asset apply?
The default asset 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 default asset.
How to set the default asset
- Open your automation
- Go to the Assets section
- Click on the asset you want as default
- Select Set as default
- A green chip appears next to the default asset
You can change the default at any time. The change applies to the next sync cycle.
If you do not set a default, 2sync uses the first available asset with write access. Setting an explicit default gives you predictable routing.
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) | Default asset |
| (unrecognized) | Default asset |
This gives you per-item control over routing while the default acts as a safety net.
What happens with read-only assets?
Some assets may be read-only (e.g., shared calendars where you only have view access). 2sync cannot write to read-only assets.
If all non-default assets are read-only, the default asset 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?
Always set an explicit default: Relying on the automatic first-asset fallback can lead to unexpected routing if you add 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
What happens if I remove the default asset?
2sync falls back to the first available asset with write access. Set a new default explicitly to avoid unexpected routing.
Can I have different defaults for different automations?
Yes. Each automation has its own default asset setting. Configure them independently based on each automation's purpose.
Does changing the default affect existing synced items?
No. Changing the default only affects where new Notion items are routed. Existing items remain linked to their current asset.
How do I know which asset is the default?
The default asset is marked with a green chip on your automation's asset list. If no green chip is visible, no explicit default is set and 2sync uses the first available asset.
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 defaults to the default asset. Verify that each project or calendar name in your mapping matches an entry in your automation's connected assets.