Find a contact's scheduled meeting history
Before following up, get a quick view of the meetings already on the calendar for a contact whose Notion record needs attention.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
List events
Retrieves a list of scheduled calendly events; requires `user`, `organization`, `group`, or `invitee email` for scope, and admin rights may be needed when filtering by `organization` or `group`.
Why this helps
Reconstructing whether a conversation is already scheduled can mean searching across contact notes and calendars.
- Bring scheduled meeting context into the follow-up process.
- Avoid duplicate outreach when a meeting is already booked.
- Reduce manual calendar searching before a conversation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Calendly to Notis once in the portal.
- 2Create the automation in the portal or ask Notis to make it in plain language.
- 3In one instruction, ask Notis to list Calendly events for the contact when a Notion record is flagged for a meeting-history check.
- 4Choose the Notion Page Properties Updated trigger and set a channel for reports.
- 5Test on a contact with a known email and an existing Calendly event.
Questions about this workflow
What scope does the event list need?
Calendly requires a user, organization, group, or invitee email scope. The prompt should identify the relevant contact email.
Does this create or change any meetings?
No. It retrieves event information for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Calendly. A trigger fires from one place; an action lands in another.
Notion triggers
Calendly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel event
Permanently cancels an existing, active scheduled event by its `uuid`, optionally providing a `reason`, which may trigger notifications to invitees.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create an invitee no-show
Marks an invitee, identified by their existing and valid uri, as a 'no show' for a scheduled event.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create One-Off Event Type
Creates a temporary calendly one-off event type for unique meetings outside regular availability, requiring valid host/co-host uris, a future date/range for `date setting`, and a positive `duration`.
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.
Create scheduling link
Create a single-use scheduling link. creates a scheduling link that can be used to book an event. the link allows invitees to schedule up to the specified maximum number of events. once the limit is reached, the link becomes inactive.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create share
Creates a customizable, one-time share link for a calendly event type, allowing specific overrides to its settings (e.g., duration, availability, location) without altering the original event type.
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.
Create single use scheduling link
Creates a one-time, single-use scheduling link for an active calendly event type, expiring after one booking.
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.
Create webhook subscription
Creates a calendly webhook subscription to notify a specified `url` (which must be a publicly accessible https endpoint) for selected `events` within a given `organization` and `scope`.
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.
Delete invitee data
Permanently removes all invitee data associated with the provided emails from past organization events, for data privacy compliance (requires enterprise subscription; deletion may take up to one week).
Connect any two apps with Notis in the middle.
Notion and Calendly, 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 Calendly.