Turn approved Notion briefs into Curated drafts
Mark a brief ready in Notion and have Notis prepare a Curated draft from it.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Create Draft Issue
Tool to create a draft issue for a publication. use after confirming the publication id. applies default settings if optional fields are omitted.
Why this helps
A finished brief can sit idle while you remember to open another tool and start an issue.
- Move approved writing into a draft without a manual handoff.
- Keep the draft tied to the brief that prompted it.
- Spend review time editing rather than starting from a blank issue.
Setup
Build it in a few focused steps.
- 1Connect Notion and Curated to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally for this outcome.
- 3In one plain-language instruction, explain how to recognize an approved newsletter brief and create a Curated draft issue from its content.
- 4Choose Notion Page Properties Updated and a reporting channel; test by updating one real brief to approved.
Questions about this workflow
Will every property change create a draft?
Describe the approval signal clearly in your instruction so Notis can determine whether the updated page is ready to become a draft.
Does this publish the issue?
No. The listed Curated action creates a draft issue for you to review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Curated. A trigger fires from one place; an action lands in another.
Notion triggers
Curated actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Draft Issue
Tool to create a draft issue for a publication. use after confirming the publication id. applies default settings if optional fields are omitted.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Collected Link
Tool to create a collected link for a publication. use when you want to add a new link (with url, title, etc.) to a publication's collection.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Email Subscribers
Tool to list all email subscribers for a publication. use after confirming the publication id.
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.
List Publications
Tool to list all publications accessible by the api key. use when you need to retrieve your publication ids for further api calls. example prompt: "list my publications".
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Categories
Tool to list all categories for a publication. use after you have the publication id and need to fetch its categories.
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.
List Issues
Tool to list all issues for a publication. use after you have the publication id and need to fetch its issues (supports pagination).
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 Curated, 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 Curated.