Schedule lead conversations from your Notion pipeline
Move a promising lead from your Notion pipeline toward a booked conversation without rewriting their details by hand.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Meeting Request V2
Tool to create a new meeting request in calendarhero. use when scheduling a meeting with participants, time range, and additional details.
Why this helps
New prospects can sit untouched while founders switch between tracking leads and scheduling conversations.
- Respond to new leads while their context is fresh.
- Reduce copying details between the pipeline and scheduling.
- Keep the next step visible in a familiar calendar workflow.
Setup
Build it in a few focused steps.
- 1Connect Notion and Calendarhero to Notis once through the portal.
- 2Create an automation in the portal or tell Notis in plain language what should happen for a new lead.
- 3Use one instruction asking Notis to create a suitable Calendarhero meeting request from the new Notion record and its context.
- 4Choose the Notion New Page trigger, a channel for run reports, and test with one real lead.
Questions about this workflow
Does every new database page have to become a meeting request?
Describe in the prompt which new records indicate a lead ready to meet. Notis interprets the instruction from the page context.
What if the record lacks meeting details?
Tell Notis to flag incomplete records in its run report rather than create a request with missing information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Calendarhero. A trigger fires from one place; an action lands in another.
Notion triggers
Calendarhero actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Calendar Connection
Tool to add a calendar integration to a user's account. use after gathering provider credentials.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Contact
Tool to create a new contact. use after confirming contact details before making the api call.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Meeting Request V2
Tool to create a new meeting request in calendarhero. use when scheduling a meeting with participants, time range, and additional details.
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.
Fetch Contact
Fetch contact
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Fetch Meeting Details
Tool to fetch details for meetings within a specified timeframe. use this after user provides start and end datetimes in iso8601.
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.
Fetch User Profile
Tool to fetch the profile details of the authenticated user. use after obtaining a valid access token.
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.
List Meetings
Tool to retrieve the user's meetings within a specified timeframe. use after confirming date range to fetch raw calendar data.
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.
List Meeting Templates
Tool to list all meeting templates available for quick scheduling. use after authenticating and when you need to retrieve available templates before scheduling.
Connect any two apps with Notis in the middle.
Notion and Calendarhero, 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 Calendarhero.