Appearance
Mixpanel
Track events, analyze user behavior, and query engagement with Mixpanel.
| Detail | Value |
|---|---|
| Category | Analytics |
| Base URL | https://api.mixpanel.com |
| Authentication | Bearer Token |
| Endpoints | 5 |
| Connector key | mixpanel |
Using Mixpanel in a workflow
- Go to Connections and click New Connection.
- Pick Mixpanel from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST /track | Track an event |
POST /engage | Update a user profile |
GET /api/2.0/events | Query event data |
GET /api/2.0/funnels | Query funnel data |
POST /import | Import historical events |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /track
Track an event
| Detail | Value |
|---|---|
| Operation ID | analytics.track |
| Method | POST |
| Path | /track |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
data | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mixpanel connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.track. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mixpanel API reference.
POST /engage
Update a user profile
| Detail | Value |
|---|---|
| Operation ID | analytics.updateProfile |
| Method | POST |
| Path | /engage |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
$token | string |
$distinct_id | string |
$set | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mixpanel connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.updateProfile. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mixpanel API reference.
GET /api/2.0/events
Query event data
| Detail | Value |
|---|---|
| Operation ID | analytics.queryEvents |
| Method | GET |
| Path | /api/2.0/events |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
event | query | string | Yes |
from_date | query | string | Yes |
to_date | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mixpanel connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.queryEvents. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mixpanel API reference.
GET /api/2.0/funnels
Query funnel data
| Detail | Value |
|---|---|
| Operation ID | analytics.queryFunnels |
| Method | GET |
| Path | /api/2.0/funnels |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
funnel_id | query | string | Yes |
from_date | query | string | Yes |
to_date | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mixpanel connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.queryFunnels. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mixpanel API reference.
POST /import
Import historical events
| Detail | Value |
|---|---|
| Operation ID | analytics.importEvents |
| Method | POST |
| Path | /import |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
data | array |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mixpanel connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.importEvents. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mixpanel API reference.