Start the week with a focused view of upcoming meetings
Notis can fetch upcoming bookings on your chosen weekly cadence, giving your Notion review a ready starting point for preparation and follow-up.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Fetch all bookings
Fetches a list of bookings, optionally filtered by status, attendee, date range, or by event/team ids (which must belong to/include the authenticated user respectively), with support for pagination and sorting.
Why this helps
A weekly review loses momentum when it begins with manually gathering calendar information.
- Bring upcoming meeting context into a recurring review.
- Reduce the effort of collecting calendar information.
- Make preparation and follow-up easier to spot at the start of the week.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cal to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to fetch upcoming bookings for your weekly planning review.
- 3Describe the useful date range and summary in one plain-language instruction.
- 4Choose a weekly recurring trigger and a channel for run reports, then test with one review cycle.
Questions about this workflow
Can I choose the weekly timing?
Yes. Select a recurring schedule that suits your planning routine and timezone.
Does the scan change any bookings?
No. It fetches bookings to support review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cal. A trigger fires from one place; an action lands in another.
Notion triggers
Cal actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add member to team
Adds a new member to a specified team within an organization by creating a team membership.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add organization attribute option
Adds a new option to an organization's attribute, requiring a display `value` and a `slug` unique for that attribute.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete oauth client webhook
Permanently deletes a specific webhook subscription of an oauth client in the cal application, stopping its notifications.
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.
Cancel booking via uid
Cancels an existing and active cal.com booking using its unique identifier (uid).
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Check calendar availability
Retrieves free/busy availability for a specified calendar to aid scheduling without revealing event details; requires an existing, accessible calendar, noting that data granularity can vary.
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.
Check gcal synchronization status
Call this read-only action to verify the connection and synchronization status of a user's google calendar integration with cal.
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.
Check ics feed calendar endpoint
Checks an ics feed url (expected as a query parameter) to verify its validity, accessibility, and icalendar data integrity.
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.
Check Stripe status
Verifies if stripe is correctly connected to the cal scheduling system and functional for processing payments, reporting only on the integration's status.
Connect any two apps with Notis in the middle.
Notion and Cal, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Cal.