Review Campayn messages from your Notion task
Use a Notion review cue to gather your Campayn messages and spend more time on decisions.
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
Get Messages
Tool to retrieve all email messages. use when you need to list all messages visible to the authenticated user.
Why this helps
Switching tools to find campaign messages adds friction to an already busy review routine.
- Reduce context switching during campaign reviews.
- Gather messages in response to a clear review cue.
- Make campaign check-ins easier to finish.
Setup
Build it in a few focused steps.
- 1Connect Notion and Campayn to Notis once through the portal.
- 2Create an automation instructing Notis to retrieve Campayn messages when your Notion review is marked ready.
- 3Choose the Notion Page Properties Updated trigger for the review database.
- 4Select a run-report channel and test with a sample review task.
Questions about this workflow
Does this retrieve message details or send email?
Get Messages retrieves email messages visible to your Campayn account. It does not send an email.
Can I run this as part of a review task?
Yes. Describe the review cue in your instruction and mark the Notion task ready to start it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Campayn. A trigger fires from one place; an action lands in another.
Notion triggers
Campayn actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contact
Tool to create a new contact in a specific list. use when you need to add a contact after gathering details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Contact
Tool to delete a specific contact. use when you need to remove a contact permanently after confirming it should be deleted. example: "delete contact 123".
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete List
Tool to delete a specific contact list. use when cleaning up unused lists after confirming they are no longer needed. example: "delete list 123".
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.
Delete webform
Tool to delete a specific webform. use when removing outdated or unnecessary webforms after confirming they are no longer needed. example: "delete webform 123".
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Contact
Tool to retrieve a specific contact by id. use when you need to fetch full contact details after confirming the contact id.
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.
Get Contacts
Tool to retrieve all contacts in a specified list. use when you need to fetch list contacts after confirming list 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.
Get List
Tool to retrieve a specific contact list by id. use when you need to fetch list details like name, tags, and contact count after knowing the list id.
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 Lists
Tool to retrieve all contact lists. use when you need to fetch available lists before performing list-specific actions. example prompt: "list all my contact lists".
Connect any two apps with Notis in the middle.
Notion and Campayn, 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 Campayn.