Resources · Make integration

ChatNode Make integrationAutomate ChatNode with Make.

What if your ChatNode bot could answer questions that never reach your chat widget? The ChatNode Make integration gives you 2 action modules. This page is for support and ops teams: it shows how to link your account and build a first scenario that asks your bot and reuses its reply.

Try the ChatNode integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ChatNode Make integration do for you?

The ChatNode Make integration lets a Make scenario (the automation you build, a chain of modules) talk to your ChatNode bot. A module is one brick of that chain. Here, one brick sends a message to your bot and hands its answer to the next brick, so the reply can land anywhere Make reaches.

Answers for questions that arrive by form or email. A prospect fills in a contact form in another app. Send a Message passes the question to your bot, and the next module stores or forwards the answer, so your team starts from a draft instead of a blank page.

One brain for every channel. Your bot already knows your offer. Put Send a Message behind any app Make can read, and the same knowledge serves inbound tickets, spreadsheet rows or a chat tool without training a second assistant.

The rest of the API, with the same account. Make an API Call reaches any endpoint of the ChatNode API through the connection you already created. It is the way to cover what the two listed modules leave out, provided you read the ChatNode API documentation first.

What the integration does not do: ChatNode has no trigger in Make, so nothing starts on its own from the ChatNode side. Your scenario begins with another app or with a schedule. Note also that the Make documentation for this app is flagged as AI generated, so check any important detail with ChatNode. If you are still choosing a platform, read our Make review and the n8n vs Make comparison; to learn scenarios step by step, the Make training is a good next stop.

Connect

How do you connect your ChatNode account to Make?

  1. 01

    Copy your API key from ChatNode

    Open your ChatNode dashboard, go to the Settings section and copy the API key displayed there. You need an active ChatNode account; without one, there is no key to paste into Make.

  2. 02

    Add a ChatNode module in Make

    In your scenario, add a ChatNode module such as Send a Message and click Create a connection. A connection is your ChatNode account linked to Make once, then reused by both ChatNode modules.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several bots. Paste the API key you copied, or follow the instructions Make shows on screen, then save.

First scenario

Your first scenario with ChatNode and Make

GoalWhen a new question lands in another app, Make sends it to your ChatNode bot and gets the answer back, ready for the next step.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since ChatNode has no trigger, pick the app where questions arrive, such as your form tool.

  2. 02

    Set up the starting app

    Connect that first app and fill its fields. Make lists what it can read once the connection exists, so you choose the form or folder rather than typing it by hand.

  3. 03

    Add Send a Message

    Click the + on the right of the first module, search ChatNode and pick Send a Message. Choose your connection, then map the question text coming from the previous module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bundle of Send a Message (a bundle is one item passed between modules) and read the answer your bot returned.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation, the unit Make bills on your plan.

Modules

What the ChatNode modules do

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

ChatNode1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

You get access to any ChatNode API endpoint from inside a scenario, signed with the connection you already set up, so no second login or key handling is needed.

When to use it
the job you have in mind is covered by the ChatNode API but not by Send a Message.
Watch out
you write the request yourself, so read the ChatNode API documentation before building it.
ChatNode2

Send a Message

Action

In Make“Sends a message to your bot and get back this answer.”

Your bot receives the text you map and sends back its answer, which the next module can store, forward or post wherever you need it.

When to use it
a question shows up outside your chat widget, in a form, an inbox or a sheet, and you want the bot to draft the reply.
Watch out
check the answer with Run once before letting the scenario send it to a customer.
Need help

Need help automating ChatNode with Make?

A person reads every message.

FAQ

ChatNode and Make: frequently asked questions

01Is the ChatNode Make integration free?
Yes, on the Make side. ChatNode is a standard app, available from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits each month. Your ChatNode subscription is separate: you need an active ChatNode account, and its pricing is set by ChatNode, not by Make.
02What do you need to connect ChatNode to Make?
Two things: an active ChatNode account and its API key. You find the key in the Settings section of your ChatNode dashboard. In Make, add a ChatNode module, click Create a connection, give it a name if you like and paste the key. The connection is then shared by both ChatNode modules, so you only do this once per account. If you manage several ChatNode accounts, create one connection for each and name them clearly so you pick the right one in every module.
03Can a ChatNode event start a Make scenario in real time?
No, not through a ChatNode module: the app has no trigger in Make, neither scheduled nor instant. Your scenario starts with another app instead, for example the tool where questions come in, and ChatNode joins as the second step. You can also start the scenario on a schedule set on its first module, every 15 minutes by default, or every minute on a paid plan. In both cases ChatNode acts when Make calls it, rather than warning Make itself.
04What if the ChatNode module you need is missing?
Use Make an API Call. It reaches any endpoint of the ChatNode API with the same connection, so you can cover what Send a Message does not. You write the request yourself, which means reading the ChatNode API documentation first. Also keep in mind that the Make documentation for ChatNode is marked as AI generated and may contain mistakes, so confirm important details with ChatNode directly. If the ChatNode API cannot do what you want, another app in the scenario may handle that part.
05Should you use Make or n8n for ChatNode?
It depends on the tool your team already runs. On Make, ChatNode comes with 2 modules: Send a Message for your bot and Make an API Call for the rest of the API, both from the Free plan. Many apps also have an n8n node, so check whether ChatNode has one before deciding. Then compare what matters to you: the modules available, how each tool starts a workflow and which platform your team already knows. Our comparison page covers the two tools side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations