Manychat
Manage Manychat subscribers, tags, custom fields, bot fields and automations, and send Flows or dynamic content over Messenger, Instagram, WhatsApp and Telegram.
About
Manychat ships in the w6w first-party pack. It declares 25 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.manychat- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Marketing · Communication · Social Media
Overview
Manychat puts a Page’s chat-marketing audience within reach of a workflow — segmenting subscribers with tags and custom fields, and triggering the Automations that message them over Messenger, Instagram, WhatsApp or Telegram.
Subscribers can be looked up by name, email, phone or a custom field, tagged and untagged, and have their custom fields set individually or in a batch; Page-wide bot fields carry a single value shared across every subscriber, for things like a feature flag or a current promo code. Sending a pre-built Automation Flow is the usual way to reach someone, and an ad-hoc content payload is available for messages authored outside Manychat, both subject to Meta’s own messaging-window rules rather than anything this app can waive.
It fits chat-marketing workflows that sync a subscriber’s state from a CRM, trigger a Flow when something happens elsewhere, or keep tags and segments current across every channel Manychat manages — one API token per Page, with the messaging rules Meta enforces surfaced rather than hidden.
Build with Manychat
Three routes to the same 25 actions. The Workflow tab is generated from Manychat's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Add Subscriber Tag
add-subscriber-tag Tag one subscriber, by tag id or tag name (POST /fb/subscriber/addTag or /fb/subscriber/addTagByName). Set semantics — safe to retry.
Create Bot Field
create-bot-field Define a new Page-global bot field (POST /fb/page/createBotField). Takes `name` (unlike Create Custom Field, which takes `caption`). Returns the field under `data.field`.
Create Custom Field
create-custom-field Define a new subscriber custom field (POST /fb/page/createCustomField). The request field is `caption`; the returned object calls it `name`. Returns the field under `data.field`.
Create Subscriber
create-subscriber Create a subscriber from an email, phone or WhatsApp number (POST /fb/subscriber/createSubscriber). Cannot create Messenger or Instagram contacts — those only exist once the person messages the Page.
Create Tag
create-tag Define a new tag on the Page (POST /fb/page/createTag). Returns the tag under `data.tag`.
Delete Tag (destructive)
delete-tag Delete a tag from the Page AND strip it from every subscriber (POST /fb/page/removeTag or /fb/page/removeTagByName). Manychat documents this as irreversible. To untag one person, use Remove Subscriber Tag instead.
Find Subscriber by Email or Phone
find-subscriber-by-system-field Find one subscriber by email OR phone (GET /fb/subscriber/findBySystemField). Returns a single object, not a list. Exactly one of the two must be supplied.
Find Subscribers by Custom Field
find-subscribers-by-custom-field Find subscribers by a custom field's value (GET /fb/subscriber/findByCustomField). Works with Text and Number fields ONLY. Capped at 100, sorted by most recent update, no pagination.
Find Subscribers by Name
find-subscribers-by-name Search subscribers by FULL name (GET /fb/subscriber/findByName). Capped at 100 results with no pagination — a lookup, not an export.
Get Page Info
get-page-info Read the Page this connection's token belongs to (GET /fb/page/getInfo) — name, username, category, timezone and the `is_pro` plan flag. Takes no parameters.
Get Subscriber
get-subscriber Read one subscriber in full (GET /fb/subscriber/getInfo) — cross-channel identity, tags, custom field values, opt-in flags, and `last_interaction` (the 24-hour-window clock).
List Bot Fields
list-bot-fields Every Page-global bot field WITH its current value (GET /fb/page/getBotFields) — `{ id, name, type, description, value }`. One value per Page, not per subscriber.
List Custom Fields
list-custom-fields Every subscriber custom-field definition on the Page (GET /fb/page/getCustomFields) — `{ id, name, type, description }`. Definitions only; values live on the subscriber.
List Flows (Automations)
list-flows Every Automation on the Page plus its folder tree (GET /fb/page/getFlows). Returns `data.flows` and `data.folders`. A flow's `ns` is the id Send Flow takes.
List Growth Tools
list-growth-tools Every Growth Tool (opt-in widget, ref link, comment trigger, overlay) on the Page (GET /fb/page/getGrowthTools) — `{ id, name, type }`.
List OTN Topics
list-otn-topics Every One-Time Notification topic on the Page (GET /fb/page/getOtnTopics) — `{ id, name, description }`. Send Content's `otnTopicName` takes the name from here.
List Tags
list-tags Every tag on the Page (GET /fb/page/getTags), as `{ id, name }`. Unpaginated — the response is the whole list.
Remove Subscriber Tag
remove-subscriber-tag Take a tag off ONE subscriber (POST /fb/subscriber/removeTag or /fb/subscriber/removeTagByName). The tag itself survives — to delete it Page-wide, see Delete Tag.
Send Content
send-content Send an ad-hoc message built in Manychat's Dynamic Block format (POST /fb/sending/sendContent). Outside Meta's 24-hour window this is refused unless a `messageTag` or `otnTopicName` is supplied. Success means accepted, not delivered.
Send Flow
send-flow Send an existing Manychat Automation to a subscriber (POST /fb/sending/sendFlow). Takes the flow's `ns` from List Flows. Capped at 100 sends per subscriber per hour.
Set Bot Field
set-bot-field Set one Page-global bot field by id or by name (POST /fb/page/setBotField or /fb/page/setBotFieldByName). Absolute write — safe to retry.
Set Bot Fields (batch)
set-bot-fields Set several Page-global bot fields in one call (POST /fb/page/setBotFields). Manychat's schema marks `field_id`, `field_name` AND `field_value` required on each element — supply what you have; elements are forwarded verbatim.
Set Subscriber Field
set-subscriber-field Set one custom field on one subscriber, by field id or name (POST /fb/subscriber/setCustomField or /fb/subscriber/setCustomFieldByName). Field names are not case sensitive. The field must already exist.
Set Subscriber Fields (batch)
set-subscriber-fields Set several custom fields on one subscriber in one call (POST /fb/subscriber/setCustomFields). Manychat's schema marks `field_id`, `field_name` AND `field_value` required on each element — elements are forwarded verbatim.
Update Subscriber
update-subscriber Update a subscriber's system fields (POST /fb/subscriber/updateSubscriber). Unset params are omitted, never nulled. Manychat publishes no way to change `whatsapp_phone` here.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Manychat's real ids.
{
"manifestVersion": "2",
"name": "manychat-example",
"steps": [
{
"id": "add-subscriber-tag",
"uses": {
"app": "io.w6w.manychat",
"action": "add-subscriber-tag",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"subscriberId": "<subscriberId>"
}
}
]
}Here are some of the things you can do
-
Add Subscriber Tag
performadd-subscriber-tag -
Create Bot Field
performcreate-bot-field -
Create Custom Field
performcreate-custom-field -
Create Subscriber
performcreate-subscriber -
Create Tag
performcreate-tag
+20 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Manychat, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Manychat. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "send-content",
payload: {
subscriberId: "<value>",
data: "<value>",
// messageTag: "<value>",
// otnTopicName: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action send-content --payload '{"subscriberId":"<value>","data":"<value>"}'Give an AI agent Manychat — without giving it Manychat's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.manychat#add-subscriber-tag",
"input": {
"subscriberId": "<subscriberId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Manychat connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Manychat's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Manychat itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Manychat declares its own checks, so its health is a property of the app rather than something the host guesses at.
Manychat platform status
Instatus per-component status for status.manychat.com. The verdict tracks the `Manychat: Public API` component; the other ten are reported for attribution only. Unauthenticated and unsigned.