mixpanel-automation - Agent Skills

Mixpanel Automation via Rube MCP

Automate Mixpanel product analytics through Composio's Mixpanel toolkit via Rube MCP.

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)

Active Mixpanel connection via RUBE_MANAGE_CONNECTIONS with toolkit mixpanel

Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds

Call RUBE_MANAGE_CONNECTIONS with toolkit mixpanel

If connection is not ACTIVE, follow the returned auth link to complete Mixpanel authentication

Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Aggregate Event Data

When to use: User wants to count events, get totals, or track event trends over time

Tool sequence:

MIXPANEL_GET_ALL_PROJECTS - List projects to get project ID [Prerequisite]

MIXPANEL_AGGREGATE_EVENT_COUNTS - Get event counts and aggregations [Required]

Key parameters:

event: Event name or array of event names to aggregate

from_date / to_date: Date range in 'YYYY-MM-DD' format

unit: Time granularity ('minute', 'hour', 'day', 'week', 'month')

type: Aggregation type ('general', 'unique', 'average')

where: Filter expression for event properties

Pitfalls:

Date format must be 'YYYY-MM-DD'; other formats cause errors

Event names are case-sensitive; use exact names from your Mixpanel project

where filter uses Mixpanel expression syntax (e.g., properties["country"] == "US")

Maximum date range may be limited depending on your Mixpanel plan

2. Run Segmentation Queries

When to use: User wants to break down events by properties for detailed analysis

Tool sequence:

MIXPANEL_QUERY_SEGMENTATION - Run segmentation analysis [Required]

Key parameters:

event: Event name to segment

from_date / to_date: Date range in 'YYYY-MM-DD' format

on: Property to segment by (e.g., properties["country"])

unit: Time granularity

type: Count type ('general', 'unique', 'average')

where: Filter expression

limit: Maximum number of segments to return

Pitfalls:

The on parameter uses Mixpanel property expression syntax

Property references must use properties["prop_name"] format

Segmentation on high-cardinality properties returns capped results; use limit

Results are grouped by the segmentation property and time unit

3. Analyze Funnels

When to use: User wants to track conversion funnels and identify drop-off points

Tool sequence:

MIXPANEL_LIST_FUNNELS - List saved funnels to find funnel ID [Prerequisite]

MIXPANEL_QUERY_FUNNEL - Execute funnel analysis [Required]

Key parameters:

funnel_id: ID of the saved funnel to query

from_date / to_date: Date range

unit: Time granularity

where: Filter expression

on: Property to segment funnel by

length: Conversion window in days

Pitfalls:

funnel_id is required; resolve via LIST_FUNNELS first

Funnels must be created in Mixpanel UI first; API only queries existing funnels

Conversion window (length) defaults vary; set explicitly for accuracy

Large date ranges with segmentation can produce very large responses

4. Manage User Profiles

When to use: User wants to query or update user profiles in Mixpanel

Tool sequence:

MIXPANEL_QUERY_PROFILES - Search and filter user profiles [Required]

MIXPANEL_PROFILE_BATCH_UPDATE - Update multiple user profiles [Optional]

Key parameters:

where: Filter expression for profile properties (e.g., properties["plan"] == "premium")

output_properties: Array of property names to include in results

page: Page number for pagination

session_id: Session ID for consistent pagination (from first response)

For batch update: array of profile updates with $distinct_id and property operations

Pitfalls:

Profile queries return paginated results; use session_id from first response for consistent paging

where uses Mixpanel expression syntax for profile properties

BATCH_UPDATE applies operations ($set, $unset, $add, $append) to profiles

Batch update has a maximum number of profiles per request; chunk larger updates

Profile property names are case-sensitive

5. Manage Cohorts

When to use: User wants to list or analyze user cohorts

Tool sequence:

MIXPANEL_COHORTS_LIST - List all saved cohorts [Required]

Key parameters:

No required parameters; returns all accessible cohorts

Response includes cohort id, name, description, count

Pitfalls:

Cohorts are created and managed in Mixpanel UI; API provides read access

Cohort IDs are numeric; use exact ID from list results

Cohort counts may be approximate for very large cohorts

Cohorts can be used as filters in other queries via where expressions

6. Run JQL and Insight Queries

When to use: User wants to run custom JQL queries or insight analyses

Tool sequence:

MIXPANEL_JQL_QUERY - Execute a custom JQL (JavaScript Query Language) query [Optional]

MIXPANEL_QUERY_INSIGHT - Run a saved insight query [Optional]

Key parameters:

For JQL: script containing the JQL JavaScript code

For Insight: bookmark_id of the saved insight

project_id: Project context for the query

Pitfalls:

JQL uses JavaScript-like syntax specific to Mixpanel

JQL queries have execution time limits; optimize for efficiency

Insight bookmark_id must reference an existing saved insight

JQL is a legacy feature; check Mixpanel documentation for current availability

Common Patterns

ID Resolution

Project name -> Project ID:

1. Call MIXPANEL_GET_ALL_PROJECTS
Find project by name in results

Extract project id

Funnel name -> Funnel ID:

1. Call MIXPANEL_LIST_FUNNELS
Find funnel by name

Extract funnel_id

Mixpanel Expression Syntax

Used in where and on parameters:

Property reference: properties["property_name"]

Equality: properties["country"] == "US"

Comparison: properties["age"] > 25

Boolean: properties["is_premium"] == true

Contains: "search_term" in properties["name"]

AND/OR: properties["country"] == "US" and properties["plan"] == "pro"

Pagination

Event queries: Follow date-based pagination by adjusting date ranges

Profile queries: Use page number and session_id for consistent results

Funnel/cohort lists: Typically return complete results without pagination

Known Pitfalls

Date Formats:

Always use 'YYYY-MM-DD' format

Date ranges are inclusive on both ends

Data freshness depends on Mixpanel ingestion delay (typically minutes)

Expression Syntax:

Property references always use properties["name"] format

String values must be quoted: properties["status"] == "active"

Numeric values are unquoted: properties["count"] > 10

Boolean values: true / false (lowercase)

Rate Limits:

Mixpanel API has rate limits per project

Large segmentation queries may time out; reduce date range or segments

Use batch operations where available to minimize API calls

Response Parsing:

Response data may be nested under data key

Event data is typically grouped by date and segment

Numeric values may be returned as strings; parse explicitly

Empty date ranges return empty objects, not empty arrays

Quick Reference

Task	Tool Slug	Key Params
List projects	MIXPANEL_GET_ALL_PROJECTS	(none)
Aggregate events	MIXPANEL_AGGREGATE_EVENT_COUNTS	event, from_date, to_date, unit
Segmentation	MIXPANEL_QUERY_SEGMENTATION	event, on, from_date, to_date
List funnels	MIXPANEL_LIST_FUNNELS	(none)
Query funnel	MIXPANEL_QUERY_FUNNEL	funnel_id, from_date, to_date
Query profiles	MIXPANEL_QUERY_PROFILES	where, output_properties, page
Batch update profiles	MIXPANEL_PROFILE_BATCH_UPDATE	(profile update objects)
List cohorts	MIXPANEL_COHORTS_LIST	(none)
JQL query	MIXPANEL_JQL_QUERY	script
Query insight	MIXPANEL_QUERY_INSIGHT	bookmark_id