Resources · Make integration

ChatData Make integrationAutomate ChatData with Make.

Can Make pass your chatbot's leads and escalations to the rest of your stack? Yes. The ChatData Make integration gives you 11 modules: 3 triggers and 8 actions. This guide covers the API key, a first scenario and every module, in plain English.

Try the ChatData integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ChatData Make integration do for you?

The ChatData Make integration links your ChatData account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick, either a trigger that starts the run or an action that does something in ChatData. You connect once with an API key, and every ChatData module reuses that connection.

Leads that land where sales works. Watch Lead Submission starts a scenario when your chatbot collects a lead, so the contact can be passed to your CRM or a shared sheet without anyone copying it by hand. Get the Leads covers the other case, when you want to pull the list on demand.

Escalations that nobody misses. Watch Live Chat Escalation fires when a visitor asks for a human. Pair it with a messaging app, such as the one described on the 2Chat Make integration page, and the support team gets pinged at the next check instead of watching the dashboard.

Bots managed from your own tools. Create a Chatbot, Update the Base Prompt and Get the Chatbot Training Status let an agency or a product team set up and adjust bots from a scenario rather than the ChatData dashboard.

Limits worth knowing: the Make documentation for this app gives no field list and no module descriptions, and it flags its own text as AI-generated, to be checked against ChatData. The 3 triggers are listed as scheduled, so Make polls ChatData instead of being called; the clock badge on each module confirms it in the editor. ChatData can also be wired in n8n; the n8n vs Make comparison lays out the differences, and the Make training helps if Make is new to you.

Connect

How do you connect ChatData to Make?

  1. 01

    Generate an API key in ChatData

    In your ChatData dashboard, open the Chatbots section and pick the bot you want to automate. Go to its API Keys tab, click Generate API Key, then copy the key shown in the window.

  2. 02

    Add a ChatData module in Make

    In your scenario, add any ChatData module and click Create a connection. The Connection name field is optional, but a clear name such as the bot's name helps when you run several bots.

  3. 03

    Paste the key and save

    Paste the API key you copied and confirm. Make stores it as a connection, meaning your ChatData account linked once, and every other ChatData module in any scenario can pick it from the list.

First scenario

Your first scenario: a chatbot for each new client

GoalWhen a new client is added in another app, Make creates a ChatData chatbot and reads its training status.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Pick the app that holds your clients, such as a CRM or a form tool, and choose the module that watches new records.

  2. 02

    Add Create a Chatbot

    Click the + to the right of the first module, search ChatData and choose Create a Chatbot. Pick your connection. Then map the client name from the previous module into whichever fields Make shows you.

  3. 03

    Check the training

    Add Get the Chatbot Training Status after it and map the chatbot returned by Create a Chatbot. Each bundle, one item moving from module to module, now carries the new bot and its status.

  4. 04

    Test with Run once

    Click Run once and add a test client in the source app. Open the bubbles above each module to read what it received and what it sent back.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Save, then turn the scenario on.

Triggers

What can start a ChatData scenario?

3 modules start a scenario when something happens in ChatData. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by ChatData as soon as it happens.

ChatData1Watch Lead Submission

Watch Lead Submission

triggerIn the docs only

Hands each lead your chatbot captures to the next module, so the contact can reach a CRM, a sheet or an inbox without a copy and paste.

How it fires
scheduled. Make checks ChatData on the scenario's schedule, so a lead shows up at the next check rather than the second it is typed.
When to use it
a bot on a pricing page that asks visitors for an email before a demo request.
Watch out
each check that finds new leads uses operations, the unit Make counts on your plan, so a short interval adds up.
ChatData2Watch Live Chat Escalation

Watch Live Chat Escalation

triggerIn the docs only

Lets a scenario react when a conversation needs a person, which is the moment your team most wants to hear about.

How it fires
scheduled. Make polls ChatData at the interval set on the scenario's clock, so the alert waits for the next poll.
When to use it
pinging the on-call support agent in a chat app when the bot hands over.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, which may be too slow for live support; paid plans go down to 1 minute.
ChatData3Watch New Message

Watch New Message

triggerIn the docs only

Gives you each new message from your bot's conversations as its own bundle, ready to log, sort or forward.

How it fires
scheduled. Make looks for new messages each time the scenario's schedule comes round, not the instant a visitor writes.
When to use it
building a log of questions in a spreadsheet so the team can spot what the bot answers badly.
Watch out
messages outnumber leads by far, and every bundle a later module processes costs an operation, so filter early.
Modules

What can Make do in ChatData?

ChatData gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

ChatData1

Create a Chatbot

ActionIn the docs only

Sets up a fresh ChatData bot from inside a scenario, so launching a new assistant no longer means a trip to the dashboard.

When to use it
an agency spinning up one bot per client once the contract is recorded.
Watch out
the doc lists no fields for this module; open it in the editor to see what it asks for before you map anything.
ChatData2

Get the Chatbot Training Status

ActionIn the docs only

Tells the scenario where a bot stands in its training, which is useful before you let it answer real visitors.

When to use it
right after Create a Chatbot or Update the Base Prompt, to decide whether the next step can run.
Watch out
the doc does not describe the possible status values, so read them in a Run once test before you build a filter on them.
ChatData3

Get the Conversations

ActionIn the docs only

Pulls the conversations of a chatbot into Make on demand, a good fit for a report or an archive rather than a live alert.

When to use it
exporting chats to a data tool after a product launch to see what visitors asked.
Watch out
if you need each new exchange as it comes, Watch New Message is the better starting point.
ChatData4

Get the Leads

ActionIn the docs only

Fetches the leads your bot has already collected, so you can catch up on older contacts or rebuild a list after a CRM change.

When to use it
a one-off import of past leads before switching on Watch Lead Submission.
Watch out
running it and the trigger side by side can create duplicates; check for an existing contact before you add one.
ChatData5

Insert a Message

ActionIn the docs only

Adds a message to a ChatData conversation from your scenario, which keeps the chat history complete when part of the exchange happens elsewhere.

When to use it
recording an agent's reply sent from a help desk tool so the conversation reads in full.
Watch out
the doc does not say how it differs from Send a Message, so compare both with Run once on a test chat.
ChatData6

Make an API Call

ActionIn the docs only

Reaches any endpoint of the ChatData API with the connection you already set up, for the cases the other ten modules leave out.

When to use it
a need that none of the listed modules covers, once you have found the endpoint in ChatData's own API docs.
Watch out
here you write the request yourself, so keep it for gaps and prefer a ready-made module when one exists.
ChatData7

Send a Message

ActionIn the docs only

Judging by its name, it puts a message to your chatbot from Make, handy for testing answers or feeding it a question that came from another channel.

When to use it
checking, after Update the Base Prompt, that the bot now gives the answer your team expects.
Watch out
the doc gives no detail on what the reply looks like; read the output bundle in a test run before mapping it further.
ChatData8

Update the Base Prompt

ActionIn the docs only

Rewrites the core instructions of a bot from a scenario, so tone or scope changes can come from a shared doc instead of the dashboard.

When to use it
a marketing team that keeps approved wording in a sheet and pushes it to the bot once it is signed off.
Watch out
every conversation with that bot is affected, so try the new prompt on a test bot first.
Need help

Need help automating ChatData with Make?

A person reads every message.

FAQ

ChatData and Make: common questions

01Is the ChatData Make integration free?
Yes, on the Make side. ChatData is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios, allow a 1 minute interval and count usage in credits each month. You still need an active ChatData account, which ChatData bills on its own terms.
02What do you need to connect ChatData to Make?
An active ChatData account and an API key. In ChatData, open the Chatbots section, choose the bot, go to the API Keys tab and click Generate API Key, then copy the key. In Make, add a ChatData module, click Create a connection, name it if you like and paste the key. The key belongs to one chatbot, so a second bot needs its own connection. After that, every ChatData module can reuse the connection.
03Does the ChatData trigger react in real time?
No. The 3 ChatData triggers, Watch Lead Submission, Watch Live Chat Escalation and Watch New Message, are scheduled. Make checks ChatData on the schedule set on the first module, every 15 minutes by default. On the Free plan that is also the fastest interval; paid plans go down to 1 minute. For a live chat escalation, that delay matters, so pick the interval with your support team's response time in mind.
04What if a ChatData module is missing in Make?
Use Make an API Call. It calls any endpoint of the ChatData API with the connection you already created, so you are not limited to the 8 actions listed. Find the endpoint in ChatData's API documentation, then test the call with Run once. Also note that the Make documentation for this app is marked as AI-generated and gives no field details, so check important behavior directly in ChatData before relying on it.
05Should you use Make or n8n for ChatData?
It depends on the tool your team already runs. ChatData often exists as an n8n node too, so the choice rarely hinges on the app itself. In Make, you get 11 ready modules, including 3 scheduled triggers, plus Make an API Call for the rest, all behind one API key connection. Compare the modules each tool offers for ChatData against the exact flows you plan, then choose the one your team will maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations