Skip to main content
The Make integration connects ChatbotX with external apps and automated processes through Make scenarios. You can send customer data from a Flow to Make, update contacts, or trigger another Flow — all without manual work. For example, after a customer completes a consultation form in ChatbotX, Make can add the information to your CRM and send a confirmation Flow back through ChatbotX.

How the Integration Works

In Make, a scenario is an automated process built from connected modules. The ChatbotX integration uses the ChatConnectX app, which provides three main components: The typical setup order is: install ChatConnectX → create a Connection → choose a Trigger → add an Action → test the scenario.

Install ChatConnectX and Connect Your Workspace

Install the ChatConnectX App

1

Open ChatConnectX from Integrations

In ChatbotX, select Settings from the left menu and open Integrations. Find Make, then click Connect to open the ChatConnectX app page in Make.
2

Install the app

On the ChatConnectX page in Make, select Install.
3

Select an organization

Choose the Make organization where you want to install the app. Your Make account must have the Admin, Owner, or App Developer role. Select Install to finish.
The Connect button in ChatbotX only opens the ChatConnectX app page in Make. You create scenarios, configure modules, and enable schedules entirely within the Make platform.

Create a Connection

A Connection gives Make access to the correct ChatbotX workspace. Create it once and reuse it across all your ChatConnectX modules.
1

Open the Connection dialog

In any ChatConnectX module in Make, select Add next to Connection.
2

Name the Connection

Enter a recognizable name such as ChatbotX Production.
3

Enter the Workspace token

In ChatbotX, go to Settings → Integrations → Workspace token and copy the token. Paste it into the Workspace token field in Make.
4

Save the Connection

Select Save, then select the new Connection in the module.
A Workspace token provides access to all workspace data. Never share it in screenshots, emails, or public documentation. If a token is exposed, rotate it immediately.

ChatConnectX Triggers

ChatConnectX provides two Triggers that can start a Make scenario:

Watch Events

Use this Trigger together with ChatbotX Webhooks to start a scenario when Make receives a subscribed event from ChatbotX.

Watch Flow Data

Use this Trigger when an Actions → Triggers → Make block inside a ChatbotX Flow sends data to Make.

Create a Make Block in a ChatbotX Flow

1

Open the Flow

In ChatbotX, open the Flow that should send data to Make and select the appropriate message node.
2

Add the Make block

Select Create, then choose Actions → Triggers → Make to add the block to the node.
3

Name the event

Select Edit on the Make block. In Events, enter an event name such as make_trigger, then select Save.

Set Up Watch Flow Data in Make

1

Create a new scenario

In Make, select Scenarios, then create a New scenario.
2

Add ChatConnectX

In the first module, search for and select ChatConnectX.
3

Choose Watch flow data

Select Watch flow data so Make can receive data from the ChatbotX Flow.
4

Create a webhook and choose a Connection

Select Create a webhook, enter a webhook name, and choose your existing Connection. If no Connection exists yet, select Add and enter the Workspace token.
5

Enter the Event name

In Event name, enter the exact name used in Events on the Make block in ChatbotX (e.g., make_trigger), then select Save.
6

Run once to capture sample data

Select Run once so Make begins waiting for incoming data.
7

Trigger from ChatbotX

Run the Flow that contains the Make block. When data arrives, Make displays the result in Operation 1.
The webhook Event name in Make must exactly match the name in Events on the Make block in ChatbotX. If they differ, Make will not receive any data.
The sample output can include Event, Contact, Custom Fields, Tags, and Contact Sequences. Map these fields into the next module in your scenario.

Perform Actions in ChatbotX

An Action is a module that runs after a Trigger. Add one by clicking the + after the Trigger module in your Make scenario, searching for ChatConnectX, and selecting the appropriate Action.

Manage Contacts

Update Tags and Custom Fields

Send Content and Perform Advanced Tasks

Delete a contact is permanent and cannot be undone. Always verify the contact identifier before running a scenario with live data.

Example: Send a Flow with Make

Suppose Make receives customer information from an external form. Use Send flow to deliver a confirmation or consultation Flow through the contact’s most recently used channel.
1

Choose Send flow

Add a new ChatConnectX module to your scenario and select Send flow.
2

Choose a Connection

Select your existing Connection, or click Add to create one.
3

Enter the Contact identifier

Enter or map the contact identifier. You can use the Contact ID from the Trigger output. Make also accepts id:123456, email:user@example.com, or phone:+84912345678.
4

Choose the Flow

Enter the ID of a published Flow. Enable Map if the Flow ID comes from a previous module.
5

Choose an Inbox

Select a specific Inbox to send through a particular channel, or leave it empty to use the contact’s most recently active channel.
6

Save and test

Select Save, then select Run once to test the scenario.
The contact must already have an existing conversation before they can receive a Flow through Make. If Inbox is left empty, ChatbotX uses the contact’s most recently used channel.

Test the Scenario Before Enabling It

1

Receive sample data

Select Run once in Make, then trigger the Flow or data source that should activate the Trigger.
2

Check the output

Open Operation 1 and confirm that all required fields contain the correct data.
3

Verify the Action

Confirm that the Action succeeds and the contact receives the correct content or data update in ChatbotX.
4

Enable the scenario

After a successful test, enable the scenario schedule so Make processes future runs automatically.
If the scenario does not run, check the Connection status, review the data in the Operation output, and confirm the scenario’s enabled status in Make.