Skip to content
Notis

Resolve location questions in vendor discussions

If a comment on your vendor page raises a location question, Notis can retrieve the agency's Clutch locations for review.

Trigger

New Comment

Triggers when a new comment is added to a specified Notion block or page.

Action

Get agency locations

clutch.co API

Why this helps

A small location question can lead to a distracting search and a delayed decision when no one owns the follow-up.

  • Turn a location question into a focused lookup.
  • Keep research tied to the vendor page discussion.
  • Reduce the need to switch tools for basic provider details.

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 locations when a location question is raised in a comment on the vendor page.
  • 4Choose the Notion New Comment trigger for the relevant page and a channel for run reports.
  • 5Test with one real location-related comment and review the result.

Questions about this workflow

Can the trigger be limited to one page?

Yes. The New Comment trigger can be scoped to a specified Notion block or page.

What does the action return?

It retrieves the agency location information available from Clutch.

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.

TriggerScheduled

Search agencies

clutch.co API

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

List service categories

clutch.co API

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Get agency portfolio

clutch.co API

ActionInstant

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.

TriggerInstant

Get agency reviews

clutch.co API

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Get agency locations

clutch.co API

ActionInstant

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.

TriggerInstant

Get agency profile

clutch.co API

ActionInstant

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.

TriggerInstant

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.

TriggerInstant

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.