Resources · Make integration

Chatfuel Make integrationAutomate Chatfuel with Make.

Can your Chatfuel bot hand a question to Make and get an answer back? Yes. The Chatfuel Make integration gives you 4 modules: 1 instant trigger and 3 actions. This guide is for bot owners new to Make, from the connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you do with the Chatfuel Make integration?

The Chatfuel Make integration links your Chatfuel bot to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that listens or acts. Your bot can send data to Make, and Make can answer the bot, push a broadcast or bring a user back into the conversation.

Answer a bot user with data from another tool. JSON Listener receives what Chatfuel's JSON API plugin sends, Make fetches what it needs in your other apps, and JSON Response hands the reply back to the conversation.

Bring a quiet contact back. Send a Reengage Message sends any block of your bot's structure, or updates user attributes, when something happens elsewhere, such as a new order in an online shop.

Announce news to your audience. Broadcast Message creates a broadcast in your Chatfuel account from a scenario, so an event in another app can be the starting point.

What Make does not offer here: Chatfuel has no Make an API Call module and no search module. If you are still weighing the tools, read the n8n vs Make comparison, and check Make pricing before you scale. For a guided start, the Make training covers the editor step by step.

Connect

How do you connect Chatfuel to Make?

  1. 01

    Add a Chatfuel module

    Open your scenario, click the +, search for Chatfuel and pick a module. Then click Create a connection. A connection is your Chatfuel account linked to Make once, and every Chatfuel module reuses it.

  2. 02

    Name it and authorize Make

    Give the connection a name if you want to spot it later, the name of the bot works well. Then authorize Make on the Chatfuel page that opens, or paste the key Chatfuel gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. The connection now shows in the module and you can fill in its fields. You only do this once: the next Chatfuel module you add offers the same connection in its list.

First scenario

Your first scenario: reply to a bot user from Make

GoalWhen a user reaches the JSON API plugin in your Chatfuel bot, Make receives the message and sends a reply back to the conversation.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Search for Chatfuel and pick JSON Listener, the instant trigger.

  2. 02

    Link your account

    Click Create a connection (or Add) and link your Chatfuel account. The trigger now waits for the messages your bot's JSON API plugin sends to Make.

  3. 03

    Run it once first

    Click Run once, then write to your bot so the message reaches the plugin. Make shows the bundle it received, one item passed between modules, and the user attributes become available.

  4. 04

    Add the reply

    Click the + on the right of JSON Listener and add JSON Response. Map data from the trigger into it, such as an attribute your bot collected, so the answer feels personal.

  5. 05

    Test and switch it on

    Click Run once again and read what each module received. When the reply looks right, switch the scenario on: each message from the plugin then starts it at once.

Triggers

What starts a Chatfuel scenario?

1 module starts a scenario when something happens in Chatfuel. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Chatfuel as soon as it happens.

Chatfuel1JSON Listener

JSON Listener

Instant trigger

In MakeListens for incoming messages from Chatfuel's JSON API plugin. The enclosing scenario has to be run once, in order for user attributes from Chatfuel to become visible and available for mapping.

JSON Listener opens a door in Make for your Chatfuel bot: whenever the bot's JSON API plugin sends a message, your scenario starts and receives the data of that user.

How it fires
instant. Chatfuel calls Make through a webhook as soon as the message goes out, so there is no schedule to set.
When to use it
a step of your bot needs information that lives outside Chatfuel, like the status of an order or a free slot, and the bot should reply with it.
Watch out
run the scenario once before you map anything. Until that first run, Make cannot see the user attributes Chatfuel sends.
Modules

What can Make do in Chatfuel?

Chatfuel gives you 3 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

2 modules
Chatfuel1

Broadcast Message

ActionIn the docs only

Broadcast Message creates a broadcast in your Chatfuel account, a message meant for your bot's audience rather than for one person. With Make, an event in another app decides when it goes out.

When to use it
a new product lands in your catalog or registrations open for an event, and your subscribers should hear about it from the bot.
Watch out
the official doc gives no description of this module, so check its fields and test with Run once before you switch the scenario on.
Chatfuel2

JSON Response

Action

In MakeSends a response to the address from which a message was received.

JSON Response sends your answer back to the address the message came from, so the user who wrote to the bot gets a reply built by Make. It is the other half of JSON Listener.

When to use it
as the last step of a scenario started by JSON Listener, right after the modules that fetched or prepared the answer in your other apps.

Other modules

1 module
Chatfuel3

Send a Reengage Message

Action

In MakeSends any block from the bot's structure or sets user attributes.

Send a Reengage Message pushes any block of your bot's structure to a user, or sets that user's attributes, straight from a scenario. It lets Make speak first instead of waiting for the contact.

When to use it
something happens in another tool, like a form submitted or a payment confirmed, and the bot should pick the conversation back up with the right block.
Watch out
the module sends a block from the bot's structure, so build that block in Chatfuel before you set up the scenario.
Need help

Need help automating Chatfuel with Make?

A person reads every message.

FAQ

Chatfuel and Make: common questions

01Is the Chatfuel Make integration free?
Yes. Chatfuel is a standard app in Make, so its 4 modules work on 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. The interval applies to scheduled triggers, and JSON Listener is an instant one. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios, allow a 1-minute interval and count usage in credits, one operation being one module run on one bundle.
02What do you need to connect Chatfuel to Make?
A Chatfuel account, and that is all the official doc asks for. In a scenario, add any Chatfuel module and click Create a connection, give it a name if you like, then authorize Make on the Chatfuel page or paste the key Chatfuel provides, and click Save. The connection is stored once and every Chatfuel module in your scenarios reuses it. To receive messages with JSON Listener, your bot relies on Chatfuel's JSON API plugin, the part that sends data to Make.
03Does the Chatfuel trigger in Make fire in real time?
Yes. JSON Listener is an instant trigger: Chatfuel calls Make through a webhook as soon as the JSON API plugin sends a message, and the scenario starts right away, without waiting for a schedule. The other three modules are actions, so they run when the scenario reaches them. One detail catches beginners: click Run once before mapping, because Make only shows the user attributes from Chatfuel after that first run. Then switch the scenario on and it keeps listening.
04What if a Chatfuel module is missing in Make?
It depends on what you need. Chatfuel has no Make an API Call module, so you cannot add your own request to Chatfuel from Make: what the 4 modules do is all you get. The 4 modules cover receiving a message, replying to it, creating a broadcast and re-engaging a user with a block or attributes. For anything else, look for another app in Make that handles that step, or describe your case to the team through the help form on this page so it can suggest a workaround.
05Should you use Make or n8n for Chatfuel?
It depends on where the rest of your stack already runs. In Make, Chatfuel comes as a native app with 4 modules, including an instant trigger, and you build the whole flow in a visual editor with a Free plan to start. The same app often has an n8n node as well, so check that it covers the steps your bot needs before choosing. A practical rule: pick the tool that already connects your other apps, so bot data does not travel across two platforms.