Track Competitor Reputation Without Manual Searches
Add a competitor to track in Notion and automatically search news, blogs, Reddit, and forums for mentions. Know what people are saying about them.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Remote Browser Session
Tool to create a remote browser session. use when you need to run browser automation on remote infrastructure.
Why this helps
Founders want competitive intelligence but manually Googling competitors is tedious. Reputation changes get missed.
- Tracks competitor reputation automatically across multiple sources
- Alerts you to news that affects your strategy
- Saves time on manual brand searches
Setup
Build it in a few focused steps.
- 1Connect Notion and Agentql to Notis.
- 2Create this automation: 'When I add a new competitor to my Competitor Tracking database, use a browser to search Google News, Reddit, and tech blogs for recent mentions. Capture headlines, sentiment, and publication dates.'
- 3Set trigger to 'New Page' in your Competitor Tracking database and choose your channel.
- 4Test by adding one competitor and let the browser session complete (usually 1-2 minutes).
- 5Customize search terms if needed (e.g., 'search for [competitor name] + negative phrases to flag PR issues').
Questions about this workflow
Can it assess sentiment of mentions or just pull links?
Agentql can read the content and flag positive vs negative mentions, so you see reputation trends.
Does it track historical mentions or just current?
Each run captures current mentions. Set up a weekly cron to build a time series and see if reputation is trending up or down.
What if a competitor has a common name?
Refine your instruction to include their domain or tagline (e.g., 'search for [Company] + [tagline]') to filter noise.
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.