See your free calendar slots every week automatically
Weekly planning falls apart when you cannot see how much time is really open, so you overcommit and then feel buried. Notis runs each week, finds your free Google Calendar slots, and sends them over, so you plan against the time you actually have instead of the time you wish you had.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Planning the week without a clear view of free time leads to overcommitting, then a scramble when reality does not fit the plan.
- Plan against real availability, not optimism
- See open time before you commit to new work
- A weekly ritual that arrives without you starting it
- Fewer overbooked weeks and last-minute reshuffles
Setup
Build it in a few focused steps.
- 1Connect Google Calendar to Notis from the portal.
- 2Open Automations, click New Automation, or ask Notis in chat to create it.
- 3Describe it: every week, find my free Google Calendar slots for the coming days and send them to me.
- 4Choose a recurring weekly schedule as the trigger and pick the channel for the results.
- 5Test the run and confirm the open slots arrive in a form you can plan with.
Questions about this workflow
Can I set which days and hours count?
Yes. Describe your working window in the prompt and Notis will only report free time inside it.
Does it include all my calendars?
It uses the calendars you name in the prompt, treating their events as busy time so the free slots are accurate.
When does it run?
Whenever you set the weekly schedule, so you can have it land the evening or morning you like to plan.
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.