Review event properties after a schema change
When a tracking-related schema changes in Notion, ask Notis to check the matching Mixpanel event's top properties and report the available analytics context.
Trigger
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.
Action
Get Top Event Properties
Get the top property names for an event. the query api has a rate limit of 60 queries per hour and a maximum of 5 concurrent queries.
Why this helps
Tracking documentation can change without a quick check of whether the event properties needed for analysis are present.
- Prompt an event-property inventory after a schema update.
- Spot whether the expected properties appear in Mixpanel.
- Reduce the chance that documentation changes go unreviewed.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mixpanel to Notis once through the portal.
- 2Create a Schema property check automation and write one instruction asking Notis to identify the related event from the updated schema and retrieve its top Mixpanel properties.
- 3Select Data Source Schema Updated and scope it to the tracking documentation data source.
- 4Choose a run-report channel and test by making one real schema update.
Questions about this workflow
Does the automation inspect Notion columns directly?
The trigger indicates a schema update. The instruction should use the available update context to identify the related Mixpanel event.
What does Mixpanel return?
The action returns top property names for an event, which can help review tracking coverage.
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.