See Your Ninox Options When a New Notion Database Appears
Starting a new Notion database can raise the question of where its related records belong. Ask Notis to retrieve your Ninox database list when that happens, so you can review the available destinations without switching tools to look them up.
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
Get Databases
Tool to retrieve all databases in a specific ninox team. use after confirming the team id is correct.
Why this helps
Choosing a Ninox destination interrupts the work of setting up a new Notion database.
- Surfaces available Ninox databases after a Notion database is created.
- Reduces a separate lookup during workspace setup.
- Keeps the next destination decision grounded in the confirmed Ninox team.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ninox to Notis once, and confirm which Ninox team to use.
- 2In the portal, create an automation with a short name and a prompt asking Notis to retrieve the databases in that team when a Notion database is created.
- 3Select the Notion Database Created trigger and choose where Notis should report runs.
- 4Test by creating one real Notion database and reviewing the run result.
Questions about this workflow
Does this create a Ninox database?
No. The available Ninox action retrieves the databases in a team so you can review them.
What should I confirm before enabling it?
Confirm the Ninox team with Notis and check that the run report shows the expected database list.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ninox. A trigger fires from one place; an action lands in another.
Notion triggers
Ninox actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Databases
Tool to retrieve all databases in a specific ninox team. use after confirming the team id is correct.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Record
Tool to delete a record from a specified table. use after confirming workspace, database, table, and record ids.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Ninox, 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 Ninox.