Bring review evidence into the next evaluation step
When an option advances in your evaluation, gather customer feedback at the same time so the next decision has useful evidence to work with.
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 product reviews
capterra.com API
Why this helps
A product may move closer to selection while review evidence remains an unfinished task with no clear reminder.
- Pairs evaluation progress with relevant review evidence.
- Makes the next decision step easier to prepare.
- Helps surface customer experience before commitment.
Setup
Build it in a few focused steps.
- 1Connect Notion and Capterra to Notis once in the portal.
- 2Create an automation with a single instruction to retrieve Capterra reviews when a product evaluation status changes and add a concise evidence summary.
- 3Select the Notion Page Properties Updated trigger for the evaluation data source and choose a run-report channel.
- 4Test by changing one real status and reviewing the returned reviews.
Questions about this workflow
Will every property update run it?
The trigger fires for property updates in the selected data source. The prompt can guide how Notis uses the change information.
Does this select a winning product?
No. It provides customer feedback to inform your evaluation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Capterra. A trigger fires from one place; an action lands in another.
Notion triggers
Capterra actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List software categories
capterra.com API
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get product detail
capterra.com API
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List category products
capterra.com API
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 product reviews
capterra.com API
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Search software
capterra.com API
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 Capterra, 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 Capterra.