Skip to content
Notis

Create a Google Calendar for every new Notion database

Kicking off a project in Notion means a fresh database, and moments later you wish it had a calendar to match. Notis notices the new database and creates a dedicated Google Calendar, so each initiative starts life with a clean schedule instead of everything piling onto one calendar.

Trigger

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.

Action

Create a calendar

Creates a new, empty google calendar with the specified title (summary).

Why this helps

New projects begin in Notion but share one crowded calendar, so it becomes impossible to see any single initiative's schedule at a glance.

  • Every project starts with its own calendar
  • No more one crowded calendar for all initiatives
  • Clean separation makes each schedule easy to read
  • Setup happens the instant the database is created

Setup

Build it in a few focused steps.

  • 1Connect Notion and Google Calendar to Notis from the portal.
  • 2Open Automations, click New Automation, or ask Notis to set it up in any channel.
  • 3Describe the outcome: when a new database is created in Notion, create a matching Google Calendar named after it.
  • 4Pick the Database Created trigger and choose the channel for run reports.
  • 5Test by creating one database and confirming the new calendar appears.

Questions about this workflow

What name does the new calendar get?

Notis names it from the database by default. Describe your naming preference in the prompt if you want a specific pattern.

Will this fire for every database I make?

You can scope the prompt so it only creates calendars for project databases, ignoring casual or scratch ones.

Can it also route future events to that calendar?

Yes. Pair this with an automation that files new project events onto the calendar Notis just created.

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.

TriggerPolling

Insert Calendar into List

Inserts an existing calendar into the user's calendar list.

ActionInstant

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.

TriggerInstant

Update Calendar List Entry

Updates an existing entry on the user\'s calendar list.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Delete Calendar

Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.

ActionInstant

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.

TriggerInstant

Update Calendar

Updates metadata for a calendar.

ActionInstant

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.

TriggerInstant

Clear Calendar

Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

New Page

Triggers when a new page is added to a Notion database.

TriggerPolling

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.

ActionInstant

Page Added to Page

Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.

TriggerPolling

Create a calendar

Creates a new, empty google calendar with the specified title (summary).

ActionInstant

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.