The Problem
ManyChat has one of the best visual automation builders on the market. But its API tells a different story. In 2026, where AI agents are becoming the primary interface between developers and SaaS platforms, ManyChat's API coverage leaves critical operations locked behind the UI — making it nearly impossible for AI-powered workflows to fully automate marketing campaigns.
We manage 1,275 WhatsApp contacts through ManyChat for marketing campaigns in Brazil. Through the API, we can tag subscribers, create contacts, set custom fields, and reactivate subscribers. That part works great. But the moment we need to do the things that actually drive revenue — create a broadcast, list our approved WhatsApp templates, schedule a campaign, or pull performance metrics — the API has nothing. We are forced back into the UI for every critical operation.
This is not a niche complaint. This is a structural gap that will determine whether ManyChat thrives in the AI agent era or gets replaced by API-first alternatives.
The AI Agent Revolution Is Here — And ManyChat Is Missing It
The numbers are not hypothetical. They are happening right now:
- Claude Code (Anthropic's AI coding agent) has reached a $2.5B annualized revenue run-rate, with 58% of professional developers using AI agents in their daily workflow.
- Gemini CLI (Google's agent) hit 98K GitHub stars within weeks of release.
- MCP (Model Context Protocol) — the open standard for connecting AI agents to external tools — now has 17,000+ community servers and 97 million monthly SDK downloads.
- Every major platform has already shipped MCP integrations: Stripe, Shopify, GitHub, Slack, HubSpot, Linear, Notion, Sentry, Cloudflare, Supabase — the list grows daily.
What does this mean in practice? Developers and agencies no longer interact with SaaS tools through UIs. They say to an AI agent: "Send last month's broadcast performance report" or "Create a campaign targeting all subscribers tagged 'hot-lead' using the approved Black Friday template, scheduled for Friday at 9am." The agent calls the API. The work gets done.
ManyChat's API cannot support any of these workflows today. Not because the product lacks the features — but because the API simply does not expose them.
The Community Is Already Building Around the Gap
The developer community is not waiting. They are building what they can with what exists:
- Biznomad/manychat-mcp — a community-built MCP server that wraps ManyChat's API so AI agents can interact with it. But it can only do what the API allows: subscriber CRUD and tagging. No broadcasts. No templates. No metrics.
- Multiple Zapier and Pipedream MCP bridges exist, all hitting the same wall.
- Existing feature requests on this very portal tell the story: broadcast API management (1 vote), template API access (2 votes), flow control via API (4 votes). The low vote counts do not reflect low demand — they reflect the fact that most ManyChat users are marketers, not developers. The developers who need this are building workarounds or leaving the platform entirely.
What We Are Asking For
P0 — Critical (Unlocks AI agent integration)
┌───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────┐
│ Endpoint │ Why │
├───────────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────┤
│ List WhatsApp templates │ AI agents need to know which templates are approved before sending. Without │
│ │ this, any automation is blind. │
├───────────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────┤
│ Send WhatsApp template to subscriber │ The single most requested programmatic action. Templates are the only way to │
│ (with variable substitution) │ initiate WhatsApp conversations outside the 24h window. │
└───────────────────────────────────────────┴───────────────────────────────────────────────────────────────────────────────┘
P1 — High Priority (Unlocks campaign automation)
┌─────────────────────────────────────────────┬─────────────────────────────────────────────────────────────────────────────┐
│ Endpoint │ Why │
├─────────────────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────┤
│ Create broadcast via API │ Allows AI agents and external systems to trigger campaigns without UI │
│ │ interaction. │
├─────────────────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────┤
│ Schedule broadcast │ Time-zone-aware scheduling is table stakes for any marketing API. │
├─────────────────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────┤
│ Get broadcast metrics (sent, delivered, │ Without metrics, there is no feedback loop. AI agents cannot optimize what │
│ read, clicked) │ they cannot measure. │
└─────────────────────────────────────────────┴─────────────────────────────────────────────────────────────────────────────┘
P2 — Important (Unlocks full platform programmability)
┌─────────────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────┐
│ Endpoint │ Why │
├─────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────┤
│ Get flow content/structure │ Currently only sendFlow exists (fire-and-forget). No visibility into what a flow │
│ │ contains. │
├─────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────┤
│ Create/update flows │ Enables version control, CI/CD pipelines, and AI-generated flow creation. │
│ programmatically │ │
├─────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────┤
│ List subscribers by tag │ No way to say "give me all subscribers tagged X." Bulk operations on filtered segments │
│ │ are impossible via API. │
└─────────────────────────────────┴─────────────────────────────────────────────────────────────────────────────────────────┘
The Competitive Reality
- Listmonk (open-source, 19K GitHub stars) offers a complete REST API for every operation: campaigns, templates, subscribers, metrics — all fully programmable.
- WhatsApp Business API (direct) gives full programmatic control over templates, messages, and analytics.
- Brevo, Mailchimp, SendGrid — all have comprehensive APIs that AI agents can fully orchestrate.
The pattern is clear: platforms that expose full APIs get integrated into AI agent workflows. Platforms that don't get bypassed.
A Real Workflow We Cannot Automate Today
1. AI agent queries CRM → identifies 340 subscribers who attended a webinar but did not purchase
2. AI agent calls ManyChat API → lists approved WhatsApp templates → selects the "post-webinar-offer" template
3. AI agent calls ManyChat API → creates a broadcast targeting those 340 subscribers, scheduled for Tuesday at 10am
4. AI agent polls ManyChat API 48 hours later → pulls delivery and read metrics
5. AI agent generates a performance report and suggests optimizations
Step 1 is possible today. Steps 2 through 5 are completely impossible via the API.
Closing
ManyChat has built an incredible product. The visual flow builder, the multi-channel support, the WhatsApp integration — all best-in-class. The API is the missing piece that would unlock an entire ecosystem of AI-powered automation tools. The community is ready — we just need the endpoints.
The platforms that win the next five years will be the ones that AI agents can fully orchestrate. ManyChat has every advantage to be one of them. It just needs to open the door.