Keep project subpages connected to Eventzilla context
A new subpage under your event plan can prompt Notis to check the Eventzilla list for useful existing context.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
List Events
Tool to retrieve a list of events associated with your account (supports filtering). use when you need to list or filter events for your organization.
Why this helps
As plans grow into subpages, useful event information can become harder to keep in view across tools.
- Check the event list when a planning subtopic begins.
- Return possible related entries in a report for review.
- Keep project context easier to recover as work expands.
Setup
Build it in a few focused steps.
- 1Connect Notion and Eventzilla to Notis once in the portal.
- 2Create an automation in the portal or ask Notis in a connected channel.
- 3Describe in one plain-language instruction how to list Eventzilla events and summarize those relevant to a new subpage under the planning page.
- 4Pick the Notion Page Added to Page trigger and choose where run reports should go.
- 5Test by adding one real subpage and review the event summary.
Questions about this workflow
Does this watch any subpage in the workspace?
This trigger applies to a specified parent page, so select the planning page intended to start the workflow.
Can it confirm a duplicate event?
It can summarize possible matches from the event list, but you should review before deciding.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Eventzilla. A trigger fires from one place; an action lands in another.
Notion triggers
Eventzilla actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get User Details
Tool to retrieve detailed information of a specific user. use after listing users to fetch full profile.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Event Categories
Tool to retrieve event categories available in eventzilla. use when you need to present or choose from available categories before creating or filtering events.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Events
Tool to retrieve a list of events associated with your account (supports filtering). use when you need to list or filter events for your organization.
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 Users
Tool to retrieve a list of users associated with your account. use when you need to fetch and paginate through users.
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 Eventzilla, 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 Eventzilla.