Keep workspace changes from becoming background noise
A busy workspace changes all day. Let Notis identify relevant page events and create a concise Coda digest entry with the context worth keeping.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
Create a page
Create a new page in a doc. note that creating a page requires you to be a doc maker in the applicable workspace.
Why this helps
Scanning every workspace update takes attention away from focused work.
- Reduce manual scanning of workspace changes.
- Keep relevant context in a place you already use.
- Ask Notis to surface only changes that fit the instruction.
Setup
Build it in a few focused steps.
- 1Connect Notion and Coda to Notis once through the portal.
- 2Create a new automation in the portal or tell Notis what you want in plain language.
- 3Describe which Notion page changes matter and ask Notis to create a concise Coda digest page with context and a useful next step.
- 4Choose All Page Events as the trigger and select a run-report channel.
- 5Test with a real page event and review whether the prompt identifies the right changes.
Questions about this workflow
Will this trigger fire often?
All Page Events triggers when any Notion page is created or updated across the workspace. Write a focused prompt so Notis can assess relevance.
Can the prompt ignore unrelated updates?
Yes. Describe the kinds of changes that matter to your work so Notis can decide whether to create a digest page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Coda. A trigger fires from one place; an action lands in another.
Notion triggers
Coda actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a category for pack
Add a publishing category for a given pack.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a maker for pack
Set a maker for a given pack. used to display makers for a pack in the corresponding packs page.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add a permission for pack
Create or modify user, workspace, or global permissions for a given pack.
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.
Add custom domain
Add a custom domain to a published doc.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Add permission
Adds a new permission to the doc.
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.
Begin content export
Initiate an export of content for the given page.
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.
Content export status
Check the status of a page content export
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.
Copy Document
Creates a copy of an existing coda document. this action allows you to duplicate a document while optionally specifying a new title and location for the copied document.
Connect any two apps with Notis in the middle.
Notion and Coda, 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 Coda.