Answer webinar date questions from your Notion page
Keep scheduling questions moving by having Notis check the Demio dates connected to the page being discussed.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
List Event Dates
Tool to list all scheduled session dates for a given Demio event. Use when you need the session schedule by event ID.
Why this helps
A quick question about timing can turn into several tool switches and a forgotten reply when the event schedule is elsewhere.
- Make a comment on the chosen page a cue to retrieve session dates.
- Keep timing questions attached to the webinar planning conversation.
- Reduce the chance that a scheduling follow-up gets lost.
Setup
Build it in a few focused steps.
- 1Connect Notion and Demio to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it in plain language.
- 3In one instruction, ask for Demio dates for the event referenced on the commented webinar page.
- 4Pick the Notion New Comment trigger for the specific page and choose a channel for run reports.
- 5Test by adding a comment that identifies a valid event.
Questions about this workflow
What is the difference from a workspace comment trigger?
This trigger watches comments on a specified Notion block or page.
Will it create a calendar event?
No. It retrieves the scheduled Demio session dates for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Demio. A trigger fires from one place; an action lands in another.
Notion triggers
Demio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Demio Create Join Link
Tool to register an attendee and obtain their unique Demio join link. Use after confirming a valid event_id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Demio: Get Event by ID
Tool to retrieve event details by ID. Use when you need the full metadata for a specific Demio event.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Event Date Participants
Tool to list participants for a specific event date. Use after scheduling an event session to retrieve attendees.
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.
List Event Dates
Tool to list all scheduled session dates for a given Demio event. Use when you need the session schedule by event ID.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Demio Events
Tool to retrieve a list of Demio events. Use when you need to fetch events optionally filtered by type or paginated.
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.
Demio API Ping
Tool to perform a health check on the Demio API. Use to verify the API is reachable before other calls.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Demio, 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 Demio.