Turn a competitor watchlist into a domain comparison
When a research system sends a watchlist, use Notion's context to request a batch analysis and keep comparison moving.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Batch Target Analysis
Get Domain Rating, backlinks, and traffic metrics for up to 100 targets at once.
Why this helps
Competitor lists arrive through different routes, leaving a founder to copy targets into repeated lookups.
- Accept an external watchlist through a Notis webhook.
- Compare Domain Rating, backlinks, and traffic in one action.
- Support batches up to 100 targets.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ahrefs to Notis once.
- 2Create an automation with one prompt explaining how a received competitor list should be analyzed using its Notion context.
- 3Choose an incoming webhook trigger and a channel for run reports.
- 4Test with one real watchlist example and review the Ahrefs batch results.
Questions about this workflow
What starts this workflow?
An external tool or custom backend sends an HTTP request to the Notis webhook.
How large can a batch be?
Ahrefs batch target analysis supports up to 100 targets.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ahrefs. A trigger fires from one place; an action lands in another.
Notion triggers
Ahrefs actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Related Keywords
Find keywords related to seed terms, with volume and difficulty.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Pages by Internal Links
List a target's pages ordered by incoming internal link counts.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Organic Keywords
List keywords a target ranks for with position, volume, and traffic estimates.
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.
Domain Rating History
Track a target's Domain Rating over time, one row per date bucket.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Backlink Anchors
Break down a target's backlinks by anchor text with referring-domain counts.
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.
Batch Target Analysis
Get Domain Rating, backlinks, and traffic metrics for up to 100 targets at once.
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 Ahrefs, 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 Ahrefs.