Skip to content
Notis

Add Capterra product details to each new decision record

As a product enters the decision database, gather a product reference alongside it so the next review starts with context.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

Get product detail

capterra.com API

Why this helps

New decision records can become a list of names without the supporting product information needed to evaluate them.

  • Adds product context when a decision record is created.
  • Makes later evaluation easier to resume.
  • Reduces repetitive lookups across multiple records.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Capterra to Notis once in the portal.
  • 2Create an automation and state in one instruction how a new decision record should retrieve Capterra product detail for its product.
  • 3Select the Notion New Page trigger for the decision database and choose a channel for run reports.
  • 4Test with one real product record and verify the correct detail is attached.

Questions about this workflow

Does it work with a database row?

A new page added to the selected Notion database can start the workflow.

Can it compare several products?

This workflow retrieves product detail for the new record. Compare multiple records in your own decision process.

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.

TriggerScheduled

List software categories

capterra.com API

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get product detail

capterra.com API

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

List category products

capterra.com API

ActionInstant

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.

TriggerInstant

Get product reviews

capterra.com API

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Search software

capterra.com API

ActionInstant

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.

TriggerInstant

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.

TriggerInstant

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.

TriggerInstant

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.