Frame a new software research view with Capterra categories
When you create a focused view for a new research area, bring in the categories that can help you define what belongs there.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
List software categories
capterra.com API
Why this helps
New tracking views can create structure without clarifying the market or software types the founder means to explore.
- Pairs new research structure with category context.
- Helps clarify the scope of a software exploration area.
- Reduces setup gaps between organizing and researching.
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 use a newly created research view's context to list relevant Capterra categories.
- 3Select the Notion View Created trigger and choose a channel for run reports.
- 4Test by creating one real research view and check whether the category list fits its purpose.
Questions about this workflow
Does every view type trigger this?
The trigger fires when a Notion view is created, with the view type available in its event data.
What if the view name is vague?
Use a clear name or surrounding research context so the prompt can identify the category area.
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.