Skip to content
Notis

Bring behavior data into customer journey work

When a new subpage is added to a journey workspace, cue a Clarity export to make behavioral evidence part of the review routine.

Trigger

Page Added to Page

Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.

Action

Data Export

Export data from microsoft clarity.

Why this helps

Journey documentation grows over time, while analytics checks can remain an informal step people forget to schedule.

  • Builds a consistent analytics cue into journey documentation.
  • Helps teams gather behavior evidence near the relevant work.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Microsoft Clarity to Notis once.
  • 2Create a new automation in the portal or explain the workflow to Notis conversationally.
  • 3Write one prompt asking for a relevant Clarity export when a subpage is created under the chosen journey page.
  • 4Choose the Notion Page Added to Page trigger and select the parent page.
  • 5Test by adding one real journey subpage and reviewing the report.

Questions about this workflow

Does it watch every page in the workspace?

No. This trigger is scoped to new subpages under a specified parent page.

Can it focus on one journey stage?

Describe the intended stage or context in the prompt so Notis can prepare a relevant report.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Microsoft clarity. A trigger fires from one place; an action lands in another.

Notion triggers

Microsoft clarity actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Data Export

Export data from microsoft clarity.

ActionInstant

Webhook trigger

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

TriggerInstant

All Page Events

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

TriggerPolling

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

New Comment

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

TriggerPolling

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

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 Microsoft clarity, 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 Microsoft clarity.