Let a Clear Notion Comment Carry a Ninox Cleanup Request
Sometimes the decision to remove a record comes up in discussion. Ask Notis to act on a comment only when it explicitly requests deletion and names the exact Ninox record, so a cleanup decision is easier to follow through on.
Trigger
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.
Action
Delete Record
Tool to delete a record from a specified table. use after confirming workspace, database, table, and record ids.
Why this helps
A cleanup decision made in a discussion can be easy to lose among other follow-ups.
- Uses a specific comment as the signal for a requested cleanup.
- Requires the request to identify the exact Ninox record.
- Helps carry a clear decision from discussion into the next action.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ninox to Notis once, and confirm the Ninox workspace, database, table, and record identification approach.
- 2Create an automation in the portal with a prompt that permits deletion only when a new comment explicitly requests it and identifies the exact Ninox record.
- 3Select the Notion Comment Created trigger and choose where run reports should appear.
- 4Test with one real comment on a record approved for deletion and review the run report.
Questions about this workflow
Could an ordinary comment cause a deletion?
The prompt should require an explicit deletion request and an exact record identifier. Test with an ordinary comment to confirm it does not meet that instruction.
Does the trigger watch the whole workspace?
The Comment Created event can cover comments the integration can access. It requires the Notion integration's Read comments capability.
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.