Automation · Operations and reporting

Ask on WhatsApp how the purchase funnel is doing in Mixpanel

Ask on WhatsApp how many users reached checkout: an AI agent builds the funnel in Mixpanel and checks data quality.

Show me this with my own operation See every automation

How do I know how many users completed a purchase this week without opening Mixpanel?

You write to your Met "how is the purchase funnel doing this week?". The Met finds the project in Mixpanel, reads the business context your team wrote down, finds the funnel events, checks the query schema and runs the funnel for the period. Before replying, it looks at whether those events have open data quality issues. It answers with how many people went through each step, the conversion between steps and, if it found data issues, the warning. It does not change anything in your project.

What starts it

When someone asks for it

It starts when someone on the team asks the Met about the funnel for a period. Each query runs on request; this procedure does not leave a scheduled report.

A manual task: someone on the team runs it with a button, or asks the Met for it in chat.

Who runs it

Product analytics Met with Mixpanel

This is not a named, seeded Met. It is an internal Met with Mixpanel connected: its work ends when it replies with the funnel numbers, or when it says which event it did not find.

Run by the data analyst Met

Channels: WhatsApp

What you need connected

Mixpanel Research and analyze

5 steps · 6 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Find the project

The Met lists the projects the connected account sees and picks the production one. If several have similar names, it asks you which one.
- get_projects Mixpanel
2
Read the business context

The Met brings the business context and vocabulary your team saved in Mixpanel, such as what counts as a purchase or which event marks sign up, so it does not interpret names its own way.
- get_business_context Mixpanel
3
Find the funnel events

The Met looks for each step's event, for example view product, add to cart and payment completed. If an event does not exist under that name, it tells you before querying.
- get_events Mixpanel
4
Run the funnel

The Met checks the query schema and runs the funnel for the period you asked. That gives it how many people went through each step and the conversion between steps.
- get_query_schema Mixpanel
- run_query Mixpanel
5
Check data quality

Before replying, the Met checks the data quality issues of those events. If one is open, it mentions it along with the numbers so you do not decide with broken data.
- get_issues Mixpanel

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

MCP enabled in your Mixpanel organization

On free and Growth accounts created from August 1, 2026 it comes enabled; on the rest, an organization admin enables it in Settings, Org, Overview.
Mixpanel connected in Met

In Met, open Connections → Mixpanel → Connect and sign in with an account that sees the project. The connector uses Mixpanel's US server.
An internal Met your team writes to

A Met with Mixpanel enabled and a WhatsApp line your team uses to write to it. It is an internal query, not a customer conversation.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not break down the funnel by cohort. Mixpanel documents that Run-Query cannot filter or break down by cohort; that needs the Mixpanel interface.
It does not fix tracking. If an event is not sent correctly, the Met warns you, but fixing it is work in your product's code.
It does not work with projects in the EU or IN regions. The connector points to Mixpanel's US server.
It does not call the funnel's payments sales. They are the events your product sends to Mixpanel, not your payment gateway's transactions.