Resources · Make integration

Cliengo Make integrationAutomate Cliengo with Make.

Your Cliengo contacts can move on their own between your tools. The Cliengo Make integration gives you 8 modules: 2 triggers that watch contacts and 6 modules that create, read, list, update or delete them. This page shows how to link your account and build a first scenario.

Try the Cliengo integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cliengo Make integration do for your contacts?

The Cliengo Make integration links your Cliengo account to Make so contacts can be picked up, created and kept up to date without copying anything by hand. You build a scenario, the automation itself, out of modules, the bricks that each do one job on one app.

Every new lead lands in the rest of your stack. Watch New Contacts spots the contacts Cliengo collected and passes each one, as a bundle (one item moving from module to module), to the next app in the flow: a sales spreadsheet, a team chat, a mailing tool.

Contacts from elsewhere show up in Cliengo. A web form or an event sign-up in another app can feed Create a Contact, so the sales team finds the person in Cliengo along with the other leads. Before creating, List Contacts helps you check whether that person is already there.

Changes stay in sync. Watch Updated Contacts reacts when a contact is edited in Cliengo, and Update a Contact pushes a correction made in another tool back into Cliengo.

Know the limits before you start. Make states that its documentation for Cliengo is limited, because little public information exists about the app, so the modules come without field descriptions. Make an API Call covers what the listed modules do not. To weigh the platform itself, read the Make review; if you also consider n8n, where the same app often has a node, the n8n vs Make comparison lays out both tools. When a run fails, Make troubleshooting lists the usual fixes.

Connect

How do you connect Cliengo to Make?

  1. 01

    Add a Cliengo module

    In a scenario, click the + and search for Cliengo, then pick any of its modules. The first time, Make asks for a connection: your Cliengo account linked to Make once and reused by every Cliengo module. Click Create a connection.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it pays off the day you manage several Cliengo accounts, for instance one per brand or per client. Pick a name that tells you at a glance which account sits behind it.

  3. 03

    Authorize and save

    Make's documentation gives no Cliengo specific steps, so follow the generic path: authorize Make on the Cliengo page that opens, or paste the key Cliengo gives you, then click Save. The connection now appears in every Cliengo module.

First scenario

Your first scenario: send form leads to Cliengo

GoalWhen a lead fills in a form in another app, Make creates that person as a contact in Cliengo.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. That first module is the one that starts the flow.

  2. 02

    Pick the starting app

    Search for the app where your leads arrive, such as your form tool, and choose its module for new entries. Link that account with Create a connection and fill in the fields Make lists.

  3. 03

    Add Create a Contact

    Click the + on the right of the first module, search for Cliengo and pick Create a Contact. Connect your Cliengo account if it is not done yet.

  4. 04

    Map the lead data

    Fill the Create a Contact fields by clicking into each one and choosing the matching value from the first module, so each piece of the lead lands in the right Cliengo field. Make shows what it can read once the connection exists.

  5. 05

    Test with Run once

    Send one test entry through your form, then click Run once. Open the bubble above each module to read the bundle it received, and check in Cliengo that the contact appeared.

  6. 06

    Schedule and switch on

    Set the schedule on the first module with the clock, every 15 minutes by default, then switch the scenario on. Each run uses operations, one per module per bundle, counted on your Make plan.

Triggers

Which Cliengo triggers can start a scenario?

2 modules start a scenario when something happens in Cliengo. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Cliengo as soon as it happens.

Cliengo1Watch New Contacts

Watch New Contacts

triggerIn the docs only

Each contact that appears in Cliengo can start a scenario, so a fresh lead reaches your other tools without anyone exporting a list. Every new contact travels on as its own bundle.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default, and at most once every 15 minutes on the Free plan.
When to use it
when sales wants every new lead copied into a shared spreadsheet or announced in a team channel.
Watch out
Make's documentation lists this trigger without a description, so look for the clock badge on the module and run it once to see what a contact bundle contains.
Cliengo2Watch Updated Contacts

Watch Updated Contacts

triggerIn the docs only

Edits made to a contact inside Cliengo can flow out to your other apps, which keeps a second list in step with the source instead of drifting apart. This trigger picks up changed contacts, not brand new ones.

How it fires
scheduled: Make checks the app on the scenario's schedule, the clock on the first module, which a paid plan can bring down to 1 minute.
When to use it
when an agent qualifies a lead in Cliengo and your CRM or mailing list must reflect that new status.
Watch out
do not pair it with Update a Contact on the same Cliengo account, or each update you write can be picked up again as a change.
Modules

What can Make do in Cliengo?

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

Cliengo1

Create a Contact

ActionIn the docs only

Adds a person to Cliengo from data that lives elsewhere, so a lead captured by another channel sits in Cliengo with the contacts your team already follows.

When to use it
after a sign-up form, a webinar registration or a new row in a lead sheet.
Watch out
it adds a new contact every time, so run List Contacts first when the same person may already exist.
Cliengo2

Delete a Contact

ActionIn the docs only

Removes a contact from Cliengo when another system says it should go, which keeps your base clean without manual clicks.

When to use it
when a person unsubscribes or asks for their data to be erased in another tool.
Watch out
a deletion cannot be undone from Make; test it with Run once on a dummy contact before switching the scenario on.
Cliengo3

Get a Contact

ActionIn the docs only

Fetches one specific contact so the following modules can use its details, which is handy when the scenario only knows who, not what.

When to use it
when a trigger hands you a contact identifier and you need the full record to write an email or fill a sheet.
Watch out
it needs to know which contact to read, so map the identifier from an earlier module instead of typing it.
Cliengo4

List Contacts

SearchIn the docs only

Returns the contacts Make finds in Cliengo, from none to many, each one as a separate bundle the next modules process in turn.

When to use it
to check whether a person already exists before creating them, or to copy your contact base into another tool.
Watch out
every returned contact costs operations in the modules that follow, so a large base can use a big share of your plan.
Cliengo5

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Cliengo API from your scenario, with the same connection as the other modules, for the jobs the named modules do not cover.

When to use it
when you need something from Cliengo that none of the contact modules offers.
Watch out
you write the request yourself, and Make's limited Cliengo documentation will not describe the endpoints for you.
Cliengo6

Update a Contact

ActionIn the docs only

Changes the details of an existing Cliengo contact, so a correction made elsewhere reaches the record your agents see.

When to use it
when a customer fixes their phone number in your shop or your CRM marks a deal as won.
Watch out
map the right contact identifier from an earlier module, often Get a Contact or List Contacts, or the change lands on the wrong person.
Need help

Need help automating Cliengo with Make?

A person reads every message.

FAQ

Questions about Cliengo and Make

01Is the Cliengo Make integration free?
Yes, you can start on the Make Free plan. Cliengo is a standard app, and standard apps are available on every Make plan, including Free. The Free plan has limits though: 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 (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month.
02What do you need to connect Cliengo to Make?
A Cliengo account and a Make account are enough to begin. Make's documentation lists no prerequisite for Cliengo and no dedicated connection steps, so the generic flow applies: add a Cliengo module, click Create a connection, optionally name it, authorize Make on the Cliengo page or paste the key Cliengo provides, then click Save. That single connection is then reused by all 8 Cliengo modules, so you only go through it once per account.
03Do the Cliengo triggers fire instantly?
No. Watch New Contacts and Watch Updated Contacts are scheduled triggers, a type inferred from their names since Make's documentation describes neither: Make checks Cliengo on the scenario's schedule instead of being called by the app the moment something changes. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can bring it down to 1 minute. If you need a contact to be processed sooner, you can open the scenario and click Run once, which checks Cliengo right away.
04What if a Cliengo module is missing or too limited?
Use Make an API Call. Cliengo has this module, and it lets a scenario call any endpoint of the Cliengo API with the same connection as the other modules. Keep in mind that Make itself says its Cliengo documentation is limited because little public information exists about the app, so the 8 modules come without detailed descriptions. Test each module with Run once to see exactly what it returns before building a longer scenario on top of it.
05Should you use Make or n8n for Cliengo?
It depends on the tool your team already runs. This page covers only the Make side: 8 Cliengo modules, 2 of them scheduled triggers, a Make an API Call module for the rest, and access from the Free plan since Cliengo is a standard app. The same app often has an n8n node as well, so check the n8n catalog before deciding. Compare what each side offers for your contacts rather than relying on a general ranking of the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations