Share new Notion policy pages with a team draft
Pair a new policy page with a clear message about what changed and where to read more.
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 Draft
Tool to create a new draft in missive. use after preparing message details to save a draft (email, sms, whatsapp, or live chat) for later editing or scheduling.
Why this helps
A useful policy can be overlooked if publishing its page is treated as the final communication step.
- Colleagues receive a concise explanation alongside the source page.
- The message can call out who is affected and what action is expected.
Setup
Build it in a few focused steps.
- 1Connect Notion and Missive to Notis once through the portal.
- 2Create an automation and write one instruction for introducing new policy pages in a Missive draft.
- 3Choose Page Created and scope it to the policy section or data source.
- 4Set a channel for run reports and test with one real policy page.
Questions about this workflow
Can I use this for only the policy area?
Scope Page Created to the policy data source or its parent page.
Will it publish or send the policy?
The workflow creates a Missive draft that a person can review and send.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Missive. A trigger fires from one place; an action lands in another.
Notion triggers
Missive actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Analytics Report
Tool to create an analytics report. use when you need to generate a report over a specific time range with optional filters. returns a report id for later retrieval.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Draft
Tool to create a new draft in missive. use after preparing message details to save a draft (email, sms, whatsapp, or live chat) for later editing or scheduling.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Send Missive Message
Tool to send a new message in a missive conversation. use after selecting the target conversation 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.
Create Webhook
Tool to create a webhook subscription. use after choosing event type and target url.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Webhook
Tool to delete a webhook subscription by webhook id. use after confirming the webhook id; this operation cannot be undone.
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 Team Members
Tool to list members of a team. use when you need to retrieve all members for a specific team.
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.
List Missive Teams
Tool to list all teams. use when you need to retrieve and enumerate all teams available in missive.
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.
List Missive Users
Tool to list all users. use after authentication when you need to retrieve all users in the organization.
Connect any two apps with Notis in the middle.
Notion and Missive, 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 Missive.