Get a weekly category review for active event plans
Start the week knowing which event classification decisions need attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Founders often remember event research only when promotion is already urgent.
- Creates a reliable review rhythm
- Reduces last-minute research
- Makes launch readiness easier to see
Setup
Build it in a few focused steps.
- 1Connect Notion and Eventbrite to Notis once through the portal.
- 2Create a scheduled automation in Automations -> New Automation or ask Notis to create it.
- 3Use this instruction: Every week, review active Notion event plans nearing promotion and retrieve relevant Eventbrite categories, reporting only decisions that need attention.
- 4Choose a weekly Notis schedule, select a run-report channel, and test it with the current event list.
Questions about this workflow
Can it focus on near-term events?
Yes. Tell Notis to prioritize plans with an upcoming promotion or launch date.
Will it send a report every week?
It reports according to the schedule and 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
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.