Notion FINALLY Connects to Your Calendar
Based on Thomas Frank Explains's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
KRON’s Notion integration adds a “Docs and links” section to event details, enabling direct linking of specific Notion pages to calendar events.
Briefing
Notion’s new integration with KRON lets calendar events directly link to specific Notion pages—so meeting details can live in Notion while still showing up inside KRON. In KRON event details, a new “Docs and links” section appears; adding a Notion link triggers a standard Notion connection flow, then surfaces recent pages from the connected workspace. Users can also paste a page URL (copied from Notion via Cmd/Ctrl+L) or manage additional workspaces. When people are invited to the KRON event, they receive access to the linked Notion pages, making it a streamlined way to attach meeting notes, agendas, or other context without manual sharing.
KRON also brings practical calendar features that pair well with this workflow: an option to automatically add conferencing links (Zoom or Google Meet) to new events, plus support for multiple time zones in the calendar interface. Together, these features aim to reduce the friction between scheduling and the documents people need during meetings.
Still, the integration has a major gap: it doesn’t sync events from Notion to a calendar. Two-way syncing is described as especially difficult, so the missing capability remains unresolved for now. To partially bridge that gap, a separate automation is provided that pushes new events from a Notion database into Google Calendar.
The workaround uses PipeDream (spelled “pipedream” in the transcript) to run a scheduled workflow. The automation triggers every 15 minutes by default, but the setup recommends switching to every hour on PipeDream’s free plan to avoid exhausting daily credits. The workflow starts by connecting a Notion account with permission to the specific database that contains the events (the transcript emphasizes granting access to the database itself, not just the workspace). Next, the user selects the target database and maps Notion properties to calendar fields—using one property for the event name (typically the task name) and another property for the date/time.
A test event is created in Notion to supply dummy data for configuration. In the example, a task is given a due date and a due time, plus an end time, demonstrating that the automation can populate both start and end times in Google Calendar. If no end date is set, the end time defaults to the same value as the start time. After mapping the Notion fields, the workflow connects to a Google Calendar account, runs a test to confirm event creation, and then is deployed.
Once live, PipeDream checks the chosen Notion database on the set schedule, finds new pages, and creates corresponding events in Google Calendar. The automation is intentionally one-way: it doesn’t update existing events and doesn’t provide two-way sync. Even so, it offers a practical path for users who want Notion tasks or events to automatically appear on their calendar—while waiting for deeper native syncing between Notion and KRON.
Cornell Notes
KRON’s new Notion integration adds a “Docs and links” area inside event details, letting users attach specific Notion pages to calendar events. After connecting a Notion workspace, KRON shows recent pages, supports searching, and allows pasting a Notion page URL to link it quickly. Linked pages can be shared with invited attendees, making meeting context easier to distribute. The integration does not sync events from Notion into a calendar, so a separate one-way automation is provided using PipeDream to push new Notion database entries into Google Calendar on a schedule. The setup maps Notion properties (event name and date/time) to Google Calendar start/end times and creates events for new pages, without updating or two-way syncing.
How does the KRON–Notion integration work inside an event, and what can attendees access?
What’s missing from the native KRON–Notion integration?
How does the one-way Notion-to-Google Calendar automation run, and why change the schedule?
Which Notion fields are mapped to calendar event details?
What are the limitations of the automation once it’s deployed?
Review Questions
- What steps are required in KRON to link a Notion page to an event, and how can a user add a page via URL?
- In the PipeDream automation, which Notion properties must be selected to populate the calendar event name and start/end times?
- Why does the setup recommend changing the PipeDream trigger interval from every 15 minutes to every hour on the free plan?
Key Points
- 1
KRON’s Notion integration adds a “Docs and links” section to event details, enabling direct linking of specific Notion pages to calendar events.
- 2
Users can connect one or more Notion workspaces, then attach pages via recent-page selection, search, or by pasting a Notion page URL copied with Cmd/Ctrl+L.
- 3
Invited attendees can access the linked Notion pages associated with a KRON event, making meeting context easier to share.
- 4
The native integration does not sync events from Notion into a calendar, and two-way syncing isn’t available.
- 5
A one-way workaround uses PipeDream to push new pages from a chosen Notion database into Google Calendar on a schedule.
- 6
The automation maps a Notion “event name” property to the calendar title and a Notion date property to calendar start/end times; missing end dates default to the start time.
- 7
The automation creates events for new entries but does not update existing events or provide two-way synchronization.