Turn a ready Notion agenda into a ChMeetings meeting
Use the agenda you already prepared as the starting point for getting the meeting onto the ChMeetings calendar.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
ChMeetings: Create Meeting
Tool to create a new meeting in ChMeetings. Use when you have all meeting details and need to schedule it via the ChMeetings API.
Why this helps
An agenda can be complete while the actual meeting setup remains an easy-to-forget separate step.
- Links preparation to the scheduling step.
- Reduces context switching during meeting setup.
- Uses the agenda as a source of meeting context.
Setup
Build it in a few focused steps.
- 1Connect Notion and ChMeetings to Notis once.
- 2Create an automation via the portal or by asking Notis in plain language.
- 3Give one instruction asking Notis to create a ChMeetings meeting from the agenda page when it is ready, using the timing and details stated in the page.
- 4Choose Page Content Updated and scope it to the agenda page; select a channel for run reports.
- 5Test by making a clear ready-for-scheduling update and reviewing the meeting.
Questions about this workflow
Can I limit this to one agenda page?
Yes. The Page Content Updated trigger supports a page_id scope. Describe the readiness condition in the instruction as well.
Will every edit create a meeting?
The trigger fires for content edits. Make the instruction explicit about when the agenda is ready and test the behavior before depending on it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Chmeetings. A trigger fires from one place; an action lands in another.
Notion triggers
Chmeetings actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Invite Meeting Attendee
Tool to invite a new attendee to a specified meeting. Use when you need to add attendees before the meeting begins.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Attendee Details
Tool to retrieve details for a specific attendee. Use when you have an attendee_id and need the attendee's full profile.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
ChMeetings: Create Meeting
Tool to create a new meeting in ChMeetings. Use when you have all meeting details and need to schedule it via the ChMeetings API.
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.
ChMeetings: Create Organization
Tool to create a new organization.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
ChMeetings: Create Reminder
Tool to create/schedule a reminder for a meeting in ChMeetings.
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.
Delete Meeting Attendee
Tool to remove an attendee from a meeting. Use after confirming attendee details.
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 Meeting Attendees
Tool to list attendees of a meeting. Use when you need to retrieve attendees for a specific meeting.
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.
ChMeetings: Delete Meeting
Tool to delete an existing meeting. Use when you have confirmed the meeting ID to permanently remove the meeting.
Connect any two apps with Notis in the middle.
Notion and Chmeetings, 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 Chmeetings.