Follow up on software feature questions in comments
A comment can capture a useful question and prompt a GetApp feature lookup while it is still fresh.
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
Get software features
Search and compare software solutions while accessing detailed information like pricing, features, integrations, reviews, and alternatives all in one place. Get category leaders, read industry research from their blog, and make informed software decisions based on comprehensive data.
Why this helps
Questions in comments are easy to miss when nobody turns them into a separate research task.
- Turns discussion into a concrete research action.
- Reduces forgotten follow-up questions.
- Keeps feature investigation close to the conversation.
Setup
Build it in a few focused steps.
- 1Connect Notion and GetApp to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language.
- 3In one instruction, ask Notis to research in GetApp the software feature questions raised in comments.
- 4Select Notion's Comment Created trigger, choose a run-report channel, and ensure the Notion connection has Read comments enabled.
- 5Test with one real comment on a research page and review the result.
Questions about this workflow
Does this require a special Notion capability?
Yes. The Notion integration needs Read comments enabled, and older connections may need re-authorization.
Can it monitor any page?
The trigger can fire for comments in the workspace accessible to the integration; an optional page filter can narrow it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to GetApp. A trigger fires from one place; an action lands in another.
Notion triggers
GetApp actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get software features
Search and compare software solutions while accessing detailed information like pricing, features, integrations, reviews, and alternatives all in one place. Get category leaders, read industry research from their blog, and make informed software decisions based on comprehensive data.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get software pricing
Search and compare software solutions while accessing detailed information like pricing, features, integrations, reviews, and alternatives all in one place. Get category leaders, read industry research from their blog, and make informed software decisions based on comprehensive data.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get software alternatives
Search and compare software solutions while accessing detailed information like pricing, features, integrations, reviews, and alternatives all in one place. Get category leaders, read industry research from their blog, and make informed software decisions based on comprehensive data.
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 software integrations
Search and compare software solutions while accessing detailed information like pricing, features, integrations, reviews, and alternatives all in one place. Get category leaders, read industry research from their blog, and make informed software decisions based on comprehensive data.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Compare software
Search and compare software solutions while accessing detailed information like pricing, features, integrations, reviews, and alternatives all in one place. Get category leaders, read industry research from their blog, and make informed software decisions based on comprehensive data.
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.
Get category leaders
Search and compare software solutions while accessing detailed information like pricing, features, integrations, reviews, and alternatives all in one place. Get category leaders, read industry research from their blog, and make informed software decisions based on comprehensive data.
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 GetApp, 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 GetApp.