Mixpanel
Bring your business data together in Mixpanel, and act on it in the apps your team already uses.
11 ways to read, 5 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Mixpanel, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Import events in bulk
event_batches.createApproval by rule - Record an event
events.createApproval by rule - List annotations
annotations.listRead
Example flow
- Mixpanel · List annotations
annotations.listDone - Mixpanel · Import events in bulk
event_batches.createMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Mixpanel.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Mixpanel
- Mixpanel's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Mixpanel test account before you go live.
For developers
Technical detail
Mixpanel: send events and profile updates from any app, and read raw events, saved reports, funnels, retention, cohorts and profiles back.
Mixpanel API docs- Source actions
- 11
- Destination actions
- 5
- Data types
- 14
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
annotations1
- List annotationsSource
Notes your team added to Mixpanel charts (for example a release or campaign launch), with their dates.
cohorts1
- List cohortsSource
Lists the saved cohorts in the project with their size.
event batches1
- Import events in bulkDestinationProvider duplicate protectionApproval before production
Imports up to 2,000 events in one request, for backfills and nightly loads.
event names1
- List event namesSource
The event names used in the project over the last 31 days.
events2
- Record an eventDestinationProvider duplicate protectionApproval before production
Sends one event (for example Order placed) to Mixpanel with the person, time and properties you map.
- Export raw eventsSourceIncremental
Reads raw events between two dates (for example every Order placed yesterday), with all their properties.
funnel results1
- Run a saved funnelSource
Conversion through a saved funnel for each day, week or month: people entering, completing and the conversion rate.
funnels1
- List saved funnelsSource
Lists the funnels saved in the project with their IDs.
group profiles1
- Update a group profileDestinationProvider duplicate protectionApproval before production
Sets properties on a group (for example a company account) for Mixpanel group analytics.
insights results1
- Run a saved Insights reportSource
Runs an Insights report you saved in Mixpanel and returns one row per metric, breakdown and date.
retention results1
- Get retentionSource
How many people came back after their first event (for example Signed up), for each starting day, week or month.
segmentation results1
- Count an event over timeSource
How many times an event happened (or how many people did it) each day, hour or month, optionally broken down by a property.
top events1
- Today's top eventsSource
The most common events today, with the change against the usual level.
user profile batches1
- Update user profiles in bulkDestinationProvider duplicate protectionApproval before production
Sets properties on up to 2,000 Mixpanel user profiles in one request.
user profiles2
- Find user profilesSource
Reads user profiles with their properties: everyone, one person, a cohort or those matching a filter.
- Update a user profileDestinationProvider duplicate protectionApproval before production
Sets properties (for example email, name or plan) on one person's Mixpanel profile, creating the profile if needed.
Access and limits
- Authentication
- Mixpanel service account
- Plans and access
- Any Mixpanel plan, including Free. Group profiles need the Group Analytics add-on; events count toward the plan's monthly volume. A service account (Owner or Admin role to import events) for the project. Projects on EU or India data residency must choose that region.
- Test environment
- Mixpanel has no separate sandbox. Create a second project (for example 'Nexra test') in the same organisation and connect to it first.
- Rate limits
- Import: 2 GB of events a minute (about 30,000 events a second); 2,000 events or 10 MB per request. Query API: 60 queries an hour, 5 at a time. Raw export: 60 an hour, 3 a second, 100 at a time. Mixpanel answers 429; Nexra waits and retries.
- Pagination
- Raw exports are JSON Lines read in pages of up to 1,000 events; profile searches page by session and page number (1,000 a page); reports return one result.
- Provider events
- Mixpanel can push cohort membership to a custom webhook destination (Cohort Syncs); it has no event or report webhooks. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Intentionally excluded: deleting events or profiles (GDPR deletion), $unset and list removals on profiles, lookup table replacement, cohort and project administration, JQL.
- Reads that need the project API secret in the address are not offered; every call uses the service account over HTTP Basic.
- The Query and Export APIs allow 60 calls an hour per project, so schedule report reads hourly or less often.
- Raw exports filter by the event's own time in whole days; events imported later with an older time are only picked up within the one-day overlap.
- Funnel and segmentation queries use APIs Mixpanel keeps in maintenance mode; prefer saving the chart as an Insights report.
- Profile updates use the project token saved on the connection (a public identifier); Mixpanel answers 1 even when the token is wrong, so check the first update in Mixpanel.
Developer reference
- Create the Mixpanel credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Mixpanel, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/mixpanel and the Connections API.