Mattering Automations Mixpanel integration
Connect Mixpanel to Mattering Automations: segmentation, funnels, retention, Insights reports, profiles, JQL, raw export, and event import as workflow steps, authenticated with a Mixpanel service account.
The Mattering Automations Mixpanel integration adds Mixpanel to your automation canvas: segment events over time with sums and averages, query saved funnels, retention, and Insights reports, pull user profiles and cohorts, discover event names and properties, run JQL scripts, export raw events, create chart annotations as deploy markers, and send events into Mixpanel from workflows.
Setup takes a few minutes: create a service account in Mixpanel's Organization Settings, attach it as a credential in Mattering, and test the connection. This guide walks through each step and ends with the full node reference.
The safety posture is simple to state: of the 23 nodes, 20 are pure reads and the 3 writes only add or update, so nothing in this integration can delete or destroy analytics data. Mixpanel: Verify Credential (List Accessible Projects) doubles as the connection test and as the lookup for the project ids that every query node requires.
Before you start
- A Mixpanel account with at least one project. Mixpanel's free plan includes the Query API and service accounts, so a free project is enough to test with.
- Access to Organization Settings in Mixpanel, where service accounts are created.
- A Mattering workspace with access to the Automations app.
- A project on Mixpanel's US data residency. This version of the integration covers the US hosts only; EU and India residency projects are not supported yet.
Create a Mixpanel service account
Mattering authenticates to Mixpanel with a service account: a username and secret pair sent as HTTP Basic auth on every request. Service accounts belong to the organization with per-project roles, which is why each query node names its target project explicitly.
Connect Mixpanel to Mattering
Verify it works
After connecting, open any automation canvas and check the palette: a Mixpanel section should list the query and action nodes. Drop Mixpanel: Verify Credential (List Accessible Projects) onto the canvas and run a test step. It takes no parameters, is a pure read, and does not count against the query rate limit; a successful response lists the organization, projects, and workspaces the service account can reach. Note the project ids in that response: every query node requires a project_id, and this is the easiest place to find them.
To confirm the query surface, run Mixpanel: List Event Names with one of those project ids, which returns the events tracked over the last 31 days, then Mixpanel: Get Today's Top Events for a first real read with counts. Everything in the verify path is read-only, and nothing anywhere in this integration can delete Mixpanel data.
Node reference
23 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 20
Mixpanel: Average a Numeric Expression
mixpanel_query_segmentation_average
Average a numeric property expression across one event per time bucket, e.g. average order value per day. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Export Raw Events
mixpanel_export_events
Download raw event records (every tracked event with all its properties) for a date range from Mixpanel's export cluster. WARNING: unfiltered exports can be enormous; always set limit (server cap 100,000 events) and keep date ranges tight, because the full result is stored in the execution record. The response is newline-delimited JSON, which this node parses into an events array for downstream steps. Export budget: 60 queries per hour, 3 per second.
Mixpanel: Get Event Counts Over Time
mixpanel_query_event_counts
Get counts for one or MORE events bucketed over time in a single call: the simplest multi-event trend read (segmentation handles one event with property breakdowns). Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Get Today's Top Events
mixpanel_query_top_events
Get today's top events by volume, each with its count and the percent change from yesterday. A quick daily pulse read for digest or alerting automations. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: List Annotations
mixpanel_list_annotations
List the chart annotations on a project (release markers, campaign launches, incidents), optionally windowed by date. Each annotation carries its id, timestamp, description, author, and tags.
Mixpanel: List Cohorts
mixpanel_list_cohorts
List the project's saved cohorts with id, name, description, current member count, and visibility. Feed a cohort id into the Query Profiles node's filter_by_cohort to pull the members. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: List Event Names
mixpanel_list_event_names
List the names of events tracked in the project over the last 31 days, for discovering what can be queried. Returns a plain array of event name strings. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: List Lexicon Schemas
mixpanel_list_lexicon_schemas
Read the project's Lexicon data dictionary: every uploaded schema for events and profile properties, with names, entity types, descriptions, and property definitions. Useful for schema discovery before building queries.
Mixpanel: List Saved Funnels
mixpanel_list_saved_funnels
List the project's saved funnels with their funnel_id and name, for feeding the funnel query node. Note: Mixpanel keeps the Funnels endpoints in maintenance mode and recommends the Insights query node for new work; this still works and is the only way to enumerate funnel IDs. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: List Top Properties of an Event
mixpanel_list_top_event_properties
List the most common property names on one event, with a count for each: the schema-discovery step before segmenting on a property. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: List Top Values of an Event Property
mixpanel_list_event_property_values
List the most common values of one property on one event, as a plain array of strings. Pairs with the top-properties node to map an event's schema before querying. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Query Retention
mixpanel_query_retention
Get cohort retention data: for each cohort start date, the size of the cohort and how many returned in each subsequent time bucket. Supports first-time (birth) and recurring (compounded) retention. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Query User Profiles
mixpanel_query_profiles
Query user (or group) profiles: fetch by distinct_id, filter with a where expression, or pull a cohort's members via filter_by_cohort. Pages of up to 1,000 profiles; to get the next page, send back the returned session_id and increment page, keeping the same filters. Profile data is personal data and persists in execution records; select only the properties you need with output_properties. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Query a Saved Funnel
mixpanel_query_funnel
Get per-step conversion data for a saved funnel over a date range: step counts, step and overall conversion ratios, and average times between steps. Note: maintenance mode; Mixpanel recommends building a funnel in Insights and using the Insights query node for new work. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Query a Saved Insights Report
mixpanel_query_insights
Pull the computed data of a saved Insights report by its bookmark ID (the number in the report URL). This is Mixpanel's recommended programmatic path for report data, including funnel reports built in the UI. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Run a JQL Query
mixpanel_run_jql
Run a custom JQL script (Mixpanel's JavaScript query language) against the project's events and profiles. The script executes inside Mixpanel's sandbox, can only READ analytics data, and cannot make network requests; results come back as a JSON array. Limits: 2 minutes of runtime, 5 GB scanned, 2 GB output. Note: JQL is in maintenance mode; prefer the typed query nodes when one fits. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Segment an Event
mixpanel_query_segmentation
The workhorse analytics read: count one event over time, optionally filtered with a where expression and broken down by a property expression (on). Returns a date series per segment value. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Segment an Event by Property Values
mixpanel_query_event_properties
Count one event over time broken down by the values of one named property, optionally restricted to specific values. The simpler cousin of the segmentation node when you have a plain property name rather than an expression. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Sum a Numeric Expression
mixpanel_query_segmentation_sum
Sum a numeric property expression across one event per time bucket, e.g. total revenue per day from a purchase event's amount property. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Verify Credential (List Accessible Projects)
mixpanel_get_me
Confirm the service account credential works and see which organization, projects, and workspaces it can reach. Takes no parameters and does not count against the query rate limit, so it doubles as the credential health check and as the way to look up project IDs for the other nodes.
Action nodes 3
Mixpanel: Create Annotation
mixpanel_create_annotation
Add a chart annotation to a project, e.g. mark a deploy, a campaign start, or an incident so it shows on every Mixpanel chart at that timestamp. Requires the service account to hold an Analyst role or higher on the project. Reversible: an annotation can be deleted in the Mixpanel UI.
Mixpanel: Import Events
mixpanel_import_events
Send events INTO Mixpanel from an automation (server-side tracking) using the same service account credential as the query nodes. Each event needs an event name plus properties with time, distinct_id, and a $insert_id for deduplication. Up to 2,000 events per call. Note: imported events cannot be deleted through this connector, so point test runs at a throwaway project or a clearly named test event.
Mixpanel: Set User Profile Properties
mixpanel_update_profile
Set (create or overwrite) properties on one user profile. NOTE ON CREDENTIALS: Mixpanel's profile ingestion authenticates with the project TOKEN (a public identifier from Project Settings, then Access Keys), not the service account, so this node has its own project_token field. Careful: $set OVERWRITES an existing value for each property it names; properties not named are left untouched.
Using the integration
On the automation canvas
Mixpanel nodes chain with every other node: a scheduled Mixpanel: Segment an Event read can land a weekly digest as a report task in Mattering Productivity, a funnel step whose conversion drops against last week can open an investigation task, and Mixpanel: Create Annotation at the end of a release workflow marks the deploy on every Mixpanel chart. There is no inbound Mixpanel trigger in this integration, so the pattern for reacting to analytics is a scheduled sweep: query on a schedule, compare, and route what changed.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can segment events, read funnels and retention, and discover a project's schema through the same nodes your workflows use. With 20 of 23 nodes being pure reads and no destructive node at all, this is one of the safest connectors to hand an agent; the discovery nodes (Mixpanel: List Event Names, Mixpanel: List Top Properties of an Event, Mixpanel: List Top Values of an Event Property, Mixpanel: List Lexicon Schemas) let it learn the schema before querying.
project_id on every query node
Mixpanel service accounts belong to the organization, not to a project, so the API cannot infer which project a query targets: every query node carries a required project_id field. The id comes from Mixpanel: Verify Credential (List Accessible Projects), from Project Settings in Mixpanel, or from the number in the project URL; look it up once and reuse the value across the workflow. Projects using Data Views can also pass the optional workspace_id the query nodes accept.
Funnels, JQL, and maintenance mode
Mixpanel keeps the Funnels endpoints and JQL in maintenance mode and recommends Insights for new work, and the integration says so rather than hiding it. Mixpanel: List Saved Funnels and Mixpanel: Query a Saved Funnel ship because they are the only programmatic path to legacy saved-funnel step data. For new work, build the funnel in the Mixpanel UI and pull it with Mixpanel: Query a Saved Insights Report by its bookmark id, the number in the report URL. Mixpanel: Run a JQL Query runs a custom script entirely inside Mixpanel's sandbox: it can only read analytics data, cannot make network requests, and is limited to 2 minutes of runtime, 5 GB scanned, and 2 GB of output. Prefer the typed query nodes when one fits.
Raw export discipline
Mixpanel: Export Raw Events downloads the underlying event records for a date range from Mixpanel's export cluster. The response is newline-delimited JSON, which the node parses into a normal events array for downstream steps. Unfiltered exports can be enormous, and the full result is stored in the execution record, so always set the limit (the server caps a call at 100,000 events) and keep date ranges tight. The export surface has its own budget of 60 queries per hour at 3 per second, separate from the query budget.
Sending data in: one credential nuance
Mixpanel: Import Events sends events into Mixpanel on the same service account credential as the queries, up to 2,000 events per call, each with a $insert_id for deduplication so retries are safe. Imported events cannot be deleted through this integration, so point test runs at a throwaway project or a clearly named test event. Mixpanel: Set User Profile Properties is the one exception to the single-credential rule: Mixpanel's profile ingestion endpoint has no service account variant and authenticates with the project token, a public identifier from Project Settings under Access Keys, so that node carries its own project_token field. It also overwrites the values of the properties it names, leaving unnamed properties untouched.
Troubleshooting
Test Connection fails with a 401
Test Connection passes but a query node returns a permission error
A query node fails asking for project_id
Queries start failing with rate limit errors
Export Raw Events returns fewer events than expected, or an enormous payload
Set User Profile Properties is rejected or asks for a token
Queries return empty data or 401s even though the project clearly has data
The funnel nodes warn about maintenance mode, or a funnel is missing from the list
Related
The Mixpanel MCP
What connecting Mixpanel unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Mixpanel is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.