Find the right Eventbrite subcategory for each workshop
Give every workshop a clearer place to be found.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
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
Broad categories make discovery decisions feel vague and force founders to repeat the same research.
- Improves event classification decisions
- Reduces repeated taxonomy searches
- Supports more consistent workshop launches
Setup
Build it in a few focused steps.
- 1Connect Notion and Eventbrite to Notis once through the portal.
- 2Create a new automation in the portal or ask Notis to build it by conversation.
- 3Use this instruction: When a new Notion workshop page is created, retrieve suitable Eventbrite subcategories and send the shortlist with the page link.
- 4Select the Notion Page Created trigger, choose run-report delivery, and test with one workshop page.
Questions about this workflow
Is this limited to workshops?
The instruction can target any event type, but it is especially useful for workshop pages.
Does it select a subcategory for me?
It retrieves and summarizes suitable options for your review.
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.