Mixpanel integration

What it does

The Mixpanel integration lets your agency keep client product analytics in sync with the rest of the stack. Connect a client project once and you can stream live events into Mixpanel, batch-import historical data, update people profiles, pull funnel and insights results into downstream workflows, and watch for new events to fire follow-on automations.

Connect a Mixpanel account

1. In Mixpanel, open Project Settings and switch to the Service Accounts tab.
2. Create a new Service Account with at least the role required for the actions you plan to run (Member for query-only, Admin for ingestion plus query). Copy the username and the secret. Mixpanel only shows the secret once.
3. From Project Settings, Overview, copy the numeric Project ID and the 32-character Project Token.
4. Open the client workspace in TaskJuice, go to Connections, choose Mixpanel, and paste the four values.
5. Leave the host fields at their defaults for US projects, or set them to api-eu.mixpanel.com and eu.mixpanel.com for EU data residency.

Service Accounts and Project Tokens can be rotated at any time from Mixpanel Project Settings.

Triggers

• mixpanel/events-recorded polls the Mixpanel Raw Data Export API and emits one activation per cycle wrapping every event recorded since the previous watermark. Drop a Loop node downstream to process each event individually, or feed the items array into a digest action.

Actions

• mixpanel/track-event sends a single event to the ingestion endpoint using the Project Token, ideal for low-volume realtime tracking.
• mixpanel/import-events batch-imports up to two thousand historical events per request using Service Account authentication, with optional strict validation.
• mixpanel/update-profile sets or updates properties on a user profile via the Engage endpoint, with support for $set, $set_once, $add, $append, $union, and $unset.
• mixpanel/query-events returns aggregated counts for one or more events across a chosen date range and bucket unit.
• mixpanel/list-funnels lists every saved funnel in the connected project so workflows can pick one by ID.
• mixpanel/query-insights fetches the result of a saved Insights report by bookmark ID.

Known limitations

• Mixpanel does not deliver webhooks. New events surface through polling on the configured interval (default fifteen minutes, floor of five minutes per the Raw Data Export rate limits).
• The Query API enforces a default ceiling of around sixty queries per hour per Service Account, with a hard cap on concurrent queries. When a 429 is returned, TaskJuice surfaces it as a retryable rate-limit error and respects the recommended backoff.
• The Raw Data Export API exposes events from the past five years; older events are not available via this surface.
• EU-resident projects must use the api-eu.mixpanel.com and eu.mixpanel.com hosts. Cross-region requests are rejected by Mixpanel with a 403.
• Each Service Account is scoped to a single project. Workflows that span multiple Mixpanel projects need one connection per project.