Keep your program positioning aligned with Eventbrite categories
A clearer program page leads to a clearer public event listing.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Get Event Categories
Tool to retrieve event categories. use when selecting a category for an event. localizes results via optional locale parameter.
Why this helps
Program positioning evolves, but category guidance often stays frozen in an earlier version.
- Keeps program language and classification aligned
- Reduces rework across sessions
- Creates a timely review signal
Setup
Build it in a few focused steps.
- 1Connect Notion and Eventbrite to Notis once through the portal.
- 2Create the automation through the portal or by asking Notis in plain language.
- 3Use this instruction: When the Notion program page is updated, retrieve Eventbrite categories that match the current positioning and summarize any meaningful change.
- 4Select the Notion Page Updated trigger for the program page, choose a report channel, and test with one content update.
Questions about this workflow
What counts as a program update?
The instruction can focus on changes to audience, promise, topic, or delivery.
Can this support an event series?
Yes. It is designed to keep series-level positioning coherent.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Event Categories
Tool to retrieve event categories. use when selecting a category for an event. localizes results via optional locale parameter.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Event Formats
Tool to list event formats. use when you need the available formats before creating or updating an event.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Event Subcategories
Tool to list all event subcategories. use when fetching available subcategory options, optionally filtered by locale after selecting a category.
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 Eventbrite, 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 Eventbrite.