Skip to content
Notis

Answer software questions raised in Notion comments

A teammate asks about an option in a Notion thread. Notis can search Capterra and bring back a focused answer without losing the conversation.

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

Search software

capterra.com API

Why this helps

Questions buried in comments can be easy to miss, especially when answering requires a separate research session.

  • Makes a software question a clear research starting point.
  • Returns findings in the context of the discussion.
  • Helps close small research loops before they turn into lingering threads.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Capterra to Notis once in the portal, and ensure the Notion connection can read comments.
  • 2Create an automation with a single instruction to search Capterra when a Notion comment asks about software and add a brief answer to the discussion context.
  • 3Select the Notion Comment Created trigger and choose a channel for run reports.
  • 4Test by adding one real software question as a comment and check the response.

Questions about this workflow

Does the Notion connection need comment access?

Yes. The integration needs the Read comments capability, and a connection authorized before that capability was enabled may need to be re-authorized.

Will it search on every comment?

The trigger fires for new comments the integration can access. The prompt should explain how Notis should recognize a software question.

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.