Follow up when comments question a software shortlist
When a comment raises doubt about a shortlisted product, prompt an alternatives search while the question is 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 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.
Why this helps
A concern raised in discussion can be forgotten, leaving the founder to continue with a shortlist nobody has revisited.
- Turns reservations into a clear research follow-up.
- Helps keep decisions open to better-fit products.
- Reduces the burden of remembering unresolved questions.
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 tell Notis the workflow in plain language.
- 3Use one instruction asking for GetApp alternatives when a comment questions a software shortlist.
- 4Select Notion's Comment Created trigger and choose a run-report channel; confirm Read comments access is enabled.
- 5Test with one real shortlist comment and review the alternatives.
Questions about this workflow
Will all comments trigger research?
The workspace-wide Comment Created trigger can fire for any new comment the integration can access. State the relevant shortlist context in your instruction.
Does the integration need to be reconnected?
If Read comments was enabled after authorization, the connection may need to be re-authorized.
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.