Keep behavior evidence near changing priorities
When a Notion priority changes, a Clarity export can help you revisit user behavior with the new focus in mind.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Data Export
Export data from microsoft clarity.
Why this helps
A priority shift often means revisiting evidence, but remembering to gather it competes with the work of updating plans.
- Adds a consistent evidence-gathering cue to priority updates.
- Makes it easier to bring user behavior into a planning conversation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Microsoft Clarity to Notis once.
- 2Create a new automation in the portal or ask Notis conversationally.
- 3Write one plain-language prompt describing the priority changes that should prompt a Clarity data export and how to report it.
- 4Choose the Notion Page Properties Updated trigger and a channel for run reports.
- 5Test with one real priority update in Notion.
Questions about this workflow
Can this respond only to a particular priority property?
Describe the intended change in the prompt; Notis interprets the instruction rather than using a field-mapping screen.
Will the export update my Notion record?
The listed action exports Clarity data. Any additional handling should be described in the prompt and confirmed in the run 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.
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.