Block 1 - Google Calendar1
- Type / Role
- n8n-nodes-base.googleCalendar - googleCalendar
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
This workflow syncs multiple Notion databases to your Google Calendar. And it works both ways. What events are supported? Everything except recurring events. All day even...
n8n-nodes-base.googlecalendar, n8n-nodes-base.notion, n8n-nodes-base.noop, n8n-nodes-base.stickynote, n8n-nodes-base.if, n8n-nodes-base.splitinbatches, n8n-nodes-base.datetime, n8n-nodes-base.merge
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Solomon.
Original n8n.io sourceThis workflow syncs multiple Notion databases to your Google Calendar. And it works both ways.
Everything except recurring events.
All day events, multiple day events, start and end date… these are all supported.
You set them in Notion and they stay in sync with Google. And vice versa.
Notion doesn’t support recurring events yet.
So when you create a recurring event in Google, it will only consider the first date, ignoring future occurrences of the event.
Yes. You can have many Notion databases synced to one Google Calendar account.
You can see how to do it in the workflow instructions.
It is recommended that you create more calendars in your account, so that you can link each calendar to a different database in Notion. But that’s a choice.
Yes. When you update the event in Google or in Notion it syncs both ways.
Either by the name or by clicking the hyperlink in the event description that says: 👉 View in Notion.
Yes. When you create an event inside one of your calendars, the item is synced to the corresponding Notion database.
No. The event description will always be “View in Notion”. Even if you change it in Google Calendar it will be overwritten when you make a change to the Notion page.
🎉 When you buy this template you receive step-by-step instructions on how to set it up.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 127 workflow blocks. Download the JSON for the full node graph.
| Workflow | 2-way sync Notion and Google Calendar |
|---|---|
| Complexity | advanced |
| Nodes | 127 |
| Categories | Personal Productivity |
| Author | Solomon |
| Published | 19 Jul 2024 |
Use the JSON export at /data/workflows/2351/2351.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
This workflow syncs multiple Notion databases to your Google Calendar. And it works both ways. What events are supported? Everything except recurring events. All day even...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Personal Productivity use case.