The Make integration connects ChatbotX with external apps and automated processes. You can send customer data from a Flow to Make, update contacts, or send another Flow 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.
How the integration works
In Make, a scenario is an automated process made of connected modules. The ChatbotX integration uses the ChatConnectX app with three main components:
The usual setup order is: install ChatConnectX, create a Connection, choose a Trigger, add an Action, and test the scenario.
Install ChatConnectX and connect your workspace
Install the ChatConnectX app
The Connect button in ChatbotX opens the ChatConnectX installation page in Make. You create and manage scenarios directly in Make.
Open ChatConnectX from Integrations
In ChatbotX, select Settings from the left menu and open Integrations. Find Make, then select Connect to open ChatConnectX in Make. Install the app
On the ChatConnectX page, select Install. Select an organization
Select the organization where you want to install the app. Your Make account needs the Admin, Owner, or App Developer role. Select Install to finish.
Connect only opens the ChatConnectX app in Make. You install the app, create scenarios, and enable scenarios in Make.
Create a Connection
A Connection gives Make access to the correct ChatbotX workspace. Create it once, then reuse it in other ChatConnectX modules.
Open the Connection dialog
In a ChatConnectX module, select Add next to Connection.
Name the Connection
Enter a recognizable name in Connection name, such as ChatbotX Production.
Enter the Workspace token
In ChatbotX, open Settings > Integrations > Workspace token and copy the token. Paste it into Workspace token in Make. Save the Connection
Select Save, then select the new Connection in the module.
A Workspace token provides access to workspace data. Do not include it in screenshots, emails, or public documentation. Stop using a token if it has been exposed.
ChatConnectX Triggers
ChatConnectX provides two Triggers that can start a scenario:
Watch events
Use this Trigger with ChatbotX Webhooks to start a scenario when Make receives a subscribed event. Watch flow data
Use this Trigger when an Actions > Triggers > Make block in a Flow sends data to Make.
Receive data from a Make block in a Flow
When a Flow uses an Actions > Triggers > Make block, select Watch flow data as the scenario Trigger. The event names on both platforms must match.
Create a Make block in a ChatbotX Flow
Open the Flow
In ChatbotX, open the Flow that should send data to Make and select the appropriate message node.
Add the Make block
Select Create, then choose Actions > Triggers > Make to add the block to the message node. 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
Create a new scenario
In Make, select Scenarios, then create a New scenario.
Add ChatConnectX
In the first module, search for and select ChatConnectX. Choose Watch flow data
Select Watch flow data so Make can receive data sent from the ChatbotX Flow. Create a webhook and choose a Connection
Select Create a webhook, enter a webhook name, and choose the existing Connection. If no Connection exists, select Add and enter the Workspace token.
Enter the Event name
In Event name, enter the exact name used in Events on the Make block, such as make_trigger, then select Save. Run the scenario once
Select Run once so Make starts waiting for sample data.
Send data from ChatbotX
Run the Flow that contains the Actions > Triggers > Make block. When the data arrives, Make displays the result in Operation 1.
The webhook Event name must exactly match the name in Events on the Make block. If the names differ, Make does not receive data from the Flow.
The sample output can include Event, Contact, Custom Fields, Tags, and Contact Sequences. Use these fields to map data into the next module.
An Action is a module that runs after a Trigger. It receives data from previous modules and performs a task in your ChatbotX workspace.
Add a new module
In the Make scenario, select the + after the Trigger module.
Choose ChatConnectX
Search for ChatConnectX, then select the appropriate Action. Configure the Action
Choose the Connection, complete the required fields, and map data from the previous module. Select Save when finished.
Send content and perform advanced tasks
Delete a contact permanently deletes the contact and cannot be undone. Check the contact identifier before running the scenario with live data.
Example: Send a Flow with Make
Suppose Make receives customer information from an external form. Use Send flow to send a confirmation or consultation Flow through the contact’s most recently used channel.
Choose Send flow
Add a new ChatConnectX module and select Send flow. Choose a Connection
Select the existing Connection. If no Connection exists, select Add to create one.
Enter the Contact identifier
Enter or map the contact identifier. You can use the Contact ID from the Trigger. Make also accepts id:123456, email:user@example.com, or phone:+84912345678.
Choose the Flow
Enter the ID of a published Flow. Enable Map if the Flow ID comes from a previous module.
Choose an Inbox
Choose an Inbox to send through a specific channel. Leave it empty to use the contact’s most recently used channel.
Save and test
Select Save, then select Run once to test the scenario.
The contact must already have a conversation before receiving a Flow. If Inbox is empty, ChatbotX uses the contact’s most recently used channel.
Test the scenario before enabling it
Receive sample data
Select Run once in Make, then run the Flow or data source that should activate the Trigger.
Check the output
Open Operation 1 and confirm that the required fields contain the correct data.
Check the Action
Confirm that the Action succeeds and the contact receives the correct content or data update.
Enable the scenario
After a successful test, enable the scenario schedule so Make can process future runs automatically.
If the scenario does not run, check the Connection, the data in the Operation, and the scenario’s enabled status.