Give every new meeting note a clear recap
Make the meeting easier to leave behind. Notis can create a Coda recap page that brings decisions and follow-ups into view.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
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
Meeting notes can quickly become a wall of text that is hard to turn into action.
- Surface decisions and next steps after a meeting.
- Create a consistent place to revisit the conversation.
- Spend less time searching through notes for commitments.
Setup
Build it in a few focused steps.
- 1Connect Notion and Coda to Notis once through the portal.
- 2Create an automation in the portal or ask Notis for it conversationally.
- 3In one plain-language instruction, ask Notis to create a Coda recap page when a meeting note is created, emphasizing decisions and follow-ups.
- 4Choose Page Created for the relevant Notion parent page or data source and a channel for reports.
- 5Test with one new meeting note and review its Coda recap.
Questions about this workflow
Can this work for notes under one meeting page?
Yes. Scope Page Created to the parent Notion page that contains the meeting notes.
Do I have to format the meeting note first?
No special field mapping is needed. Describe in the prompt what kind of recap you want Notis to create.
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.