Start an event database with an Eventee overview
As your event database takes shape, get a quick overview of Eventee events so existing work stays in view.
Trigger
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.
Action
List Events
Tool to retrieve a list of all events. use when you need an overview of all events.
Why this helps
Creating a new event database can split planning from existing events unless someone checks the current event list.
- Bring current Eventee context to a newly created planning database.
- Reduce the chance of duplicating event records.
- Keep a simple report alongside the new planning setup.
Setup
Build it in a few focused steps.
- 1Connect Notion and Eventee to Notis once through the portal.
- 2Create a prompt that asks for an Eventee overview only when the new Notion database is for event planning.
- 3Choose Notion Database Created and a channel for run reports.
- 4Create the automation and test with one real event database creation.
Questions about this workflow
Does this run when I add a data source to an existing database?
No. Database Created is for creation of the database container; adding a data source to an existing database is a distinct event.
Will it create an event in Eventee?
No. This workflow lists existing events for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Eventee. A trigger fires from one place; an action lands in another.
Notion triggers
Eventee actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add speaker
Tool to add a new speaker to a specific eventee event. use after creating an event and obtaining its id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Speaker
Tool to delete a speaker by their id. use when you need to remove a speaker after confirming their id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Events
Tool to retrieve a list of all events. use when you need an overview of all events.
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 Eventee, 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 Eventee.