Marketing Automation · Integration
Manychat
Add Manychat to your product for your customers, and give your AI agents governed access to it.
Manychat is where a business runs conversations on Instagram, Messenger, WhatsApp and SMS, and its API is built around the subscriber rather than the message. Everything hangs off that one record, its tags, its field values and whether the channel still permits a send, and the way you make something happen is to send that subscriber a flow, which is the automation the customer already built in Manychat's own editor. That is the design point worth leaning on: your product supplies the trigger and the data, the customer keeps the words, so a change to their messaging is never a deploy on your side. Tags and custom fields are defined per account and are read before they are written. The platform rules underneath still apply, so a message sent outside the window a channel permits is refused however correct your call was. Each business connects its own account, so messages come from the page or number their audience already knows.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each business connect their own Manychat account so messages come from the page or number their audience already recognises.
Send a subscriber a flow the customer built themselves, so your product supplies the trigger and they keep control of the wording.
Write tags and custom fields read from that account's own definitions rather than a field set you assumed.
Update a subscriber's fields from what happened in your product, so the next flow they enter already knows it.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent tags a subscriber after a qualifying event, with the tag and the account recorded.
An agent triggers an approved flow for a contact within scoped permissions.
An agent reports which subscribers entered a flow and where each of them stopped.
Example prompt
Which subscribers started the onboarding flow last week and never reached the end of it?
Set up Manychat in 4 steps
- 01Enable the Manychat connector in your fastn dashboard.
- 02Have each business connect their own Manychat account, so messages send from the page or number they own.
- 03Read that account's tag and custom field definitions and map them, then decide which of your product's events send which flow.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Manychat integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Manychat integration without building it. Your customers connect their own Manychat account inside your product and work their campaigns, segments and subscribers there, with no per-customer code on your side.
- Handle the part that actually costs time: engagement data arrives as a high-volume event stream, so ordering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Manychat update is not your on-call problem.
- One integration serves your product and your agents. The same governed Manychat connection powers in-product features and gives AI agents scoped, audited access, so you trigger and measure campaigns from inside your product without wiring it twice.
Used by these teams
Compare with
Works well with
Often used alongside
Tools the same teams tend to run next to Manychat, across other categories.
Manychat integration FAQ
How do I add a Manychat integration to my product?
Enable the Manychat connector in your fastn dashboard, then let each customer authenticate their own Manychat account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Manychat client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Manychat account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Manychat account and only ever sees their own campaigns, segments and subscribers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Manychat integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent tags a subscriber after a qualifying event, with the tag and the account recorded.
Who maintains the Manychat integration?
fastn does. When Manychat changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I trigger a Manychat campaign from an event in my product?
Yes. Product events can start a campaign, add a contact to a segment, or enrol someone in a journey, so lifecycle messaging follows what a user actually did rather than a nightly export.
Can I read engagement results back from Manychat?
Yes. Results come back scoped per tenant, so your product can act on them without one customer's data mixing with another's. What you get depends on the channel: opens, clicks, bounces and unsubscribes where there are sends, and impressions, spend and conversions where there are campaigns.
What can I build with the Manychat integration?
A common starting point: let each business connect their own Manychat account so messages come from the page or number their audience already recognises. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Manychat integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Manychat does not change your per-connector cost. You can start free with 3 connected accounts.
Add Manychat to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.