Resources · Make integration

Chatwize Connection Make integrationAutomate Chatwize Connection with Make.

Can a new form submission in Chatwize set off the rest of your workflow on its own? The Chatwize Connection Make integration offers 3 modules: 1 trigger and 2 actions. This page walks you through the connection, then a first scenario you can test and switch on.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Chatwize Connection Make integration do?

The Chatwize Connection Make integration links your Chatwize account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule or when an app calls Make. A module is one brick of that chain. Chatwize brings three of them: one that watches form submissions and two actions.

Follow up on every form. Start with Watch a New Form Submission, then add Send a Message so each new submission leads to a message without anyone copying details by hand. The data that travels between modules is called a bundle: here, one submission.

Feed your other tools. The same trigger can hand each submission to a module from another app, such as a CRM or a spreadsheet, so the lead lands where your sales team already works.

Reach what the list does not cover. Make an API Call reaches any endpoint of the Chatwize API with the connection you already set up. Turn to it when neither listed action matches your need.

Keep the limits in mind. The official documentation gives no description for these modules and warns that its content is AI-generated and may contain mistakes, so check each field in the editor before relying on it. Before you build, the Make review helps you judge the tool, and Make pricing explains how operations are counted. Chatwize may also exist as an n8n node; n8n vs Make lays out the differences.

Connect

How do you connect Chatwize Connection to Make?

  1. 01

    Generate your Chatwize API key

    In Chatwize, open the Account section, go to API Keys and click Generate new key. Add a short description, click Generate, then copy the key shown in the dialog. Make will ask for it in the next step.

  2. 02

    Add a Chatwize module to a scenario

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

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you like, it is optional. Paste the API key you copied, or follow the instructions on screen, and confirm. The module can now read your Chatwize data.

First scenario

Your first scenario with Chatwize Connection

GoalWhen a new form submission arrives in Chatwize, Make sends a message with Send a Message.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place the first module. That first module decides when everything else runs.

  2. 02

    Pick the trigger

    Search for Chatwize Connection, choose Watch a New Form Submission and select your connection, or click Create a connection if this is your first Chatwize module.

  3. 03

    Add the message

    Click the + on the right of the trigger and add Send a Message. Fill its fields and map values from the submission, so each message carries the details of the form it answers.

  4. 04

    Test with Run once

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

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From then on, each run counts operations on your Make plan.

Triggers

What starts a Chatwize Connection scenario

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

Chatwize Connection1Watch a New Form Submission

Watch a New Form Submission

triggerIn the docs only

You get each new form submission from Chatwize as a separate bundle, ready to pass to the next module. It is the only Chatwize module that can open a scenario, so every automated follow-up on a form starts here.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default and no more often than every 15 minutes on the Free plan.
When to use it
when a visitor fills in a form and someone on your team should be told, or the answers should reach another tool.
Watch out
the documentation gives no description of this module, so run it once with a test submission and read the bundle to see which fields actually come through.
Modules

What the Chatwize Connection modules do

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

Chatwize Connection1

Make an API Call

ActionIn the docs only

This module gives you access to any endpoint of the Chatwize API, using the connection you already created, so you are not limited to the two listed modules.

When to use it
when neither Watch a New Form Submission nor Send a Message covers the request you need to make.
Watch out
you write the request yourself, so keep the Chatwize documentation open while you fill it in.
Chatwize Connection2

Send a Message

ActionIn the docs only

This action lets your scenario send a message through Chatwize instead of someone typing it, with content you map from earlier modules.

When to use it
right after Watch a New Form Submission, when a new form should lead to a written reply or a notice.
Watch out
the documentation does not describe where the message goes, so check the fields Make lists and test with Run once before activating.
Need help

Need help automating Chatwize Connection with Make?

A person reads every message.

FAQ

Questions about the Chatwize Connection Make integration

01Is the Chatwize Connection Make integration free?
Yes, on the Make side. Chatwize Connection is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and allow runs of up to 40 minutes. Your Chatwize subscription is a separate matter: the documentation points to the Chatwize pricing page for it.
02What do you need to connect Chatwize Connection to Make?
You need an active Chatwize account and, according to the documentation, an OpenAI API key. In Chatwize, generate an API key from the API Keys section of your account settings and copy it. In Make, add a Chatwize Connection module, click Create a connection, optionally name it, then paste the key. The connection is then reused by every Chatwize module in your scenarios, so you only set it up once per account.
03Does the Chatwize Connection trigger react in real time?
No. Watch a New Form Submission is a scheduled trigger: Make checks Chatwize on the scenario's schedule rather than being alerted the moment a form arrives. New scenarios check every 15 minutes by default. The Free plan cannot go below 15 minutes, while paid plans can go down to 1 minute. A submission therefore reaches your scenario at the next check, not instantly, which is worth knowing before promising an immediate reply.
04What if a Chatwize Connection module is missing in Make?
Use Make an API Call. With the connection you already have, it can call any endpoint of the Chatwize API, which covers what the two listed actions do not. Keep in mind that the official documentation gives no description of the modules and notes that its content is AI-generated and may contain mistakes. For anything important, check the Chatwize documentation or ask Chatwize directly before building a scenario on it.
05Should you use Make or n8n for Chatwize Connection?
It depends on the tool your team already uses. In Make, Chatwize Connection offers 3 modules: one scheduled trigger for form submissions, Send a Message, and Make an API Call for the rest of the API. The same app often has an n8n node as well, so check the list of operations there against what you need. Compare the modules each tool offers for your case rather than picking on reputation.