Keep feedback follow-up connected to exports
A new comment can create a follow-up thread. A Cloudpress export snapshot gives you related activity to review while the context is fresh.
Trigger
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.
Action
List Document Exports
Tool to retrieve a paginated list of document exports. use after initiating export jobs to fetch export history.
Why this helps
Feedback can be hard to act on when it arrives in one place and publishing history sits elsewhere.
- Check export history when feedback arrives
- Keep feedback and activity review in one run
- Lower the effort of resuming a thread
Setup
Build it in a few focused steps.
- 1Connect Notion and Cloudpress to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally for an export-history report when a Notion comment is created.
- 3Use one plain-language instruction to retrieve recent Cloudpress exports and summarize them with the comment context.
- 4Choose the Notion Comment Created trigger and a channel for run reports.
- 5Test by adding one real comment and checking the report.
Questions about this workflow
Does this require a Notion permission?
Comment events require the Notion integration to have Read comments capability; an older connection may need re-authorization after enabling it.
Does the comment start a publishing action?
No. The Cloudpress action lists document exports for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cloudpress. A trigger fires from one place; an action lands in another.
Notion triggers
Cloudpress actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account Information
Tool to retrieve authenticated account information. use after authentication to get current account details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Connections
Tool to list all connections with pagination. use when you need to retrieve cloudpress connections page by page with optional filters like kind, type, or sourcereference.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Document Exports
Tool to retrieve a paginated list of document exports. use after initiating export jobs to fetch export history.
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 Webhooks
Tool to retrieve a paginated list of webhooks. use when you need an overview of all configured webhooks.
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 Cloudpress, 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 Cloudpress.