Skip to content
Notis

Turn new Notion event briefs into Eventbrite category options

Start every event with a category decision already in motion.

Trigger

New Page

Triggers when a new page is added to a Notion database.

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

Choosing an event category from scratch creates avoidable research and decision fatigue.

  • Reduces category research time
  • Creates a repeatable launch starting point
  • Keeps event planning inside a familiar Notion workflow

Setup

Build it in a few focused steps.

  • 1Connect Notion and Eventbrite to Notis once through the portal.
  • 2Create an automation in Automations -> New Automation, or ask Notis to create it conversationally.
  • 3Use this instruction: When a new Notion event brief is created, retrieve the most relevant Eventbrite categories and report the recommendation with the brief link.
  • 4Select the Notion New Page trigger and choose a channel for run reports, then test with one real brief.

Questions about this workflow

Does this publish the event automatically?

No. It retrieves category options and reports a recommendation so you can make the final launch decision.

Can I use a shared event brief database?

Yes. Scope the Notion New Page trigger to the database when creating the automation.

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.

TriggerPolling

Get Event Categories

Tool to retrieve event categories. use when selecting a category for an event. localizes results via optional locale parameter.

ActionInstant

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.

TriggerInstant

Get Event Formats

Tool to list event formats. use when you need the available formats before creating or updating an event.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Get Event Subcategories

Tool to list all event subcategories. use when fetching available subcategory options, optionally filtered by locale after selecting a category.

ActionInstant

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.

TriggerInstant

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.

TriggerInstant

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.

TriggerInstant

New Page

Triggers when a new page is added to a Notion database.

TriggerPolling

Page Added to Page

Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.

TriggerPolling

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.