Connect key Notion page updates to account work
Update the operating page in Notion and let Notis start the Nango action that follows from its current instructions.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Trigger Nango Action
Tool to trigger nango workflow actions via api. use when you need to execute an action by specifying the connection, provider config, and action identifier.
Why this helps
Operational instructions can change in Notion while the external work still follows an outdated understanding.
- Uses a specific operational page as the update signal.
- Keeps account-related next steps close to the latest documented context.
- Provides a run record for checking what happened.
Setup
Build it in a few focused steps.
- 1Connect Notion and Nango to Notis once through the portal.
- 2Create an automation through the portal or tell Notis what account action follows a page update.
- 3In one instruction, explain the context to use and the Nango action to run.
- 4Select Page Updated for the selected page and choose a channel for run reports.
- 5Test with one real page update and inspect the Nango action result.
Questions about this workflow
What does Page Updated watch?
It triggers when a block within the specified Notion page is updated.
How can I avoid unrelated page edits?
Scope the trigger to a specific page and describe the relevant update in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Nango. A trigger fires from one place; an action lands in another.
Notion triggers
Nango actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Trigger Nango Action
Tool to trigger nango workflow actions via api. use when you need to execute an action by specifying the connection, provider config, and action identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Connections
Tool to list all connections. use when you need to retrieve existing connections.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Connections
Tool to list all connections without credentials. use when you need connection metadata across your account without exposing credentials.
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.
Get Provider Details
Tool to retrieve details for a specific provider. use when you need to fetch provider configuration details by name (e.g., 'salesforce'). use after selecting the provider.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Providers
Tool to retrieve a list of all available providers. use when you need to display or iterate through every provider before creating connections.
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.
Get Scripts Configuration
Tool to fetch the nango scripts configuration. use when you need to get the available scripts and their triggers.
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.
Trigger Sync
Tool to trigger a sync process manually. use after establishing a connection and defining a sync.
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 Nango, 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 Nango.