Cliengo Zapier integrationAutomate Cliengo with Zapier.
The Cliengo Zapier integration gives you 2 triggers, 2 actions and 2 searches. Every customer your Cliengo chatbot captures can start a Zap, and Zapier can create, update or look up customers and agents in Cliengo without anyone retyping a lead.
Verified Trustpilot reviews · AI, automation & growth agency
What the Cliengo Zapier integration does with your leads
It connects Cliengo, the website chatbot that turns visitors into leads, to Zapier so those leads move without copy and paste. Cliengo can start an automation when a customer is created or changed, and it can receive new customers, updates and lookups from it.
Three results worth building. Chatbot leads passed on: Nuevo Cliente - New Customer starts the Zap once per new customer, and a filter on the email keeps only the leads you can actually write to before they reach your email tool. Customers created from other sources: Crear Cliente / Create Customer adds a contact to Cliengo with a name, an email and a website, so every lead lives in one place. The right record before you write: Buscar Contacto / Search Customer finds the existing contact, and Buscar Agente / Search Agent finds a team member, so later steps work on the right person.
What Zapier does not do here: both triggers are polling triggers, so nothing is instant and the delay depends on your plan. There is no trigger for a deleted customer or for a conversation, only for customers. The operation names mix Spanish and English, exactly as Cliengo published them, which is what you will see in the editor. And the New/Updated trigger also fires on every edit, so it is a poor base for anything that creates records.
Comparing platforms? The Cliengo Make integration covers the same app on Make. There is no n8n page for Cliengo on this site.
Zapier vocabulary, one line each
Eight words, and the editor stops being a guessing game.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, like a new Cliengo customer. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something, like updating a customer in Cliengo.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer, keeping only items it has not seen before. Both Cliengo triggers work this way.
- Instant trigger
- A trigger the app reports itself the moment the event happens, with no wait for the next check. Cliengo has none.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can use what it found.
What a Cliengo Zap really costs
Zapier bills tasks, not Zaps. The trigger never costs a task, however often Zapier checks Cliengo for new customers.
- Free plan100 tasks a month, unlimited Zaps
- Zap size on FreeTwo steps: one trigger, one action
- Premium appNo, Cliengo works on the free plan
- Filter or searchMakes the Zap multi-step, paid plan
Each action that succeeds is one task; one that fails is not counted. A Zap with two actions uses two tasks per run. A few apps and actions take more than one task, so the count follows completed actions, never Zaps. The free plan stops at two steps, one trigger and one action. A filter or a search step makes the Zap multi-step, which needs a paid plan. Both Cliengo triggers are polling ones: on Free, Zapier looks every 15 minutes.
Connect Cliengo to Zapier in 3 steps
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. A connection is your Cliengo account linked once, then reused by every Zap that talks to Cliengo.
- 02
Find Cliengo
Search for Cliengo in the dialog, select it and click Add connection. You need an existing Cliengo account, plus access to any contacts you do not own and want the Zap to touch.
- 03
Sign in and grant access
Sign in to Cliengo in the tab that opens and grant Zapier access to the account. From there, every Cliengo step in every Zap reuses this connection without asking again.
Your first Zap: pass chatbot leads with an email to your mailing tool
GoalEach new Cliengo customer who left an email address is added to your email tool; leads without one stop at the filter.
- 01
Build: set the trigger
Start a new Zap, pick Cliengo and the Nuevo Cliente - New Customer trigger. Leave its Email with phone if empty option unset, so a lead with no email arrives with that field empty. Each customer comes through once.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent customers of the account, so you map fields on a real lead and see which ones arrive without an email.
- 03
Add the filter
From the plus icon, add a Filter: the email field and the rule that it exists. Phone-only leads stop here instead of failing in the next step. The filter makes this a multi-step Zap on a paid plan.
- 04
Add your email tool
Pick your email tool and its action for adding a subscriber. Map the email and the first name the trigger test brought back. Cliengo only reads here: nothing is written back, so nothing can set the trigger off again.
- 05
Test, then Publish
Test the action and check the subscriber in your email tool. Then click Publish. Leads captured before that moment are not processed.
Cliengo triggers on Zapier
2 events start a Zap when something happens in Cliengo. Zapier checks for them at the interval your plan allows.
Nuevo Cliente - New Customer
Polling triggerIn Zapier“Se activa cuando un cliente es creado - Triggers when a new customer is created.”
Starts your Zap when the chatbot, or anyone on your team, creates a new customer in Cliengo. Each customer comes through once, so it is the safe base for anything that adds a record elsewhere or sends a first message.
Cliente Nuevo/Actualizado - New/Updated Customer
Polling triggerIn Zapier“Se activa cuando un cliente es creado y actualizado - Triggers when a new customer is created y updated.”
Fires when a customer is created and again each time one is updated. That makes it the trigger for keeping another tool in step with Cliengo, not for counting new leads.
Cliengo actions on Zapier
Cliengo gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Crear Cliente / Create Customer
ActionIn Zapier“Crear un nuevo contacto / Creates a new customer.”
Adds a new contact to Cliengo from data the Zap already carries, so leads captured outside the chatbot end up in the same list. You fill in at least a first name, an email and a website.
Actualizar Cliente / Update Customer
ActionIn Zapier“Actualizar un contacto existente / Update an existing customer”
Changes an existing Cliengo contact, identified by its Cliengo contact ID, with the values you map in the step.
Cliengo searches on Zapier
2 search steps look for data that already exists in Cliengo, so a later step can use it.
Searches sit at the bottom of the action event list, under their own heading. They hand what they find to the next steps, and each one makes the Zap multi-step. Three settings decide what happens when a search does not find exactly one result.
Buscar Contacto / Search Customer
SearchIn Zapier“Busca un contacto / Search a customer”
Looks up a contact that already exists in Cliengo and hands what it found to the following steps, so they work on the right record.
Buscar Agente / Search Agent
SearchIn Zapier“Busca un agente / Search a agent”
Finds an agent of your Cliengo account and passes what it found on to the next steps, so they can use that person's details.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps after it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. Cliengo offers no such variant on Zapier, so neither search here can create the missing contact or agent.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Cliengo Zap breaks
Zapier ties no help article to Cliengo, so the traps below are the general ones of any Zap, applied to this app.
Test each step before publishing and read what comes back. If a step keeps failing, the Zapier troubleshooting guide helps you find why, and the Zapier training covers the editor from the start.
Old leads never come through
A Zap only reacts to what happens after you publish it. Customers captured earlier stay in Cliengo; moving that backlog is a separate job.An update that updates itself
New/Updated Customer plus Update Customer on the same contact: each update starts the Zap again and burns through your tasks fast.A bulk import held back
If hundreds of contacts land at once after an import or a migration, Zapier's flood protection can hold that sudden batch back.Phone numbers posing as emails
With the Email with phone if empty option set, a lead with no email arrives with an address built from the phone number. Mapped into an email step, it goes nowhere useful.
Need help automating Cliengo with Zapier?
A person reads every message.
