Skip to content
Notis

Move open software research forward each week

A small weekly pass can bring Capterra options back to the open Notion items that otherwise wait for a quiet afternoon.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

Action

Search software

capterra.com API

Why this helps

Unfinished research can sit in a backlog because there is no obvious moment to pick it up again.

  • Gives unresolved software needs a predictable follow-up.
  • Brings search results back without relying on memory.
  • Helps keep the research queue bounded.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Capterra to Notis once in the portal.
  • 2Create an automation with one instruction to find open software research in Notion and search Capterra for entries still needing options.
  • 3Choose a weekly schedule for the trigger and select a channel for run reports.
  • 4Test with one real open research item and confirm it is represented in the results.

Questions about this workflow

How often does it run?

Choose a weekly schedule when creating the automation.

Can it close or prioritize backlog items?

The prompt can ask for a concise research result. Review and update your own backlog status as needed.

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.