Resources · Make integration

Mixpanel Make integrationAutomate Mixpanel with Make.

Can Make feed Mixpanel and read its reports without a developer? Yes. The Mixpanel Make integration brings 42 modules, 22 actions and 20 searches. This guide helps product and growth teams connect their project and build a first scenario step by step.

Try the Mixpanel integration on Make See the 42 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Mixpanel Make integration do?

With it, Make sends data to Mixpanel and reads data back, without code. You build a scenario, the automation made of modules (one brick per step), and each Mixpanel module either writes something (an event, a profile, an annotation) or runs a search that returns reports, profiles or pipelines.

Your product analytics fed by the rest of your tools. A payment in your billing app or a signup in your CRM becomes an event through Track an Event, and Create or Update a User Profile keeps the person's details in step. Each item passed from one module to the next is called a bundle.

Reports that reach people who never open Mixpanel. Query a Funnels Report, Query a Retention Report or Aggregate Event Counts send the figures to a sheet or a chat channel, so a sales lead sees the numbers where they already work.

A cleaner project. Delete a User Profile handles erasure requests, Merge Identities joins a person split over two IDs, and Create an Annotation marks releases on your charts.

What the app does not offer: no trigger, so a Mixpanel scenario starts from another app or from a schedule, and no universal Make an API Call module. Its Make a Query API Call, Make an Ingestion API Call and Make a JQL Query modules cover custom requests. The same app often exists as an n8n node too; the n8n vs Make comparison lays out the differences. To learn the editor properly, see Make training, and when a run fails, Make troubleshooting walks through the usual fixes.

Connect

How do you connect Mixpanel to Make?

01
Copy your project keys
In Mixpanel, click the Settings gear at the top right of your project and choose Project settings. The Access Keys table shows your API token and your API secret: copy both.
02
Add a Mixpanel module
In your Make scenario, add any Mixpanel module and click Create a connection. The Connection name field is optional; a clear name such as the project's name helps when you run several projects.
03
Paste the credentials and save
Paste the token and the secret you copied, or follow the instructions Make shows on screen. The connection, your Mixpanel account linked to Make, is then reused by every Mixpanel module you add later.

First scenario

Your first scenario with Mixpanel

GoalWhen a new customer is created in your billing tool, Make updates their Mixpanel profile and records a signup event.

01
Create the scenario
On the Scenarios page, create a new scenario and click the big + to add the first module. Mixpanel has no trigger, so the scenario starts from the app where customers are created.
02
Pick the starting app
Search your billing tool or CRM by name, choose its module that watches new customers, and click Create a connection to link that account. Each new customer will arrive as one bundle.
03
Add the profile module
Click the + on the right, search Mixpanel and pick Create or Update a User Profile. Connect your project, then map the customer ID and details coming from the first module.
04
Record the event
Add Track an Event after it and map the same customer ID, so the event and the profile point at one person. Name the event after what happened, a new signup.
05
Test with Run once
Create a test customer, click Run once and open the bundles each module received. Check in Mixpanel that the profile and the event show up for that person.
06
Schedule and switch on
Set the schedule on the first module (every 15 minutes by default, 15 minutes minimum on the Free plan) and turn the scenario on. Each module run on a bundle counts as one operation.

Modules

What each Mixpanel module does

Mixpanel gives you 42 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Mixpanel1

Create an Alias

Action

In Make“Creates a new alias to a distinct ID.”

Attaches a second identifier to someone Mixpanel already tracks, so everything sent under that alias counts toward the same distinct ID instead of a stranger.

When to use it

a visitor browsed your site under a temporary ID, then signed up, and your signup tool hands Make the new customer ID.

Watch out

the alias follows whichever distinct ID you map from the previous module, so confirm that mapping with Run once before you switch the scenario on.

Mixpanel2

Create an Annotation

Action

In Make“Creates a new annotation at the specified time.”

Pins a dated note on your Mixpanel charts, so a spike or a dip comes with its explanation right on the timeline.

When to use it

a release ships, a pricing page changes or a campaign goes out from another tool, and the team should see that moment next to the curves.

Watch out

the note lands at the time you give it; map the date of the real event from the earlier module so it sits where it belongs on the chart.

Mixpanel3

Create an Identity

Action

In Make“Creates a new identity.”

Registers a brand new identity in your Mixpanel project, the starting point for tying events and profiles to one real person.

When to use it

an account opens in your product or your billing tool and you want Mixpanel to know that person before the first events arrive.

Watch out

if the person may already exist under another ID, Merge Identities or Create an Alias fits better, so check which case you are in before choosing this module.

Mixpanel4

Create a Pipeline

Action

In Make“Creates a new export pipeline.”

Sets up a new export pipeline in Mixpanel from inside a scenario, so the export exists without anyone configuring it by hand.

When to use it

a new client project opens and every project of that kind needs the same export ready from the start.

Watch out

a pipeline keeps scheduling jobs until someone removes it; keep List Pipelines and Delete a Pipeline in mind to tidy up the ones you no longer need.

Mixpanel5

Create or Update a Group Profile

Action

In Make“Creates a new group profile or updates the existing one.”

Writes a group profile, the card for an account shared by several users (a company, for instance), and updates it when it already exists, so one module covers both cases.

When to use it

a deal changes stage in your CRM and the matching company record in Mixpanel should carry the same information.

Watch out

because the module creates a profile when nothing matches, a typo in the group ID gives you a second profile instead of an update.

Mixpanel6

Create or Update a Schema

Action

In Make“Creates a schema for a single entity. Schema already existing will be replaced.”

Writes the schema of a single entity in your project's lexicon, and swaps out the old version whenever one is already there.

When to use it

your tracking plan lives in a sheet or a database, and each change made there should reach the lexicon without copy and paste.

Watch out

the existing schema is replaced, not patched, so send the full version every time rather than only the line that changed.

Mixpanel7

Create or Update a User Profile

Action

In Make“Creates a new user profile or updates the existing one.”

Creates a user's profile in Mixpanel, or refreshes it when the person is already there, so the details you hold in other tools stay in line.

When to use it

a contact is edited in your CRM or a customer upgrades in your billing tool, and Mixpanel should reflect it.

Watch out

the match relies on the user ID you map; send the same ID your product uses when it tracks events, otherwise you end up with a twin profile.

Mixpanel8

Delete a Group Profile

Action

In Make“Removes a group profile permanently by its ID.”

Erases a group profile for good, using its ID, when a company should no longer appear among your Mixpanel groups.

When to use it

a company closes its account or asks for its data to be removed, and the request reaches Make from your CRM or your help desk.

Watch out

the removal is permanent; run the scenario with Run once on a test group before switching it on for real accounts.

Mixpanel9

Delete an Annotation

Action

In Make“Removes an annotation by its ID.”

Removes a single annotation from your charts by its ID, handy when a note was posted by mistake or no longer tells the truth.

When to use it

a release is rolled back or a campaign is canceled, and the note announcing it should go as well.

Watch out

you need the annotation's ID: fetch it first with List Annotations over the right date range, then map it into this module.

Mixpanel10

Delete a Pipeline

Action

In Make“Removes a pipeline and stops any future jobs to be scheduled for the pipeline.”

Shuts an export pipeline down: Mixpanel removes it and schedules no further jobs for it.

When to use it

a client contract ends or a destination is retired, and the export tied to it has to stop cleanly.

Watch out

upcoming jobs are gone once it runs, so confirm with Get a Pipeline or List Pipeline Logs that you hold the right ID before the first real run.

Mixpanel11

Delete a User Profile

Action

In Make“Removes a user profile permanently by its ID.”

Wipes one user profile from your Mixpanel project permanently, based on its ID, which is what an erasure request calls for.

When to use it

a customer asks for their account to be erased and your support tool or web form passes the request on to Make.

Watch out

nothing brings the profile back; find the right person with Query Profiles first, and test the scenario once on a dummy user.

Mixpanel12

Delete Schemas

Action

In Make“Removes one or many schemas in a project.”

Clears schemas out of a project, one or several in a single run, to tidy a lexicon cluttered by events nobody sends anymore.

When to use it

an event is dropped from your tracking plan and its description should leave the lexicon along with it.

Watch out

the module can hit several schemas at once; list them with List Schemas and check the selection before you let it loose on the project.

Mixpanel13

Get a Pipeline

Action

In Make“Retrieves a pipeline by its ID.”

Reads what Mixpanel holds about one export pipeline, found by its ID, so the next module can act on it.

When to use it

a scenario checks an export before reporting on it to the data team, or before deciding whether to delete it.

Watch out

the module needs the pipeline ID; if you do not have it yet, start with List Pipelines, which returns every pipeline scheduled for the project.

Mixpanel14

Import an Old Event

Action

In Make“Imports an event that was created in the past.”

Sends Mixpanel an event that happened in the past, so your history also covers what occurred before the scenario existed.

When to use it

you move orders or signups over from another tool, or an event older than five days still has to reach the project.

Watch out

Track an Event is meant for recent activity; the doc points to this module as soon as an event is more than five days old.

Mixpanel15

Make a JQL Query

Action

In Make“Performs an arbitrary authorized JQL query.”

Runs a JQL query you write yourself against your project, for the questions no ready-made report module answers.

When to use it

you already know JQL and need a custom calculation sent on to a sheet, a slide or a chat message.

Watch out

Make returns exactly what your query asks for; test it with Run once and read the bundles before mapping anything downstream.

Mixpanel16

Make an Ingestion API Call

Action

In Make“Performs an arbitrary authorized API call to Ingestion API.”

Sends a request of your own design to Mixpanel's Ingestion API, with the authorization already handled by your connection.

When to use it

the tracking and profile modules stop short of what you want to send, and you know the exact request you need.

Watch out

you build the request yourself, so read the bundle that Run once returns to confirm Mixpanel accepted it before activating the scenario.

Mixpanel17

Make a Query API Call

Action

In Make“Performs an arbitrary authorized API call to Query API.”

Calls Mixpanel's Query API with a request you write, already authorized through your connection, to reach data the other modules leave out.

When to use it

a view exists in Mixpanel but none of the query modules on this page returns it in the shape you need.

Watch out

this is the app's own call module for the Query API; Make's universal Make an API Call module does not exist for this app.

Mixpanel18

Merge Identities

Action

In Make“Merges two identities by their distinct IDs.”

Fuses two identities into one from their distinct IDs, so the history split between them reads as a single person.

When to use it

someone used your product on two devices or under two emails, and your CRM confirms it is the same customer.

Watch out

the scenario merges whatever IDs you map, so look both of them up with Query Profiles before the merge runs.

Mixpanel19

Query an Insights Report

Action

In Make“Retrieves data from your insights report.”

Pulls the figures of one of your Insights reports so they can travel to a spreadsheet, a slide or a message.

When to use it

a manager asks a question in your team chat and the scenario answers with the numbers straight from the report.

Watch out

the output mirrors the report as it is built in Mixpanel; adjust the report there, not in Make, when the figures look off.

Mixpanel20

Track an Event

Action

In Make“Tracks a new event. Use "Import an Old Event" module to import an event older than 5 days.”

Records one new event in Mixpanel for a user, the basic gesture for feeding your analytics with what happens outside your product.

When to use it

a payment succeeds in your billing tool or a form gets submitted, and that step should show up in your funnels.

Watch out

keep it for recent events: past five days, the doc sends you to Import an Old Event instead.

Mixpanel21

Track Multiple Events

Action

In Make“Tracks multiple events in one batch. The entire request will be rejected for one invalid event in the batch.”

Sends a whole batch of events to Mixpanel in one request instead of a separate module run for each of them.

When to use it

a previous module hands over several rows at once, such as an export from your store, and they all belong in Mixpanel.

Watch out

a single invalid event makes Mixpanel reject the entire batch, so test with Run once on a small sample first.

Mixpanel22

Update an Annotation

Action

In Make“Updates an annotation to the new time or description by its ID.”

Changes the date or the text of an annotation you already posted, found by its ID, without deleting and recreating it.

When to use it

a launch slips to another day and the note on your charts should move with it.

Watch out

the ID comes from List Annotations or from the module that created the note; map it rather than typing it by hand.

Mixpanel23

Aggregate a Segmentation Report

In Make“Aggregates data from your segmentation report. Either in sum or on average.”

Turns a segmentation report into one figure, either a sum or an average, ready to drop into a KPI sheet.

When to use it

you need the total or the mean of a segmented metric rather than the detail of every single segment.

Watch out

sum and average give very different numbers from the same report, so pick one deliberately and label it clearly in the destination.

Mixpanel24

Aggregate Event Counts

In Make“Retrieves unique, total, or average data for a set of events over N days, weeks, or months.”

Counts a set of events over days, weeks or months and returns unique, total or average figures for them.

When to use it

a dashboard in another tool should show signups, purchases and cancellations side by side.

Watch out

decide which kind of figure you want before mapping the result, because unique and total counts answer different questions.

Mixpanel25

Aggregrate Event Property Values

In Make“Retrieves unique, total, or average data for a single event and property over days, weeks, or months.”

Zooms in on one event and one of its properties, then gives unique, total or average values over days, weeks or months.

When to use it

you want to follow how a single property of an event, for example the plan chosen at checkout, moves over time.

Watch out

the module name carries a typo in Make (Aggregrate with an extra r), so look for it under that spelling when you search.

Mixpanel26

Export Data

In Make“Exports raw data stored within Mixpanel with all event properties and the exact timestamp the event was fired.”

Pulls raw events out of Mixpanel with every property attached and the exact moment each one fired.

When to use it

you archive events in a warehouse or a sheet, or feed another tool that needs event-level detail.

Watch out

as a search, it can return a large number of bundles, and every module after it runs once per bundle, which adds up in operations.

Mixpanel27

List Annotations

In Make“Retrieves a list of annotations for a given date range.”

Gives back the annotations posted over a date range, one bundle per note, ready to reuse elsewhere.

When to use it

you need a note's ID before Update an Annotation or Delete an Annotation, or you want a recap of the changes logged over a period.

Watch out

a wide range brings back many bundles; narrow the dates to what the scenario actually needs.

Mixpanel28

List Cohorts

In Make“Retrieves saved cohorts in a project by the project ID.”

Returns the cohorts saved in a project, the user groups your team defined in Mixpanel, so a scenario can reuse them elsewhere.

When to use it

you keep a register of cohorts in a shared sheet, or check that a cohort exists before relying on it downstream.

Watch out

the module works from the project ID, so keep that ID at hand when you fill in the module.

Mixpanel29

List Pipeline Logs

In Make“Retrieves a list of logs by the pipeline ID.”

Reads the logs of one export pipeline from its ID, the first place to look when an export did not arrive.

When to use it

a scenario watches your exports and alerts the data team in chat when the logs show a problem.

Watch out

you need the pipeline ID; List Pipelines can supply it earlier in the same scenario.

Mixpanel30

List Pipelines

In Make“Retrieves a list of pipelines scheduled for a project.”

Lists every pipeline scheduled for a project, a fast inventory of the exports running out of Mixpanel.

When to use it

you audit exports across projects, or need an ID before Get a Pipeline, List Pipeline Logs or Delete a Pipeline.

Watch out

each pipeline comes out as a separate bundle, so the module that follows runs once for every one of them.

Mixpanel31

List Schemas

In Make“Retrieves a list of lexicon schemas in a project.”

Fetches the lexicon schemas of a project, handy for copying your event definitions into a sheet the whole team can read.

When to use it

product and data people review the tracking plan together outside Mixpanel.

Watch out

run it before Delete Schemas or Create or Update a Schema to see what already exists and avoid overwriting the wrong entry.

Mixpanel32

Query a Frequency Report

In Make“Retrieves data from your frequency report.”

Brings back the data behind your frequency report so it can be shared outside Mixpanel.

When to use it

the frequency figures you look at in Mixpanel should land in a sheet, a slide or a message for people without a Mixpanel seat.

Watch out

the output follows the way the report is set up in Mixpanel; tweak the report there first, then run the scenario again.

Mixpanel33

Query a Funnels Report

In Make“Retrieves data from your funnel report.”

Reads your funnel report and returns its numbers for use in another tool, no copying from the screen.

When to use it

a conversion review happens in a slide deck or a spreadsheet, and the funnel figures should get there on their own.

Watch out

run it once and inspect the bundle before mapping, since a funnel can hold more values than you expect.

Mixpanel34

Query an Activity Feed

In Make“Retrieves an activity feed for specified users by their distinct IDs.”

Returns the activity feed of the users you name by distinct ID, the trail of what they recently did.

When to use it

a support ticket arrives and the agent would benefit from seeing the customer's latest actions right next to it.

Watch out

you have to pass the distinct IDs yourself; map them from the ticket or the CRM record that started the scenario.

Mixpanel35

Query a Retention Report

In Make“Retrieves data from your retention report.”

Fetches the data of your retention report so a scenario can pass it on to a sheet, a dashboard or a chat channel.

When to use it

a product review is being prepared outside Mixpanel and the retention figures need to be part of it.

Watch out

the report can come back as several bundles; add an aggregator after it if you want everything in one message.

Mixpanel36

Query a Segmentation Report

In Make“Retrieves data from your segmentation report.”

Gets the detail of your segmentation report, segment by segment, where the aggregate module would give you a single number.

When to use it

you compare channels or countries in a spreadsheet and need each segment on its own line.

Watch out

if a total or an average is all you need, Aggregate a Segmentation Report spares you the extra bundles.

Mixpanel37

Query Profiles

In Make“Retrieves a list of users that fit specified criteria.”

Searches user profiles and returns the ones matching the criteria you set: zero, one or many people.

When to use it

you need an ID before deleting, merging or updating someone, or a list of users to follow up in your CRM.

Watch out

loose criteria mean many bundles, and each one sets off the modules after it, so tighten them before activating.

Mixpanel38

Query Segmentation Report in Buckets

In Make“Retrieves data from your segmentation report in buckets.”

Returns your segmentation report grouped in buckets rather than value by value.

When to use it

a numeric property such as order amount spreads over too many values to read one by one.

Watch out

choosing between this module and Query a Segmentation Report depends on the view you want at the destination; try both with Run once.

Mixpanel39

Query Today's Top Events

In Make“Retrieves today's top events with their counts and the normalized percent change from yesterday.”

Lists today's top events with their counts and a normalized percent change against yesterday.

When to use it

someone asks in your team chat what is moving today and the scenario replies with this snapshot.

Watch out

the comparison is always today against yesterday; for a longer look back, Query Top Events covers the last 31 days.

Mixpanel40

Query Top Event Properties

In Make“Retrieves the top property names for an event.”

Returns the property names used most often on a given event, a quick way to see what data it actually carries.

When to use it

you review an event before building a report or a scenario on it and want to know which properties are worth mapping.

Watch out

it gives names, not values; Query Top Event Property Values is the next step when you need the values.

Mixpanel41

Query Top Event Property Values

In Make“Retrieves the top values for a property.”

Returns the values that come up most often for one property, so you see which plan, country or campaign leads. Each value reaches the next module as its own bundle.

When to use it

you already know the property name and want its leading values copied into a sheet or a team message.

Watch out

it only covers values; if you are unsure which property to ask about, run Query Top Event Properties first.

Mixpanel42

Query Top Events

In Make“Retrieves a list of the most common events over the last 31 days.”

Lists the events your product fires most often over the last 31 days, a quick way to learn what users actually do before building anything heavier. Each event arrives as its own bundle.

When to use it

a product manager wants the busiest events pushed into a report without opening Mixpanel.

Watch out

it covers the last 31 days as a whole; for today alone, Query Today's Top Events is the better fit.

Need help

Need help automating Mixpanel with Make?

A person reads every message.

FAQ

Mixpanel and Make: common questions

01Is the Mixpanel Make integration free?

Yes, on the Make side. Mixpanel is a standard app, available from the Free plan like the 3,000 plus standard apps. The Free plan allows 2 active scenarios, scheduled runs no closer than 15 minutes apart, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) go down to a 1 minute interval, unlimited active scenarios and 40 minutes per execution, with usage counted in credits each month. Your Mixpanel subscription is a separate matter: the doc asks for an active Mixpanel account and points to Mixpanel's own pricing page.

02What do you need to connect Mixpanel to Make?

An active Mixpanel account and the keys of the project you want to automate. In Mixpanel, open the Settings gear, then Project settings, and copy the API token and the API secret from the Access Keys table. In Make, add a Mixpanel module, click Create a connection, give it a name if you like and paste the credentials. That single connection then serves every Mixpanel module in all your scenarios, so you only do this once per project.

03Does the Mixpanel Make integration react in real time?

No, because the app has no trigger module at all. A scenario that writes to Mixpanel starts from another app: the trigger of your CRM, your billing tool or your form tool. If that trigger is instant, meaning the app calls Make through a webhook as soon as something happens, the Mixpanel modules follow right away. A scenario that reads reports can also simply run on a schedule, every 15 minutes by default, with 1 minute as the shortest interval on paid plans.

04What if a Mixpanel module you need is missing in Make?

Look first at the three open modules the app already has. Make a Query API Call sends your own request to the Query API, Make an Ingestion API Call does the same on the Ingestion API, and Make a JQL Query runs a JQL query you write. Make's universal Make an API Call module does not exist for Mixpanel, so do not count on it. If your case still does not fit, the Hack'celeration team can study the scenario with you and suggest another route.

05Should you use Make or n8n for Mixpanel?

It depends on your setup. In Make, Mixpanel comes with 42 ready modules, including query and ingestion call modules, and the editor draws each step so you can follow the flow visually. The same app often has an n8n node as well, so check what it covers before deciding. The fair criteria are the modules you actually need, the tool where your other automations already run, and the one your team is comfortable maintaining. Neither choice is wrong for a simple tracking or reporting flow.

Copy your project keys

Add a Mixpanel module

Paste the credentials and save

Create the scenario

Pick the starting app

Add the profile module

Record the event

Test with Run once

Schedule and switch on

Need help automating Mixpanel with Make?