Make ownership handoffs easier to pick up
When an item's ownership or other handoff details change, query Contentful for relevant entries and give the next person context.
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
GraphQL Content API Query
Tool to execute a GraphQL query against a specified space and environment. Use when fetching Contentful content via GraphQL after obtaining or providing a valid token.
Why this helps
A handoff can drop useful history when the next owner has to search for related content before taking action.
- Give a new owner relevant material to review.
- Reduce repeated explanations during handoffs.
- Help work resume with less context rebuilding.
Setup
Build it in a few focused steps.
- 1Connect Notion and Contentful graphql to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to retrieve Contentful context when a Notion handoff item's properties change.
- 3Choose the Notion Page Properties Updated trigger and describe the handoff summary in the prompt.
- 4Choose a reporting channel and test with one real ownership change.
Questions about this workflow
Can the trigger be limited to one data source?
Yes. Page Properties Updated supports an optional data_source_id scope.
Will it assign the next owner?
No. The Contentful action retrieves related entries and reports them through Notis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Contentful graphql. A trigger fires from one place; an action lands in another.
Notion triggers
Contentful graphql actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get CMA Token
Tool to retrieve a Contentful Management API (CMA) access token. Use when making CMA calls to ensure valid authorization.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
GraphQL Content API Persisted Query
Tool to execute a persisted GraphQL query via its SHA256 hash. Use after registering a query hash to run cached queries by hash. On first call include full query text; thereafter invoke with only hash and variables.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
GraphQL Content API Query
Tool to execute a GraphQL query against a specified space and environment. Use when fetching Contentful content via GraphQL after obtaining or providing a valid token.
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 graphql, 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 graphql.