Capture Product Reviews Without Site-Hopping
Update a product note in Notion and get fresh reviews from G2, Capterra, and ProductHunt scraped automatically. No tab-switching needed.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
Why this helps
Founders evaluate products by hand, context-switching between review sites. By the time they compile notes, ratings have changed.
- Captures reviews at the moment you're evaluating
- Reduces tab-switching and cognitive load
- Keeps comparison data current without re-searching
Setup
Build it in a few focused steps.
- 1Connect your Notion workspace and Agentql to Notis.
- 2Create this automation: 'When I update a product page in my Product Research database, scrape G2, Capterra, and ProductHunt for the latest review count, average rating, and top customer complaints. Append to the page.'
- 3Set the trigger to 'Page Content Updated' on your Product Research database and choose your channel.
- 4Test by editing one product page and verify reviews pull in.
- 5Customize if you want different review sites or specific focus areas (e.g., 'only grab pricing feedback').
Questions about this workflow
Does it get the actual review text or just ratings?
You can request either. Ask Notis for full review snippets or just aggregate scores - your call.
How current is the data?
It pulls what's live on those sites at the moment the automation runs, so you get the latest published reviews.
What if a product doesn't exist on all review sites?
Notis will report which sites have it and which don't. Very new or niche products may only appear on one or two platforms.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Agentql. A trigger fires from one place; an action lands in another.
Notion triggers
Agentql actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Usage Details
Tool to retrieve subscription usage details for the current api key, including usage limits and billing period. use after confirming api connection is valid.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Remote Browser Session
Tool to create a remote browser session. use when you need to run browser automation on remote infrastructure.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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 Agentql, 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 Agentql.