Understand how often users repeat a behavior
Update product notes and have Notis check how frequently users perform the related event, giving prioritization a useful view of usage habits.
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
Query Frequency Report
Get data about how frequently users are performing events. the query api has a rate limit of 60 queries per hour and a maximum of 5 concurrent queries. example response with unit="day" and addiction unit="hour": { "2012-01-01": [305, 107, 60, 41, ...], # users who did event in 1+ hours, 2+ hours, etc. "2012-01-02": [495, 204, 117, 77, ...], "2012-01-03": [671, 324, 176, 122, ...] }
Why this helps
Frequency questions can linger in planning discussions because the relevant report takes effort to find.
- Bring frequency patterns into ongoing product discussions.
- Check whether an event is a one-time or repeated behavior.
- Reduce manual report searches during prioritization.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mixpanel to Notis once through the portal.
- 2Create a Usage frequency review automation and write one instruction asking Notis to identify the event in the edited notes, query its frequency report, and summarize the pattern.
- 3Choose Page Content Updated and scope it to product-notes pages.
- 4Choose a run-report channel and test by editing one real product-notes page.
Questions about this workflow
What does the frequency report measure?
It reports how frequently users perform events, with activity grouped by time units.
How can I avoid runs on unrelated edits?
Scope the content-update trigger to the product-notes data source or a specific page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mixpanel. A trigger fires from one place; an action lands in another.
Notion triggers
Mixpanel actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Aggregated Event Property Values
Get unique, total, or average data for a single event and property over days, weeks, or months. the query api has a rate limit of 60 queries per hour and a maximum of 5 concurrent queries.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Aggregate Event Counts
Get aggregate event counts over time. supports different types of aggregation: general, unique, average, sum.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Aggregate Events
Get aggregate event counts over time. supports different types of aggregation: general, unique, average, sum.
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 All Projects
Get all projects associated with the authenticated mixpanel account. returns project details including name, permissions, role, domain, and other configuration details.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Execute JQL Query
Execute a custom jql (javascript query language) query against mixpanel's query api. key constraints: - 60 queries/hour, max 5 concurrent queries. - 2-minute execution timeout. - 5 gb data processing limit, 2 gb output limit. - no remote network requests (xmlhttprequest) are allowed inside the jql script.
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.
List Saved Cohorts
Get list of all cohorts in a mixpanel project. returns cohort details including name, id, count, description, creation date, and visibility. the query api has a rate limit of 60 queries per hour and a maximum of 5 concurrent queries.
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.
List Saved Funnels
Get the names and funnel ids of your funnels. the query api has a rate limit of 60 queries per hour and a maximum of 5 concurrent queries.
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.
Get Profile Event Activity
Get event activity feed for specified users from mixpanel query api. the query api has a rate limit of 60 queries per hour and a maximum of 5 concurrent queries.
Connect any two apps with Notis in the middle.
Notion and Mixpanel, 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 Mixpanel.