Refresh event context after a Notion page update
When a planning page changes, get a current view of related Evenium events so you can keep moving with useful context.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Get Events
Tool to retrieve a list of events with optional filters. use after authenticating with evenium.
Why this helps
Event pages change over time, and remembering to revisit a separate schedule adds another follow-up to track.
- Pair a page update with a fresh schedule lookup.
- Avoid relying solely on an old event summary.
- Reduce context switching during planning.
Setup
Build it in a few focused steps.
- 1Connect Notion and Evenium to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Ask Notis in one plain-language instruction to retrieve Evenium events related to the selected page whenever a block on that page changes and summarize useful context.
- 4Select Page Updated for the chosen page and choose a report channel.
- 5Test with one real page update and check the report.
Questions about this workflow
How is this different from Page Content Updated?
Page Updated watches block updates within a specified page. Page Content Updated watches edits to page body content and supports different optional scopes.
Can it alter the Evenium schedule?
No. It can retrieve and summarize event information only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Evenium. A trigger fires from one place; an action lands in another.
Notion triggers
Evenium actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Contacts
Tool to retrieve a list of contacts from evenium. use when you need to fetch and optionally filter organizer contacts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Events
Tool to retrieve a list of events with optional filters. use after authenticating with evenium.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Logout
Tool to log out the current user and invalidate the session token. use when you need to explicitly end the current session.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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 Evenium, 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 Evenium.