Resources · Make integration

Chatsistant Make integrationAutomate Chatsistant with Make.

Want form answers collected by your Chatsistant bot to reach the rest of your tools on their own? The Chatsistant Make integration gives you 3 modules: 1 scheduled trigger and 2 actions. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Chatsistant integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Chatsistant Make integration do for you?

The Chatsistant Make integration links your Chatsistant account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger or an action. Chatsistant, filed under AI in the Make docs, brings one trigger that spots new submitted forms and two actions.

Pass leads to your sales tools. Watch New Submitted Forms picks up each form a visitor fills in through Chatsistant. Every form becomes a bundle, one item handed to the next module, so a CRM or a spreadsheet module can file it without copy and paste.

Reply from the same account. Send a Message lets the scenario push a message through Chatsistant, for example once another app has done its part. The docs give no description of this module, so read the fields Make shows once your connection exists.

Reach the rest of the API. Make an API Call reuses the same connection to call any endpoint of the Chatsistant API. It is the way out when the two named modules stop short.

Keep the limits in mind: the Make docs for this app are AI-generated from vendor material and may contain mistakes, so verify anything important with Chatsistant. If you are still choosing a platform, the n8n vs Make page sets out the criteria, and the Make training covers the editor from scratch. A stuck run? The Make troubleshooting guide lists the usual fixes.

Connect

How do you connect Chatsistant to Make?

  1. 01

    Generate an API key in Chatsistant

    In Chatsistant, open the Account menu, go to API Keys and click Generate new key. Add a description so you know later what the key is for, click Generate and copy the key shown on screen.

  2. 02

    Add a Chatsistant module in Make

    In your Make scenario, add any Chatsistant module and click Create a connection. A connection is your Chatsistant account linked to Make once, then reused by every Chatsistant module you add later.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like; the field is optional. Paste the API key you copied, or follow the on-screen instructions, then confirm to finish the link.

First scenario

Build your first scenario with Chatsistant

GoalWhen a visitor submits a form in Chatsistant, Make sends a message through Chatsistant with Send a Message.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + to place your first module.

  2. 02

    Place the trigger

    Search for Chatsistant, pick Watch New Submitted Forms and click Create a connection with your API key. Make then lists what it can read from your account, so fill the fields from there.

  3. 03

    Add the action

    Click the + to the right of the trigger and choose Send a Message. Map data from the form bundle into the fields Make shows, so each message reuses what the form collected.

  4. 04

    Test with Run once

    Submit a test form, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the data before going live.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. On the Free plan, 15 minutes is also the shortest gap between two scheduled runs.

Triggers

What starts a Chatsistant scenario?

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

Chatsistant1Watch New Submitted Forms

Watch New Submitted Forms

triggerIn the docs only

This trigger opens your scenario whenever Chatsistant has new forms submitted, so answers gathered by your bot turn into bundles that the next modules can use. Each form counts as its own item, and every module that handles it uses an operation, which is what Make counts on your plan.

How it fires
scheduled, Make checks Chatsistant on the scenario's schedule instead of being told the moment a form arrives.
When to use it
a lead form collected in the chat that sales wants to see in their own tools.
Watch out
on the Free plan, the gap between two checks is at least 15 minutes.
Modules

What can Chatsistant do in a Make scenario?

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

Chatsistant1

Make an API Call

ActionIn the docs only

Here you get access to any endpoint of the Chatsistant API, through the connection you already set up, so there is no second login to manage. It covers whatever the two other modules leave out.

When to use it
the task you need has no named module, and the Chatsistant API documentation shows an endpoint for it.
Watch out
you build the request yourself, so keep the vendor API docs open next to the editor.
Chatsistant2

Send a Message

ActionIn the docs only

With this action, your scenario sends a message through Chatsistant, using data mapped from earlier modules. The docs give no description, so the fields Make displays once connected are your best guide to what it expects.

When to use it
right after a form lands or another app reports an event you want to answer.
Watch out
click Run once on a test form and read what was sent before switching the scenario on.
Need help

Need help automating Chatsistant with Make?

A person reads every message.

FAQ

Chatsistant and Make: common questions

01Is the Chatsistant Make integration free?
Yes, on the Make side. Chatsistant is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a scheduled run at most every 15 minutes, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. You still need an active Chatsistant account, billed by Chatsistant under its own pricing.
02What do you need to connect Chatsistant to Make?
An active Chatsistant account and an API key. In Chatsistant, open the Account menu, go to API Keys, click Generate new key, add a description, click Generate and copy the key. In Make, add a Chatsistant module, click Create a connection, optionally name it, and paste the key. That single connection then serves all three Chatsistant modules in every scenario you build. Once it is saved, test the link with Run once before you switch on your first scenario.
03Does the Chatsistant trigger react as soon as a form is submitted?
No. Watch New Submitted Forms is a scheduled trigger: Make checks Chatsistant on the scenario's schedule, every 15 minutes by default, rather than being pushed each form by a webhook. On a paid plan the interval can go down to 1 minute. For most lead follow-up, that delay is fine; if you need a shorter gap, a paid plan is the lever Make gives you. Before relying on it, submit a test form and click Run once to see the bundle Make picks up.
04What if the Chatsistant module you need is missing in Make?
It depends on the task, but Make an API Call is the usual answer. It calls any endpoint of the Chatsistant API with the connection you already have, so you can reach features the trigger and Send a Message do not cover. Keep in mind that the Make docs for this app are AI-generated and may contain mistakes, so check important details with Chatsistant directly. Keep the vendor API documentation open while you build the request yourself, and test it with Run once.
05Should you use Make or n8n for Chatsistant?
It depends on your criteria, not on a winner. On Make, Chatsistant comes with 3 ready modules, a scheduled form trigger, a message action and an API call, all usable from the Free plan. The same app often has an n8n node too. Compare which tool your team already runs, how each counts usage and which modules match your flow, then decide. Whichever you pick, test your flow with a sample form before going live.
Same platform

Other docs you might need on this stack.

Browse all integrations