Surface free calendar slots from Notion meeting requests
Someone drops a meeting request into Notion and now you owe them times, but checking your calendar means stopping everything to squint at the week. Notis catches the new request and pulls your open Google Calendar slots, so you can offer availability without breaking focus.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Find free slots
Finds free/busy time slots in google calendars for specified calendars within a defined time range (defaults to the current day utc if `time min`/`time max` are omitted), enhancing busy intervals with event details; `time min` must precede `time max` if both are provided.
Why this helps
Every meeting request forces a context switch into the calendar to hunt for open times, and the reply keeps sliding down the to-do list.
- Availability is ready before you even open the calendar
- Replies to meeting requests stop stalling for days
- No manual scanning across a busy week
- Fewer context switches out of your current work
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Calendar to Notis from the portal.
- 2Open Automations and click New Automation, or ask Notis to set it up in any channel.
- 3State the outcome: when a meeting request is added to my Notion database, find my free Google Calendar slots and send them to me.
- 4Choose the New Page trigger for the request database and pick the channel for results.
- 5Test with one request and confirm Notis returns usable open times.
Questions about this workflow
Can I limit the search to working hours?
Yes. Describe your preferred window in the prompt and Notis will only surface slots inside it.
Does it book the meeting too?
This automation finds and returns open times. Pair it with a create-event automation if you want Notis to book directly.
Can it check more than one calendar for conflicts?
Yes. Name the calendars in the prompt and Notis will treat all of them as busy time when finding free slots.
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.