Add new Notion tasks to Google Calendar automatically
You capture a task in Notion and mean to schedule it later, but later never comes. Notis watches your task database and turns each new item into a real Google Calendar event, so a due date becomes a block of time you will actually see.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Event
Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.
Why this helps
Tasks pile up in Notion with due dates that never make it onto the calendar, so the day arrives and the work is a surprise.
- Every dated task shows up where you plan your day, not buried in a list
- No manual copying of titles and dates from Notion into Calendar
- Due dates stop slipping because the time is already reserved
- One less tab to check when you decide what to work on
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Calendar to Notis once from the portal.
- 2Ask Notis for your portal link, then open Automations and click New Automation.
- 3Write the plain-language prompt: when a new task is added to my Notion database, create a Google Calendar event using its title and due date.
- 4Pick the New Page trigger for your task database and choose the channel where Notis reports each run.
- 5Test it by adding one dated task in Notion and confirm the event appears on your calendar.
Questions about this workflow
Do I have to map the Notion date field to the calendar time?
No. Notis reads your plain-language instruction and figures out the due date on its own. There are no field-mapping screens to fill in.
What if a task has no due date?
You can tell Notis in the prompt to skip tasks without a date, or to place them on a default day so nothing gets lost.
Which calendar does the event go on?
Your primary Google Calendar by default. Mention a specific calendar in the prompt and Notis will use that one instead.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google Calendar. A trigger fires from one place; an action lands in another.
Notion triggers
Google Calendar actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Insert Calendar into List
Inserts an existing calendar into the user's calendar list.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Update Calendar List Entry
Updates an existing entry on the user\'s calendar list.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Calendar
Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Update Calendar
Updates metadata for a calendar.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Clear Calendar
Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Create Event
Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.
New Page
Triggers when a new page is added to a Notion database.
Delete event
Deletes a specified event by `event id` from a google calendar (`calendar id`); this action is idempotent and raises a 404 error if the event is not found.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Create a calendar
Creates a new, empty google calendar with the specified title (summary).
Connect any two apps with Notis in the middle.
Not just Notion and Google Calendar. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Google Calendar.