Mixpanel Ingestion connector for AI agents

Tools your data agent reaches for on Mixpanel Ingestion, scoped per tenant.

CALL ANY TOOL

Event ingestion and profile management in one toolkit: import events, set and union profile properties, group profiles, identity merges, lookup tables, and flag evaluation.

mixpanelingestion_lookup_tables_list

List lookup tables

List the lookup tables defined in a mixpanel project. returns each table's id and name. use the id with 'mixpanelingestion_lookup_table_replace' to update a table's contents, or find it in lexicon under the lookup table's details.

Parameters

Name

Type

Required

Description

project_id

string

Required

Your numeric Mixpanel Project ID, required to authenticate Service Account requests. Find it in Mixpanel under Project Settings > Overview.

mixpanelingestion_identity_create

Create identity

mixpanelingestion_group_batch_update

Update group batch

mixpanelingestion_group_delete

Delete group

mixpanelingestion_group_remove

Remove group

mixpanelingestion_identity_create_alias

Identity create alias

mixpanelingestion_profile_batch_update

Update profile batch

mixpanelingestion_profile_delete

Delete profile

mixpanelingestion_profile_remove

Remove profile

mixpanelingestion_feature_flags_definitions

Feature flags definitions

mixpanelingestion_group_set

Group set

mixpanelingestion_identity_merge

Merge identity

mixpanelingestion_import_events

Import events

mixpanelingestion_lookup_table_replace

Lookup table replace

mixpanelingestion_profile_append

Profile append

mixpanelingestion_track_event

Track event

mixpanelingestion_feature_flags_evaluate

Evaluate feature flags

mixpanelingestion_group_set_once

Group set once

mixpanelingestion_profile_increment

Profile increment

mixpanelingestion_group_union

Group union

mixpanelingestion_profile_set

Profile set

mixpanelingestion_group_unset

Group unset

mixpanelingestion_profile_set_once

Profile set once

mixpanelingestion_profile_union

Profile union

mixpanelingestion_profile_unset

Profile unset

Build your Agent

Drop the toolkit in, point it at the tenant, and your agent can import events and update profiles from the first run.

import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["mixpanelingestion"], toolNames: ["mixpanelingestion_import_events", "mixpanelingestion_profile_set", "mixpanelingestion_identity_merge"] },
  pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  schema: z.object({}).passthrough(),
  func: async (args) => {
    const { data } = await sk.tools.executeTool({
      toolName: t.tool.definition.name,
      identifier: "user_123",
      params: args,
    });
    return JSON.stringify(data);
  },
}));

const agent = createReactAgent({ llm, tools: lcTools });

import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["mixpanelingestion"], toolNames: ["mixpanelingestion_import_events", "mixpanelingestion_profile_set", "mixpanelingestion_identity_merge"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  type: "function",
  function: {
    name: t.tool.definition.name,
    description: t.tool.definition.description,
    parameters: t.tool.definition.input_schema,
  },
}));

const resp = await openai.responses.create({
  model: "gpt-4o", input: prompt, tools: llmTools,
});

import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["mixpanelingestion"], toolNames: ["mixpanelingestion_import_events", "mixpanelingestion_profile_set", "mixpanelingestion_identity_merge"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
  model: "claude-sonnet-4-6", max_tokens: 1024,
  tools: llmTools,
  messages: [{ role: "user", content: prompt }],
});

import { Agent } from "@google/adk/agents";
import {
  MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
  connectionParams: new StreamableHTTPConnectionParams({
    url: "https://mcp.scalekit.com/mixpanelingestion",
    headers: { Authorization: `Bearer ${userScopedToken}` },
  }),
});

const agent = new Agent({
  name: "agent", model: "gemini-2.0-flash",
  tools: await toolset.getTools(),
});

Try these prompts

Paste any prompt into your agent to start running Mixpanel ingestion from your workflows.

Event import

Copy the prompt

Copied

Import these events for [date] and report anything rejected.

Copy the prompt

Copied

Backfill signup events for last week and dedupe on insert_id.

Copy the prompt

Copied

Track a single [event] for distinct_id [id] with these properties.

Profiles and groups

Copy the prompt

Copied

Set plan and mrr on profile [distinct_id].

Copy the prompt

Copied

Union the feature_flags property on these profiles instead of overwriting.

Copy the prompt

Copied

Batch update group profiles for org [group_id].

Identity and lookups

Copy the prompt

Copied

Merge distinct_id [a] into [b] and confirm the surviving id.

Copy the prompt

Copied

Replace the lookup table for plan tiers with this CSV.

Copy the prompt

Copied

Evaluate feature flags for distinct_id [id].

SEE HOW AUTH WORKS

Your users connect once. Their Mixpanel Ingestion credentials stay vaulted, every call is scope-checked, and every action is logged.

Authorize

Your user connects

Mixpanel Ingestion

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Mixpanel Ingestion

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Mixpanel Ingestion

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Mixpanel Ingestion

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

SALES

Deal intelligence agent

Score Gong call risk with an LLM, cross-reference the Attio record, and DM each owner their at-risk deals in Slack.

ENGINEERING

Engineering standup agent

Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.

// shared token
audit → bot_service_account
user_filter → broken

// scalekit
audit → user_abc
scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Mixpanel Ingestion today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Mixpanel Ingestion as the user or as a shared key?

As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Mixpanel Ingestion service account key stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Mixpanel Ingestion?

Yes. Pass a tool name filter to listScopedTools so the analytics agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Mixpanel Ingestion.

What happens when a user revokes Mixpanel Ingestion access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

What stops an agent from writing junk events into production?

Scope and separation. Ingestion tools are separate from the delete and lookup-replace tools, so you expose only what a given agent needs. Every call is scope-checked before it reaches Mixpanel, attributed to the acting user, and kept in the 90-day audit chain for replay.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit