Keep usability findings connected to behavior data
A new or revised usability observation can cue a Clarity export, helping you compare what people report with what visitors do.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Data Export
Export data from microsoft clarity.
Why this helps
Usability findings can lead to further questions, but collecting behavior data adds another task after synthesis.
- Prompts a timely comparison between usability notes and visitor behavior.
- Reduces the number of manual steps after research synthesis.
Setup
Build it in a few focused steps.
- 1Connect Notion and Microsoft Clarity to Notis once.
- 2Create a new automation in the portal or describe it to Notis conversationally.
- 3Write one prompt asking for a Clarity export when relevant usability findings change and how to report it.
- 4Choose the Notion Page Content Updated trigger and scope it to the findings page or data source.
- 5Test by updating one finding and checking the result.
Questions about this workflow
Can this watch the whole findings database?
Yes. Use the data source scope when selecting the Page Content Updated trigger.
Does it interpret the finding as verified behavior?
The export supplies behavior data for review; the team decides how it relates to the finding.
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.
Data Export
Export data from microsoft clarity.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 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.