Mixpanel Automation

1---
2name: mixpanel-automation
3description: "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]
6---
7 
8# Mixpanel Automation via Rube MCP
9 
10Automate Mixpanel product analytics through Composio's Mixpanel toolkit via Rube MCP.
11 
12## Prerequisites
13 
14- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
15- Active Mixpanel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`
16- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
17 
18## Setup
19 
20**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.
21 
22 
231. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
242. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`
253. If connection is not ACTIVE, follow the returned auth link to complete Mixpanel authentication
264. Confirm connection status shows ACTIVE before running any workflows
27 
28## Core Workflows
29 
30### 1. Aggregate Event Data
31 
32**When to use**: User wants to count events, get totals, or track event trends over time
33 
34**Tool sequence**:
351. `MIXPANEL_GET_ALL_PROJECTS` - List projects to get project ID [Prerequisite]
362. `MIXPANEL_AGGREGATE_EVENT_COUNTS` - Get event counts and aggregations [Required]
37 
38**Key parameters**:
39- `event`: Event name or array of event names to aggregate
40- `from_date` / `to_date`: Date range in 'YYYY-MM-DD' format
41- `unit`: Time granularity ('minute', 'hour', 'day', 'week', 'month')
42- `type`: Aggregation type ('general', 'unique', 'average')
43- `where`: Filter expression for event properties
44 
45**Pitfalls**:
46- Date format must be 'YYYY-MM-DD'; other formats cause errors
47- Event names are case-sensitive; use exact names from your Mixpanel project
48- `where` filter uses Mixpanel expression syntax (e.g., `properties["country"] == "US"`)
49- Maximum date range may be limited depending on your Mixpanel plan
50 
51### 2. Run Segmentation Queries
52 
53**When to use**: User wants to break down events by properties for detailed analysis
54 
55**Tool sequence**:
561. `MIXPANEL_QUERY_SEGMENTATION` - Run segmentation analysis [Required]
57 
58**Key parameters**:
59- `event`: Event name to segment
60- `from_date` / `to_date`: Date range in 'YYYY-MM-DD' format
61- `on`: Property to segment by (e.g., `properties["country"]`)
62- `unit`: Time granularity
63- `type`: Count type ('general', 'unique', 'average')
64- `where`: Filter expression
65- `limit`: Maximum number of segments to return
66 
67**Pitfalls**:
68- The `on` parameter uses Mixpanel property expression syntax
69- Property references must use `properties["prop_name"]` format
70- Segmentation on high-cardinality properties returns capped results; use `limit`
71- Results are grouped by the segmentation property and time unit
72 
73### 3. Analyze Funnels
74 
75**When to use**: User wants to track conversion funnels and identify drop-off points
76 
77**Tool sequence**:
781. `MIXPANEL_LIST_FUNNELS` - List saved funnels to find funnel ID [Prerequisite]
792. `MIXPANEL_QUERY_FUNNEL` - Execute funnel analysis [Required]
80 
81**Key parameters**:
82- `funnel_id`: ID of the saved funnel to query
83- `from_date` / `to_date`: Date range
84- `unit`: Time granularity
85- `where`: Filter expression
86- `on`: Property to segment funnel by
87- `length`: Conversion window in days
88 
89**Pitfalls**:
90- `funnel_id` is required; resolve via LIST_FUNNELS first
91- Funnels must be created in Mixpanel UI first; API only queries existing funnels
92- Conversion window (`length`) defaults vary; set explicitly for accuracy
93- Large date ranges with segmentation can produce very large responses
94 
95### 4. Manage User Profiles
96 
97**When to use**: User wants to query or update user profiles in Mixpanel
98 
99**Tool sequence**:
1001. `MIXPANEL_QUERY_PROFILES` - Search and filter user profiles [Required]
1012. `MIXPANEL_PROFILE_BATCH_UPDATE` - Update multiple user profiles [Optional]
102 
103**Key parameters**:
104- `where`: Filter expression for profile properties (e.g., `properties["plan"] == "premium"`)
105- `output_properties`: Array of property names to include in results
106- `page`: Page number for pagination
107- `session_id`: Session ID for consistent pagination (from first response)
108- For batch update: array of profile updates with `$distinct_id` and property operations
109 
110**Pitfalls**:
111- Profile queries return paginated results; use `session_id` from first response for consistent paging
112- `where` uses Mixpanel expression syntax for profile properties
113- BATCH_UPDATE applies operations (`$set`, `$unset`, `$add`, `$append`) to profiles
114- Batch update has a maximum number of profiles per request; chunk larger updates
115- Profile property names are case-sensitive
116 
117### 5. Manage Cohorts
118 
119**When to use**: User wants to list or analyze user cohorts
120 
121**Tool sequence**:
1221. `MIXPANEL_COHORTS_LIST` - List all saved cohorts [Required]
123 
124**Key parameters**:
125- No required parameters; returns all accessible cohorts
126- Response includes cohort `id`, `name`, `description`, `count`
127 
128**Pitfalls**:
129- Cohorts are created and managed in Mixpanel UI; API provides read access
130- Cohort IDs are numeric; use exact ID from list results
131- Cohort counts may be approximate for very large cohorts
132- Cohorts can be used as filters in other queries via `where` expressions
133 
134### 6. Run JQL and Insight Queries
135 
136**When to use**: User wants to run custom JQL queries or insight analyses
137 
138**Tool sequence**:
1391. `MIXPANEL_JQL_QUERY` - Execute a custom JQL (JavaScript Query Language) query [Optional]
1402. `MIXPANEL_QUERY_INSIGHT` - Run a saved insight query [Optional]
141 
142**Key parameters**:
143- For JQL: `script` containing the JQL JavaScript code
144- For Insight: `bookmark_id` of the saved insight
145- `project_id`: Project context for the query
146 
147**Pitfalls**:
148- JQL uses JavaScript-like syntax specific to Mixpanel
149- JQL queries have execution time limits; optimize for efficiency
150- Insight `bookmark_id` must reference an existing saved insight
151- JQL is a legacy feature; check Mixpanel documentation for current availability
152 
153## Common Patterns
154 
155### ID Resolution
156 
157**Project name -> Project ID**:
158```
1591. Call MIXPANEL_GET_ALL_PROJECTS
1602. Find project by name in results
1613. Extract project id
162```
163 
164**Funnel name -> Funnel ID**:
165```
1661. Call MIXPANEL_LIST_FUNNELS
1672. Find funnel by name
1683. Extract funnel_id
169```
170 
171### Mixpanel Expression Syntax
172 
173Used in `where` and `on` parameters:
174- Property reference: `properties["property_name"]`
175- Equality: `properties["country"] == "US"`
176- Comparison: `properties["age"] > 25`
177- Boolean: `properties["is_premium"] == true`
178- Contains: `"search_term" in properties["name"]`
179- AND/OR: `properties["country"] == "US" and properties["plan"] == "pro"`
180 
181### Pagination
182 
183- Event queries: Follow date-based pagination by adjusting date ranges
184- Profile queries: Use `page` number and `session_id` for consistent results
185- Funnel/cohort lists: Typically return complete results without pagination
186 
187## Known Pitfalls
188 
189**Date Formats**:
190- Always use 'YYYY-MM-DD' format
191- Date ranges are inclusive on both ends
192- Data freshness depends on Mixpanel ingestion delay (typically minutes)
193 
194**Expression Syntax**:
195- Property references always use `properties["name"]` format
196- String values must be quoted: `properties["status"] == "active"`
197- Numeric values are unquoted: `properties["count"] > 10`
198- Boolean values: `true` / `false` (lowercase)
199 
200**Rate Limits**:
201- Mixpanel API has rate limits per project
202- Large segmentation queries may time out; reduce date range or segments
203- Use batch operations where available to minimize API calls
204 
205**Response Parsing**:
206- Response data may be nested under `data` key
207- Event data is typically grouped by date and segment
208- Numeric values may be returned as strings; parse explicitly
209- Empty date ranges return empty objects, not empty arrays
210 
211## Quick Reference
212 
213| Task | Tool Slug | Key Params |
214|------|-----------|------------|
215| List projects | MIXPANEL_GET_ALL_PROJECTS | (none) |
216| Aggregate events | MIXPANEL_AGGREGATE_EVENT_COUNTS | event, from_date, to_date, unit |
217| Segmentation | MIXPANEL_QUERY_SEGMENTATION | event, on, from_date, to_date |
218| List funnels | MIXPANEL_LIST_FUNNELS | (none) |
219| Query funnel | MIXPANEL_QUERY_FUNNEL | funnel_id, from_date, to_date |
220| Query profiles | MIXPANEL_QUERY_PROFILES | where, output_properties, page |
221| Batch update profiles | MIXPANEL_PROFILE_BATCH_UPDATE | (profile update objects) |
222| List cohorts | MIXPANEL_COHORTS_LIST | (none) |
223| JQL query | MIXPANEL_JQL_QUERY | script |
224| Query insight | MIXPANEL_QUERY_INSIGHT | bookmark_id |
225