Keep project subpages available in Cody
Let new pages beneath a project hub become part of the knowledge Cody can use.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
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.
Why this helps
Project context tends to spread as new pages are created, making it harder to know where useful details live.
- Bring newly added subpages into Cody's document library.
- Keep useful project context available to Cody.
- Make it easier to search across evolving project notes.
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 ask Notis in plain language to create it.
- 3In one instruction, ask Notis to add each new subpage beneath the selected project hub to Cody as a document.
- 4Select Page Added to Page for the project hub and choose a run-report channel.
- 5Create one test subpage and confirm Cody receives its content.
Questions about this workflow
Will this trigger for any page in the workspace?
No. Page Added to Page is configured for a specified parent page, such as a project hub.
Can Cody search the new document immediately?
Cody processes documents after creation. Confirm the document's learning status if processing is still underway.
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.