Make new Notion data sources easier to adopt
A new database structure can be useful and unfamiliar at the same time. Create a Coda orientation doc to explain where it fits and how to start.
Trigger
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.
Action
Create doc
Creates a new coda doc, optionally copying an existing doc. note that creating a doc requires you to be a doc maker in the applicable workspace (or be auto-promoted to one).
Why this helps
New workspace resources can add more questions when no one knows their purpose or owner.
- Give a new data source an accessible introduction.
- Reduce repeated questions about its purpose.
- Make workspace changes easier to communicate.
Setup
Build it in a few focused steps.
- 1Connect Notion and Coda to Notis once through the portal.
- 2Create an automation through the portal or ask Notis for it conversationally.
- 3In plain language, ask Notis to create a Coda orientation doc for each new Notion data source, explaining its likely purpose from available context.
- 4Choose Data Source Created and select a reporting channel.
- 5Test with a new data source event and review the orientation doc.
Questions about this workflow
How often can this trigger fire when a template is used?
A template-based database creation can produce multiple data source events, one for each data source it creates.
Can the doc explain where the data source lives?
Ask Notis to include available parent context in the plain-language instruction.
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.