Quick start guide
Step-by-step guide to connect Notion with Google Calendar, Outlook, Todoist, or Google Tasks. Set up your first two-way sync in under 5 minutes.
Setting up 2sync takes under 5 minutes. In 5 steps, you'll connect your Notion database to Google Calendar, Outlook Calendar, Todoist, Google Tasks, Google Contacts, Outlook Contacts, Gmail, or Outlook Mail. You'll have a working two-way sync running automatically. This guide covers everything from connecting your accounts to activating your first automation.
Before you begin
To use 2sync, you need:
- A Notion account with at least one database
- An account with one of our supported services: Google Calendar, Google Tasks, Google Contacts, Gmail, Outlook Calendar, Outlook Contacts, Outlook Mail, or Todoist
- A 2sync account (sign up at app.2sync.com)
Not sure which integration to start with? Google Calendar ↔ Notion is our most popular sync and a great first automation.
Step 1: Connect your accounts
Before creating a sync, connect both your Notion account and your external service to 2sync.
- Go to the 2sync dashboard
- Click Connections in the left sidebar
- Click Add Connection
- Select your service (Google, Microsoft, or Todoist)
- Authorize 2sync to access your account (this uses secure OAuth, so your passwords are never shared with 2sync)
- Repeat for Notion, then select the databases you want to sync
When connecting Notion, you'll choose which databases 2sync can access. You can update this later from your Notion connection settings.
Step 2: Create a sync automation
Once your accounts are connected, you're ready to create your first sync.
- From the dashboard, click New Automation
- Select the integration type (e.g., Google Calendar)
- Choose your connected accounts
- Select a Notion database
- Select the specific calendar, task list, or contact group to sync with
Step 3: Map your fields
Field mapping tells 2sync how to match data between Notion and your external service. For example:
- Event Title ↔ Notion Name property
- Event Date ↔ Notion Date property
- Event Description ↔ Notion Notes property
For each field mapping, choose a sync direction:
- Two-way: changes sync in both directions
- One-way to Notion: only updates from the external service flow to Notion
- One-way to provider: only updates from Notion flow to the external service
Start with two-way sync on your most important fields (like title and date), then fine-tune after your first sync runs.
Step 4: Set filters (optional)
Filters let you control which items sync. You can add conditions like:
- Only sync events from a specific calendar
- Only sync tasks with high priority
- Only sync Notion items where Status is not "Archived"
Filters are optional, so skip them if you want everything to sync.
Step 5: Activate your sync
Review your settings and click Create. 2sync will:
- Run an initial sync to match existing items between both services
- Begin automatic syncing based on your plan's frequency (every 2-5 minutes)
- Log all sync activity in the Activity Log
Use the Sync Now button on your automation page to trigger an immediate sync, which is useful for verifying everything works before waiting for the next automatic cycle.
The first sync may take a few minutes depending on how many items are in your database. Subsequent syncs are faster since they only process changes.
What happens next
Once your sync is active:
- Changes sync automatically based on your plan's frequency, or use Sync Now for an immediate sync
- View sync history in the Activity Log on your automation page
- Edit your automation anytime to adjust field mappings, filters, or sync direction
- Pause or delete your sync from the automation settings
Troubleshooting
If your sync isn't working as expected:
- Check the Activity Log for error messages
- Verify your connections are still authorized (Connections page)
- Review field mappings to ensure properties are correctly matched
- Check filters to make sure they aren't excluding items you expect to sync
If you see authorization errors, disconnect and reconnect the affected service. For Notion, make sure the database is still shared with the 2sync integration.
Next steps
Now that your first sync is running:
- Sync Direction & Field Mapping: fine-tune how each field syncs between your apps
- Filters: control exactly which items sync with conditions
- Relation Databases: connect attendees to contacts, tasks to projects
- Shared Connections: let team members sync personal calendars to a shared Notion workspace
- Delete Behavior: control what happens when items are removed from one side
- Default Asset: when syncing multiple calendars, choose where new Notion items go
FAQ
How long does the first sync take?
The initial sync typically takes 1-5 minutes depending on the number of items in your database. After that, only changes are processed, so regular syncs are much faster.
Can I sync multiple calendars to one Notion database?
Yes! Create separate automations for each calendar pointing to the same Notion database. Use the Default Asset setting to control where new items created in Notion are added.
What happens if I edit the same item in both places?
2sync uses a last-write-wins approach. The most recent change takes priority. With sync intervals of 2-5 minutes, conflicts are rare in practice.
Will syncing delete my existing data?
No. 2sync matches existing items between services and keeps them in sync going forward. It won't delete items unless you specifically enable that in your delete behavior settings.
Can I change my field mappings after the first sync?
Yes, you can edit your automation's field mappings at any time. Changes apply to the next sync cycle.
Does Notion natively sync with Google Calendar?
Notion Calendar displays events as a visual overlay, but it doesn't create database pages or support two-way sync. 2sync creates full Notion database pages that sync both ways - edit in either app and changes reflect automatically.
Do I need coding skills to use 2sync?
No. 2sync is a no-code tool. Connect your accounts, configure your field mappings, and activate your sync - no scripts, APIs, or technical setup required.