See client reviews when an agency enters your shortlist
New candidate added? Have Notis retrieve the agency's Clutch reviews so feedback is part of the first pass, not a forgotten follow-up.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Get agency reviews
clutch.co API
Why this helps
Review research often falls to the bottom of a busy founder's list after the candidate has already been added.
- Bring client feedback into the first candidate review.
- Avoid a separate reminder to check reviews later.
- Make provider research easier to pick back up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Clutch to Notis once through the portal.
- 2Create an automation in the portal, or tell Notis conversationally what result you want.
- 3Ask Notis in one plain-language instruction to retrieve Clutch reviews for each new agency candidate page.
- 4Choose the Notion Page Created trigger and a channel for run reports.
- 5Test with one real candidate page and check the retrieved reviews.
Questions about this workflow
What information should the candidate page contain?
Add the agency name or another clear identifier so Notis can find the corresponding Clutch listing.
Does this recommend or approve an agency?
No. It retrieves reviews to support your own evaluation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Clutch. A trigger fires from one place; an action lands in another.
Notion triggers
Clutch actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Search agencies
clutch.co API
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List service categories
clutch.co API
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get agency portfolio
clutch.co API
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 agency reviews
clutch.co API
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get agency locations
clutch.co API
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 agency profile
clutch.co API
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 Clutch, 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 Clutch.