Turn meaningful Notion updates into Eventbrite taxonomy help
Let the workspace notice event-planning work before it becomes a forgotten task.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
Get Event Subcategories
Tool to list all event subcategories. use when fetching available subcategory options, optionally filtered by locale after selecting a category.
Why this helps
Event decisions scattered across pages are hard to monitor without adding another checklist.
- Reduces workspace monitoring
- Surfaces event decisions earlier
- Supports teams with many planning pages
Setup
Build it in a few focused steps.
- 1Connect Notion and Eventbrite to Notis once through the portal.
- 2Create the automation in Automations -> New Automation or ask Notis to create it conversationally.
- 3Use this instruction: When any Notion page changes, detect meaningful event-planning updates and retrieve relevant Eventbrite subcategories, reporting only when research is useful.
- 4Select the Notion All Page Events trigger, choose a channel for reports, and test with one genuine event update.
Questions about this workflow
Could this create too many reports?
The instruction can tell Notis to report only when the update clearly changes event classification needs.
Does it scan all workspace content?
It responds to accessible Notion page events and follows the relevance rules in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Eventbrite. A trigger fires from one place; an action lands in another.
Notion triggers
Eventbrite actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Event Categories
Tool to retrieve event categories. use when selecting a category for an event. localizes results via optional locale parameter.
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.
Get Event Formats
Tool to list event formats. use when you need the available formats before creating or updating an event.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Event Subcategories
Tool to list all event subcategories. use when fetching available subcategory options, optionally filtered by locale after selecting a category.
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.
New Page
Triggers when a new page is added to a Notion database.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Connect any two apps with Notis in the middle.
Not just Notion and Eventbrite. Any 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 Eventbrite.