Keep your Notion event brief aligned with Demio details
When the event brief changes, retrieve the current Demio event information without leaving your planning flow to look it up yourself.
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
Demio: Get Event by ID
Tool to retrieve event details by ID. Use when you need the full metadata for a specific Demio event.
Why this helps
Event details spread across planning pages and webinar tools are easy to misremember when a brief is revised.
- Use a brief update as a cue to retrieve current Demio event metadata.
- Reduce the need to switch tools during planning revisions.
- Keep the relevant event details ready for the next planning decision.
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 conversationally to set it up.
- 3Tell Notis in plain language to retrieve Demio details for the event referenced by an updated Notion brief.
- 4Pick the Notion Page Properties Updated trigger for the brief and choose a run-report channel.
- 5Test with an updated brief that references a valid Demio event ID.
Questions about this workflow
What information can Demio provide?
The action retrieves details for a specific event by its ID.
Will this update the Notion brief?
The listed Demio action retrieves event details. It does not write them back to Notion.
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.