Your Notion Edits Go Live Instantly
Fix a typo, add a paragraph, or rewrite your about page in Notion and it flows to your site in seconds. No publishing queue. No approval step.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Sync Content Items
Tool to retrieve all content items in a paged format with sync tokens. use when you need to synchronize large volumes of content and maintain state across calls.
Why this helps
You fix mistakes and improve content in Notion but forget that your live site still shows the old version, creating confusion and lost trust.
- Updates land on your site immediately
- No forgotten republish tasks
- Your site always reflects your latest thinking
Setup
Build it in a few focused steps.
- 11. Open Notis portal and ensure Notion and Agility cms are connected.
- 22. Create a new automation: 'When content in a Notion page changes, sync it to Agility cms content items.'
- 33. Select your notification channel and pick which Notion pages or databases to watch.
- 44. Edit a test page in Notion and confirm the change appears on your live site within 30 seconds.
Questions about this workflow
Will this sync partial edits or only complete page rewrites?
Notis captures all content changes, even a single word edit. It syncs whenever you update the page body in Notion.
What if I'm working on a post and don't want intermediate drafts going live?
Use a Status property in Notion. Tell Notis to only sync pages marked as 'Reviewed' or 'Final.' Keep drafts unpublished until ready.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Agility cms. A trigger fires from one place; an action lands in another.
Notion triggers
Agility cms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Authors
Tool to retrieve all authors from an agility cms instance. use when you need the full list of authors for display or processing.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Categories
Tool to get all categories. use when you need to list every category in a given locale.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Content Item
Tool to fetch details of a content item by content id. use when you need item fields and metadata from agility cms.
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 Content List
Tool to retrieve a list of content items by reference name. use when you need to fetch and page through content list data with optional filtering, sorting, and link expansions.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Content Models
Tool to retrieve content models and page modules. use when you need schema definitions to dynamically build content structures.
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 Logs
Tool to retrieve sync items (logs) from agility cms. use after initial full sync to fetch updates.
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.
Get Page
Tool to retrieve details of a page, including metadata, content zones, and components. use after you know the page id to fetch.
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.
Get Page Modules
Tool to retrieve all page modules defined in the agility instance. use when you need only modular definitions without content models.
Connect any two apps with Notis in the middle.
Notion and Agility cms, 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 Agility cms.