Connect new project pages with comparison records
A new project subpage may capture a document decision or deliverable. Surface likely comparison context while it is being organized.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
List Comparisons
Tool to retrieve a paginated list of document comparisons. use when you need to browse comparisons across pages.
Why this helps
Project details spread across nested pages can make it harder to remember where document review stands.
- Catch new project context as it is added.
- Make likely comparison records easier to discover.
- Keep project organization from creating another search task.
Setup
Build it in a few focused steps.
- 1Connect Notion and Draftable to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it conversationally.
- 3Use one instruction asking Notis to list Draftable comparisons when a subpage is added under the project page and report likely matches using its context.
- 4Choose Page Added to Page and select the project page as the parent.
- 5Test with a real project subpage and review the report.
Questions about this workflow
Does this watch all project pages?
This event is for a new subpage under the specified parent page. Set up the trigger for the project page you want to monitor.
Can it create a comparison for the subpage?
No. It can only retrieve and report the available comparison list.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Draftable. A trigger fires from one place; an action lands in another.
Notion triggers
Draftable actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Comparisons
Tool to retrieve a paginated list of document comparisons. use when you need to browse comparisons across pages.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Draftable, 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 Draftable.