Resources · Make integration

Connverz Make integrationAutomate Connverz with Make.

Can Make react to what lands in Connverz and answer with a template? The Connverz Make integration gives you 4 modules: 1 scheduled trigger and 3 actions. This guide shows how to link your account, then walks you through a first scenario you can test before switching it on.

Try the Connverz integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Connverz Make integration let you automate?

The Connverz Make integration links your Connverz account to Make, a visual tool where you build a scenario: a chain of modules that runs on its own. Each module is one brick of that chain. Connverz brings four of them, so incoming data can start a scenario and Make can reply through Connverz without anyone copying things by hand.

Reply without watching the inbox. Watch the Received Data picks up what reached Connverz since the last check, and Send a Template answers from a message you prepared in advance. The team stops retyping the same reply.

Start a Connverz flow from another app. A form, a CRM or a spreadsheet can open the scenario, then Trigger a Flow hands the rest to a flow you already built inside Connverz. The logic stays where your team maintains it.

Reach what the list does not cover. Make an API Call talks to any endpoint of the Connverz API with the same connection, so a missing module is rarely a dead end. The API documentation has to be requested from the Convrs team first.

Know the limits before you start. The official Make page for Connverz is AI-generated from the vendor documentation and carries a warning that it may contain errors, so check important details with Connverz. If you are still choosing a tool, read our Make review and the n8n vs Make comparison. When a run fails, Make troubleshooting lists the usual fixes.

Connect

How do you connect Connverz to Make?

  1. 01

    Get your API token

    Log in to the Convrs dashboard, open Integrations, click Convrs API, then Enable API. Copy the token it generates. It belongs to your organization only, so keep it out of shared documents.

  2. 02

    Add a Connverz module

    In a Make scenario, add any Connverz module and click Create a connection. A connection is your Connverz account linked to Make once and reused by every Connverz module afterwards. The Connection name field is optional.

  3. 03

    Paste the token and save

    Paste the value into the token field, or follow the on-screen instructions, and save. The connection is then ready for the three other modules of the app.

First scenario

Your first scenario with Connverz

GoalWhen new data reaches Connverz, Make sends a prepared template in return.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. That empty circle is where your first module, the trigger, will go.

  2. 02

    Add the trigger

    Search for Connverz, pick Watch the Received Data and choose your connection. This module decides when the whole scenario starts working.

  3. 03

    Add the reply

    Click the + on the right of the trigger and add Send a Template. Map the data from the first module into its fields so each reply fits the item that came in.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. A bundle is one item passing from one module to the next.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. Save, then switch the scenario on.

Triggers

What can start a Connverz scenario?

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

Connverz1Watch the Received Data

Watch the Received Data

triggerIn the docs only

This trigger gives your scenario a starting point inside Connverz: judging by its name, it collects the data received since the previous check and passes each item on as a bundle to the next module. The Make documentation does not describe which kind of data it returns, so run a test and look at the output before mapping anything.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and never in real time.
When to use it
any time something arriving in Connverz should lead to a follow-up, such as a reply or a record in another tool.
Watch out
Make counts an operation for each module run on each bundle, so a busy inbox multiplies the credits the next modules consume.
Modules

What can Make do in Connverz?

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

Connverz1

Make an API Call

ActionIn the docs only

This module covers everything the three named modules leave out: it calls any endpoint of the Connverz API while reusing the connection you already created, so no second login is needed.

When to use it
the action you need is in the Connverz API documentation but not in the module list.
Watch out
you write the request yourself, and the endpoint list comes from the documentation you request from the Convrs team.
Connverz2

Send a Template

ActionIn the docs only

Pick this module when the answer is always built on the same base: judging by its name, it sends a template from Connverz, filled with values mapped from earlier modules. The Make documentation gives no description, so the exact fields appear only once your connection is set.

When to use it
a new lead, order or request should get a consistent answer without anyone typing it.
Watch out
test with Run once on your own contact before letting it reach real people.
Connverz3

Trigger a Flow

ActionIn the docs only

Your existing Connverz flows become reachable from any app: going by its name, this action starts one of them from a Make scenario, so the logic you built inside Connverz keeps running there instead of being rebuilt module by module.

When to use it
another tool, such as a form or a CRM, holds the event and Connverz already has the flow that should follow.
Watch out
the Make documentation says nothing about the inputs a flow expects, so check them in Connverz first.
Need help

Need help automating Connverz with Make?

A person reads every message.

FAQ

Connverz and Make: frequent questions

01Is the Connverz Make integration free?
Yes, Connverz is a standard app in Make, so it works from the Free plan. That plan has its own limits: 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 lower the interval to 1 minute, remove the cap on active scenarios and count usage in monthly credits. Your Connverz subscription is a separate matter that this page does not cover.
02What do you need to connect Connverz to Make?
You need an active Connverz account and the API token of your organization. The token comes from the Convrs dashboard: open Integrations, click Convrs API, then Enable API, and copy the generated value. The Make documentation also asks you to request the API documentation from the Convrs team. In Make, add any Connverz module, click Create a connection, paste the token and save. Every Connverz module in your scenarios then reuses that single connection.
03Does the Connverz trigger in Make react in real time?
No. Watch the Received Data is a scheduled trigger, marked with a clock badge in the editor. Make checks Connverz at the interval set on the first module of the scenario, every 15 minutes by default and never less than 15 minutes on the Free plan. On a paid plan the interval can go down to 1 minute. Pick the interval that matches how quickly your team actually needs to follow up, and keep in mind that the next modules run once for each bundle the trigger returns.
04What if a Connverz module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Connverz API with the connection you already have, so the four listed modules are not a hard ceiling. You write the request yourself, based on the API documentation you request from the Convrs team. Keep in mind that the official Make page for Connverz is AI-generated from vendor documentation and may contain errors, so confirm important details directly with Connverz before building on them.
05Should you use Make or n8n for Connverz?
It depends on what each tool offers for this app. On the Make side, the facts are clear: 1 scheduled trigger, 3 actions including Make an API Call, and access from the Free plan. The Make documentation says nothing about a Connverz node in n8n, so check the n8n integration list before comparing. If both exist, compare the modules you actually need and the tool your team already knows, rather than a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations