Check process changes while the context is fresh
Use a process edit as a chance to check whether the new instructions are clear and complete.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Create Conversation
Tool to create a new conversation with a specified bot. Use when starting a new conversation thread with optional focus mode to limit bot's knowledge base to specific documents.
Why this helps
Small process edits can leave gaps that only show up when the founder or team tries to follow them later.
- Review revised process instructions while they are fresh.
- Prompt a check for missing steps or unclear handoffs.
- Reduce the risk of rediscovering process gaps during execution.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cody to Notis once through the portal.
- 2Create an automation in the portal or tell Notis in a connected channel.
- 3Use one instruction asking Notis to start a Cody review conversation after an SOP page changes and identify unclear or missing steps.
- 4Select Page Updated for the SOP page and choose where run reports should appear.
- 5Make one genuine test edit and review Cody's process feedback.
Questions about this workflow
Can I use this for one SOP?
Yes. Configure Page Updated for the specific page whose blocks should start the workflow.
Does this overwrite my procedure?
No. It creates a Cody conversation for review. You decide whether to edit the Notion process.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cody. A trigger fires from one place; an action lands in another.
Notion triggers
Cody actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Conversation
Tool to create a new conversation with a specified bot. Use when starting a new conversation thread with optional focus mode to limit bot's knowledge base to specific documents.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Document
Tool to create a new document with text or HTML content in Cody AI. Use when you need to add documents to Cody's knowledge base with up to 768 KB of content.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Document From File
Tool to create a document by uploading a file (up to 100 MB). Supports txt, md, rtf, pdf, ppt, pptx, pptm, doc, docx, docm formats. Use when you need to add file-based documents to Cody's knowledge base. The file is processed asynchronously.
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.
Create Document from Webpage
Tool to create a document from a publicly accessible webpage URL. Use when you need to import content from a webpage into Cody AI. The webpage must be accessible without login. If request fails, ensure the URL is publicly accessible and not blocked by a firewall.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Folder
Tool to create a new folder in Cody AI for organizing content. Use when you need to create a folder to organize documents or conversations.
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.
Delete Conversation
Tool to delete a conversation by its ID. Use when you need to permanently remove a conversation from the system.
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.
Delete Document
Tool to delete a document by id. Use when removing a document that is no longer needed.
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 Conversation
Tool to fetch a conversation by its ID from Cody AI. Use when you need to retrieve details about a specific conversation. Supports optional includes parameter to filter response to list document IDs.
Connect any two apps with Notis in the middle.
Notion and Cody, 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 Cody.