Keep tracking changes close to their content workspace
When a record changes, bring the relevant Contentful space context into the follow-up.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Get space
Retrieves details of a specific space by its id. this action is used to get information about a single space in contentful.
Why this helps
Property updates often signal a change in ownership or status, but the connected workspace can remain out of sight.
- Bring relevant workspace details to an operational change.
- Make the next step easier to identify.
- Reduce repeated context gathering.
Setup
Build it in a few focused steps.
- 1Connect Notion and Contentful to Notis once in the portal.
- 2Create an automation in Automations, or ask Notis conversationally.
- 3In one plain-language instruction, ask Notis to retrieve details for the Contentful space linked to a changed tracking record and summarize them.
- 4Choose the Notion Page Properties Updated trigger and scope it to the relevant data source if useful.
- 5Choose a channel for run reports and test with one real record change.
Questions about this workflow
Can the trigger be limited to one database?
Yes. Page Properties Updated can be scoped to a data source or page.
Can it act only on a particular property?
The event includes updated property information that Notis can use in its instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Contentful. A trigger fires from one place; an action lands in another.
Notion triggers
Contentful actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get space
Retrieves details of a specific space by its id. this action is used to get information about a single space in contentful.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List spaces
Lists all spaces that the authenticated user has access to in contentful. this is a fundamental operation needed before performing any other content management actions since most operations require a space id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Update space
Updates the name of a specific space. notes: - the version number is required to ensure you're updating the latest version of the space. - you can get the current version from the sys.version field when fetching space details. - only the name of the space can be updated.
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 Contentful, 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 Contentful.