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
2. Find project by name in results
3. Extract project id
Funnel name -> Funnel ID:
1. Call MIXPANEL_LIST_FUNNELS
2. Find funnel by name
3. 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 |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
1---2name: mixpanel-automation3description: "Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas."4requires:5 mcp: [rube]6risk: unknown7source: community8metadata:9 source: https://skillmd.com/skills/mayurrathi/mixpanel-automation10---1112# Mixpanel Automation via Rube MCP1314Automate Mixpanel product analytics through Composio's Mixpanel toolkit via Rube MCP.1516## Prerequisites1718- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)19- Active Mixpanel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`20- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2122## Setup2324**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.2526271. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds282. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`293. If connection is not ACTIVE, follow the returned auth link to complete Mixpanel authentication304. Confirm connection status shows ACTIVE before running any workflows3132## Core Workflows3334### 1. Aggregate Event Data3536**When to use**: User wants to count events, get totals, or track event trends over time3738**Tool sequence**:391. `MIXPANEL_GET_ALL_PROJECTS` - List projects to get project ID [Prerequisite]402. `MIXPANEL_AGGREGATE_EVENT_COUNTS` - Get event counts and aggregations [Required]4142**Key parameters**:43- `event`: Event name or array of event names to aggregate44- `from_date` / `to_date`: Date range in 'YYYY-MM-DD' format45- `unit`: Time granularity ('minute', 'hour', 'day', 'week', 'month')46- `type`: Aggregation type ('general', 'unique', 'average')47- `where`: Filter expression for event properties4849**Pitfalls**:50- Date format must be 'YYYY-MM-DD'; other formats cause errors51- Event names are case-sensitive; use exact names from your Mixpanel project52- `where` filter uses Mixpanel expression syntax (e.g., `properties["country"] == "US"`)53- Maximum date range may be limited depending on your Mixpanel plan5455### 2. Run Segmentation Queries5657**When to use**: User wants to break down events by properties for detailed analysis5859**Tool sequence**:601. `MIXPANEL_QUERY_SEGMENTATION` - Run segmentation analysis [Required]6162**Key parameters**:63- `event`: Event name to segment64- `from_date` / `to_date`: Date range in 'YYYY-MM-DD' format65- `on`: Property to segment by (e.g., `properties["country"]`)66- `unit`: Time granularity67- `type`: Count type ('general', 'unique', 'average')68- `where`: Filter expression69- `limit`: Maximum number of segments to return7071**Pitfalls**:72- The `on` parameter uses Mixpanel property expression syntax73- Property references must use `properties["prop_name"]` format74- Segmentation on high-cardinality properties returns capped results; use `limit`75- Results are grouped by the segmentation property and time unit7677### 3. Analyze Funnels7879**When to use**: User wants to track conversion funnels and identify drop-off points8081**Tool sequence**:821. `MIXPANEL_LIST_FUNNELS` - List saved funnels to find funnel ID [Prerequisite]832. `MIXPANEL_QUERY_FUNNEL` - Execute funnel analysis [Required]8485**Key parameters**:86- `funnel_id`: ID of the saved funnel to query87- `from_date` / `to_date`: Date range88- `unit`: Time granularity89- `where`: Filter expression90- `on`: Property to segment funnel by91- `length`: Conversion window in days9293**Pitfalls**:94- `funnel_id` is required; resolve via LIST_FUNNELS first95- Funnels must be created in Mixpanel UI first; API only queries existing funnels96- Conversion window (`length`) defaults vary; set explicitly for accuracy97- Large date ranges with segmentation can produce very large responses9899### 4. Manage User Profiles100101**When to use**: User wants to query or update user profiles in Mixpanel102103**Tool sequence**:1041. `MIXPANEL_QUERY_PROFILES` - Search and filter user profiles [Required]1052. `MIXPANEL_PROFILE_BATCH_UPDATE` - Update multiple user profiles [Optional]106107**Key parameters**:108- `where`: Filter expression for profile properties (e.g., `properties["plan"] == "premium"`)109- `output_properties`: Array of property names to include in results110- `page`: Page number for pagination111- `session_id`: Session ID for consistent pagination (from first response)112- For batch update: array of profile updates with `$distinct_id` and property operations113114**Pitfalls**:115- Profile queries return paginated results; use `session_id` from first response for consistent paging116- `where` uses Mixpanel expression syntax for profile properties117- BATCH_UPDATE applies operations (`$set`, `$unset`, `$add`, `$append`) to profiles118- Batch update has a maximum number of profiles per request; chunk larger updates119- Profile property names are case-sensitive120121### 5. Manage Cohorts122123**When to use**: User wants to list or analyze user cohorts124125**Tool sequence**:1261. `MIXPANEL_COHORTS_LIST` - List all saved cohorts [Required]127128**Key parameters**:129- No required parameters; returns all accessible cohorts130- Response includes cohort `id`, `name`, `description`, `count`131132**Pitfalls**:133- Cohorts are created and managed in Mixpanel UI; API provides read access134- Cohort IDs are numeric; use exact ID from list results135- Cohort counts may be approximate for very large cohorts136- Cohorts can be used as filters in other queries via `where` expressions137138### 6. Run JQL and Insight Queries139140**When to use**: User wants to run custom JQL queries or insight analyses141142**Tool sequence**:1431. `MIXPANEL_JQL_QUERY` - Execute a custom JQL (JavaScript Query Language) query [Optional]1442. `MIXPANEL_QUERY_INSIGHT` - Run a saved insight query [Optional]145146**Key parameters**:147- For JQL: `script` containing the JQL JavaScript code148- For Insight: `bookmark_id` of the saved insight149- `project_id`: Project context for the query150151**Pitfalls**:152- JQL uses JavaScript-like syntax specific to Mixpanel153- JQL queries have execution time limits; optimize for efficiency154- Insight `bookmark_id` must reference an existing saved insight155- JQL is a legacy feature; check Mixpanel documentation for current availability156157## Common Patterns158159### ID Resolution160161**Project name -> Project ID**:162```1631. Call MIXPANEL_GET_ALL_PROJECTS1642. Find project by name in results1653. Extract project id166```167168**Funnel name -> Funnel ID**:169```1701. Call MIXPANEL_LIST_FUNNELS1712. Find funnel by name1723. Extract funnel_id173```174175### Mixpanel Expression Syntax176177Used in `where` and `on` parameters:178- Property reference: `properties["property_name"]`179- Equality: `properties["country"] == "US"`180- Comparison: `properties["age"] > 25`181- Boolean: `properties["is_premium"] == true`182- Contains: `"search_term" in properties["name"]`183- AND/OR: `properties["country"] == "US" and properties["plan"] == "pro"`184185### Pagination186187- Event queries: Follow date-based pagination by adjusting date ranges188- Profile queries: Use `page` number and `session_id` for consistent results189- Funnel/cohort lists: Typically return complete results without pagination190191## Known Pitfalls192193**Date Formats**:194- Always use 'YYYY-MM-DD' format195- Date ranges are inclusive on both ends196- Data freshness depends on Mixpanel ingestion delay (typically minutes)197198**Expression Syntax**:199- Property references always use `properties["name"]` format200- String values must be quoted: `properties["status"] == "active"`201- Numeric values are unquoted: `properties["count"] > 10`202- Boolean values: `true` / `false` (lowercase)203204**Rate Limits**:205- Mixpanel API has rate limits per project206- Large segmentation queries may time out; reduce date range or segments207- Use batch operations where available to minimize API calls208209**Response Parsing**:210- Response data may be nested under `data` key211- Event data is typically grouped by date and segment212- Numeric values may be returned as strings; parse explicitly213- Empty date ranges return empty objects, not empty arrays214215## Quick Reference216217| Task | Tool Slug | Key Params |218|------|-----------|------------|219| List projects | MIXPANEL_GET_ALL_PROJECTS | (none) |220| Aggregate events | MIXPANEL_AGGREGATE_EVENT_COUNTS | event, from_date, to_date, unit |221| Segmentation | MIXPANEL_QUERY_SEGMENTATION | event, on, from_date, to_date |222| List funnels | MIXPANEL_LIST_FUNNELS | (none) |223| Query funnel | MIXPANEL_QUERY_FUNNEL | funnel_id, from_date, to_date |224| Query profiles | MIXPANEL_QUERY_PROFILES | where, output_properties, page |225| Batch update profiles | MIXPANEL_PROFILE_BATCH_UPDATE | (profile update objects) |226| List cohorts | MIXPANEL_COHORTS_LIST | (none) |227| JQL query | MIXPANEL_JQL_QUERY | script |228| Query insight | MIXPANEL_QUERY_INSIGHT | bookmark_id |229230## When to Use231This skill is applicable to execute the workflow or actions described in the overview.