> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/manychat.md).

# Manychat

Generate a Manychat API token and connect the Appmixer Manychat connector.

The Appmixer Manychat connector (**Get Subscriber**, **Find Subscribers**, **Update Subscriber**, **Create Tag**, **Delete Tag**, **List Tags**, **Add Tag to Subscriber**, **Remove Tag from Subscriber**, **List Custom Fields**, **Set Custom Field**, **List Flows**, **Send Flow**, **Send Content**, **Make API Call**) uses **API key** authentication. You do not need to register an app with Manychat. Each user generates an API token in their Manychat account and enters it when they connect Manychat in Appmixer.

{% hint style="warning" %}
The Manychat API is only available on the Manychat **Pro** plan. Without it you cannot generate a token, and API calls fail.
{% endhint %}

***

## 1. Generate an API token

1. Sign in to [Manychat](https://app.manychat.com) and open the account you want to connect.
2. Go to **Settings → API**.
3. Click **Generate your API Key**.
4. Copy the whole token. It looks like `1234567:0123456789abcdef…`: the account (page) ID, a colon and a hash.

{% hint style="info" %}
A Manychat token belongs to one Manychat account (page). To work with several accounts, generate a token in each of them and create one Appmixer connection per account. If you refresh or delete the token in Manychat, connections that use the old token stop working.
{% endhint %}

***

## 2. Connect in Appmixer

When you add a Manychat component to a flow, Appmixer asks you to connect an account. Paste the token into the **API Token** field. Do not add the word `Bearer`.

Appmixer sends the token as a bearer token (`Authorization: Bearer <token>`) to `https://api.manychat.com`. To check the token, it calls `GET /fb/page/getInfo`. The connection is named after the Manychat account the token belongs to.

**Make API Call** only sends requests to `https://api.manychat.com`. It rejects other hosts and URLs that contain credentials, so the token is never sent anywhere else.

***

## 3. Account limitations

### Creating contacts needs contact import enabled by Manychat

The connector works with contacts that came to Manychat through a channel (a message, a comment, a sign-up widget). It has no component that creates contacts.

Manychat lets an account create contacts through the API (by email, phone or WhatsApp number) only after Manychat support enables contact import for it. Without it, the API answers `Permission denied to import email` (or the same message for phone), even when the email or SMS opt-in is off. Manychat reviews each request: expect questions about your business, how you collected the contacts, whether they consented to receive messages, and evidence of that consent. It declines requests it cannot verify.

If your account has contact import enabled, create contacts with **Make API Call**: method `POST`, path `/fb/subscriber/createSubscriber`, and a JSON body such as `{"first_name": "Jane", "email": "jane@example.com", "has_opt_in_email": true, "consent_phrase": "…"}`. Creating a contact by phone or WhatsApp number also needs the matching channel (SMS or WhatsApp) connected in Manychat.

### Sending works only for contacts reachable on a channel

**Send Content** and **Send Flow** deliver to a contact that already talks to the account on a connected channel (Messenger, Instagram, WhatsApp or Telegram). Pick the contact's channel in **Send Content**: a message on a channel the contact does not use fails.

* **Messenger and Instagram:** Meta allows messages only within 24 hours after the contact's last message. Outside that window, Manychat delivers only messages sent with a **Message Tag** that fits the content, and rejects the rest.
* **WhatsApp:** outside the 24-hour window, only pre-approved message templates can be sent; start such a template from a Manychat flow with **Send Flow**.
* **Telegram:** there is no messaging window.

**Send Flow** starts a published Manychat flow. Its steps must have content for the contact's channel.

***

## Rate limits

Manychat sets limits per endpoint: 10 requests per second for most subscriber and tag calls, and higher limits for some reads. The connector queues requests at 10 requests per second for each Appmixer user.

***

## Troubleshooting

* **"Invalid Manychat API token" when connecting:** check that you copied the whole token, including the part before the colon, and that it has not been refreshed or deleted under **Settings → API**.
* **Other errors when connecting:** the connector only reports an invalid token on a 401 response. Other messages come from Manychat, for example when the account is not on the Pro plan.
* **Make API Call to `createSubscriber` fails with "Permission denied to import email":** contact import is not enabled for the Manychat account. See [Creating contacts needs contact import enabled by Manychat](#creating-contacts-needs-contact-import-enabled-by-manychat).
* **Send Content or Send Flow fails for a Messenger or Instagram contact:** the contact has not written to the account in the last 24 hours. Add a fitting **Message Tag**, or wait until the contact writes again. See [Sending works only for contacts reachable on a channel](#sending-works-only-for-contacts-reachable-on-a-channel).
* **Make API Call fails with "API Endpoint Path must target <https://api.manychat.com>":** use a path such as `/fb/page/getTags` or a full URL on `https://api.manychat.com`.

***

## Backoffice configuration

Configuration ID: `appmixer:manychat`. For how to set connector configuration values, see [Connector Configuration](https://docs.appmixer.com/getting-started/services).

You do not need any Backoffice configuration to authenticate, because every user enters their own API token. There are two optional keys:

* `listCacheTTL`: optional. How long, in milliseconds, the lists of tags, custom fields and flows shown in the Inspector dropdowns are cached. **Set Custom Field** also uses this cache to look up the field type. The default is `120000` (2 minutes).
* `outputFilePrefix`: optional. A prefix for the names of CSV files created when **Find Subscribers**, **List Tags**, **List Custom Fields** or **List Flows** runs with the **Store to CSV file** output type. Files are named `<prefix>-<component label in the flow>.csv`. The default is `manychat-objects-export`.

```bash
appmixer service-config set appmixer:manychat -u -d '{
  "listCacheTTL": 120000,
  "outputFilePrefix": "manychat-objects-export"
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/manychat.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
