Mixpanel (Service Account) ACTION
Query Insights Report
Fetch the computed numbers behind an Insights report that has already been saved in the Mixpanel UI, exactly as the report renders them. Use this when the question maps to a metric the team has already defined and you want their definition rather than your own. For ad-hoc counts where no saved report exists, use Aggregate Event Counts instead. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Mixpanel (Service Account) account once, then configure and run Query Insights Report from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "mixpanel_service_account-query-insights-report",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
mixpanel_service_account: { authProvisionId: "apn_xxxxxxx" },
bookmarkId: 10,
workspaceId: 10,
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "mixpanel_service_account-query-insights-report",
"configured_props": {
"mixpanel_service_account": { "authProvisionId": "apn_xxxxxxx" },
"bookmarkId": 10,
"workspaceId": 10
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "mixpanel_service_account",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "mixpanel_service_account-query-insights-report",
arguments: {
bookmarkId: 10,
workspaceId: 10,
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
bookmarkId Bookmark ID | integer | The ID of the saved Insights report. Open the report in Mixpanel and read it from the URL fragment, which looks like ...#id=12345&editor-card-id=%22report-67890%22 - the bookmark ID is the number after report- (here, 67890). Required |
workspaceId Workspace ID | integer | The ID of the Data View to query. Only needed for projects that use Data Views; leave it empty otherwise. It is the segment after /view/ in a project URL such as https://mixpanel.com/project/1234/view/5678/app/boards. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- mixpanel_service_account-query-insights-report
- Version
- 0.0.1
- App
- Mixpanel (Service Account)
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗