01Who this is for
- Digital marketers who capture leads in ManyChat and need those leads in HighLevel for follow up.
- Agencies managing multiple client accounts that require a single source of truth for contact information.
02Manychat to HighLevel integration, explained
The integration uses ManyChat’s External Request block to call HighLevel’s API endpoints. When a user provides an email, phone or name in a chat flow, the block sends a JSON payload to the designated endpoint. HighLevel then creates a new contact or updates an existing one based on the supplied email address.
The request includes required HTTP headers, an Authorization header with a bearer API key and a Content Type header set to application/json. The body contains fields such as first_name, last_name, email and phone, wrapped in JSON syntax. If the contact already exists, HighLevel updates the record instead of creating a duplicate.
This feature lives inside ManyChat’s flow builder, not within the HighLevel UI. It relies on the external request capability of ManyChat and the public API of HighLevel.
03How businesses use manychat to HighLevel integration
- Digital marketing agency. The agency builds a chat flow that captures visitor details, then adds an External Request block pointing to the HighLevel contact endpoint. The payload includes the visitor’s name, email and phone so the agency’s contact list right away reflects the new lead.
- Online course provider. The provider sets up an External Request to the HighLevel opportunity endpoint, sending the student’s email and a tag for the specific course. This creates or updates the contact and records the enrollment opportunity automatically.
- Fitness studio. The studio uses an External Request to add a new contact in HighLevel whenever a chat user books a class, ensuring the studio’s contact list stays current without manual data entry.
04The numbers and rules that matter
- Data fields example: { “email”: “john@deo.com”, “phone”: “+18887324197”, “firstName”: “John”, “lastName”: “Deo”, “tags”: [“commodo sed aliquip”, “ut exercitation sunt”] }.
05Before you start
- A valid HighLevel API key must be available.
- Access to ManyChat’s External Request block is required.
06How to set up and use manychat to HighLevel integration in HighLevel
Set up external request in ManyChat
- Open the ManyChat flow editor and add an External Request block.
- Enter the appropriate HighLevel API endpoint URL for creating or updating a contact.
- Add two headers: AUTHORIZATION set to Bearer followed by your API key, and Content Type set to application/json.
- Paste the JSON body using placeholders for first_name, last_name, email and phone as shown in the article.
07Settings that matter
- AUTHORIZATION. Specifies the bearer token that authenticates the request with HighLevel.
- Content Type. Indicates that the request payload is formatted as JSON.
- first_name. Maps the chat user’s first name to the HighLevel contact field.
- last_name. Maps the chat user’s last name to the HighLevel contact field.
- email. Provides the contact’s email address, which HighLevel uses to match existing records.
- phone. Supplies the contact’s phone number for HighLevel’s record.
08Things to know before you rely on it
- Support for the API and ManyChat integration is not provided by the HighLevel support team.
- Duplicate contacts can appear if the request creates rather than updates a record; use the update pattern to avoid this.
09If something goes wrong
- Duplicate contacts appear in HighLevel after ManyChat submissions.. Configure the External Request to update an existing contact instead of creating a new one, using the example payload shown in the article.
10How it connects to the rest of HighLevel
- Learn how to use custom fields in HighLevel for additional data capture. Custom fields
- Explore inbound and outbound webhook setup, which can complement the ManyChat integration. Webhooks guide
- Review HighLevel pricing and plans to ensure your account includes API access. Pricing
Michael's take

Manychat often captures leads, but without a connection to your HighLevel account the data stays separate.
Setting the AUTHORIZATION header with a valid API key is essential; without it, the request will not reach HighLevel.