Listen to Customer Voice Without Manual Scraping
Flag a product for urgent improvement in Notion and automatically pull what customers are complaining about from G2, Trustpilot, and ProductHunt. Know what to fix.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
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
Teams improve products based on gut feel instead of customer feedback. Reviews are scattered across sites and get overlooked.
- Grounds product decisions in actual customer feedback
- Aggregates feedback across multiple review platforms
- Surfaces patterns in complaints without manual reading
Setup
Build it in a few focused steps.
- 1Connect Notion and Agentql to Notis.
- 2Create this automation: 'When I update a product status to Urgent Improvement, scrape G2, Trustpilot, and ProductHunt for the most recent negative reviews and common complaints. Extract the top 5 pain points and feature requests.'
- 3Set trigger to 'Page Properties Updated' on your Products database (filtering for status = Urgent Improvement) and choose your channel.
- 4Test by flagging one product and verify customer feedback appears.
- 5Customize to focus on specific themes (e.g., 'extract only complaints about onboarding' if that's your focus).
Questions about this workflow
Can it extract the review text or just themes?
Both - it can pull direct quotes from negative reviews and summarize common themes so you see patterns.
Does it separate feedback by customer size or industry?
Reviewers often mention their company type. Agentql can filter (e.g., 'show me complaints from enterprise customers only').
How long does it take to compile this?
Usually 1-2 minutes to scrape all three sites. You'll get a report when complete.
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.