Check campaign progress from a review update
When a review note changes, let Notis check the referenced campaign's current processing status so you do not need to switch tools to look it up.
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 Campaign Status
Tool to check the processing status of a submitted campaign. use after submitting a campaign to monitor its progress.
Why this helps
Campaign status can be easy to lose between a planning page and a separate processing tool.
- Bring campaign progress into the review moment
- Reduce manual status lookups
- Make it easier to resume paused campaign work
Setup
Build it in a few focused steps.
- 1Connect Notion and Campaign cleaner to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to create one conversationally.
- 3In one plain-language instruction, ask Notis to check the referenced campaign status when a Notion campaign record is updated.
- 4Choose Page Properties Updated as the trigger and select a channel for run reports.
- 5Test with a real updated record that identifies a campaign.
Questions about this workflow
Will it infer a campaign id if the Notion record does not identify one?
The instruction should reference a campaign clearly enough for Notis to find the intended saved campaign; verify the result in the run report.
Does a status check change the campaign?
No. The Campaign cleaner action checks processing status.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Campaign cleaner. A trigger fires from one place; an action lands in another.
Notion triggers
Campaign cleaner actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Campaign
Tool to delete a saved campaign by id. use when you need to remove a campaign after confirming its id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Campaign List
Tool to list all campaigns in the account. use when you need to retrieve campaign listings for reporting or management.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Download Campaign PDF Analysis
Tool to download a pdf analysis report for a processed campaign. use after a campaign has been processed.
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.
Get Campaign Status
Tool to check the processing status of a submitted campaign. use after submitting a campaign to monitor its progress.
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 Campaign cleaner, 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 Campaign cleaner.