Cliengo

Automate the Cliengo chatbot and CRM platform, managing contacts and conversations and replying across web and WhatsApp. Agents send approved WhatsApp templates and keep lead records current as conversations progress.

1 trigger 26 actions API key available

Platform Documentation ↗ Capability data verified 2026-08-02

On Cliengo Event fires for a new website or WhatsApp conversation

Agent reads the exchange with List Conversation Messages and the record with Get Contact

Agent searches List Contacts on the captured email and phone for an existing record

Agent enriches the record with Update Contact and advances it with Move Conversation To Phase

Rep receives the transcript, the UTM attribution, and any duplicate candidates found

Rep decides which contact record survives before anything is deleted or merged

What This Integration Enables

Most chatbot platforms treat the conversation as the object and the person as an afterthought. Cliengo inverts that. It ships a CRM underneath the chat, so the contact is a first-class record with a lifecycle status, an assigned agent, a rating, tags, and the UTM attribution captured the moment they first engaged. Conversations hang off that contact across every connected channel, and they move through pipeline phases the way deals do. For a sales team, this is the difference between a chat log and a lead.

FlowRunner agents work both layers. On contacts they search with filters for status, channel, agent, tags, rating, and date ranges, read a full profile, create records on a specific channel, apply partial updates that leave the rest of the record alone, read the activity timeline, and read the internal notes reps have left. On conversations they search across channels, read one back with its state and participants, and list every conversation belonging to a contact. They read the ordered message history with attachments, post messages as an agent or as the bot or as an internal note, close and reopen threads, and move them between pipeline phases. They resolve the account's tags, phases, channels, and users, and on the WhatsApp side they list connected channels and approved templates and send a template to one or more recipients with positional variables, getting successes and failures reported separately. The On Cliengo Event trigger covers conversation lifecycle changes, new messages, notes, phase moves, tag changes, and contact create, update, status, assignment, and delete events, and FlowRunner registers the subscription when the flow is enabled and removes it when the flow is disabled.

Without FlowRunner

Chat leads retyped into the CRM A rep reads the conversation, then keys the name and phone into a second system

Attribution lost at the handoff The UTM data Cliengo captured on first contact never reaches the deal record

Duplicates created channel by channel The same person becomes a website contact and a WhatsApp contact with no link between them

With FlowRunner

The conversation and the record move together The event that starts the conversation also enriches the contact and advances its phase

Attribution travels with the lead UTM data read from the contact lands on the CRM record alongside the transcript

Duplicate resolution is a human decision The agent assembles the evidence and a person chooses which record survives

Use Case Scenarios

Website Chat Lead Into the CRM With Its Attribution Intact

A visitor asks about pricing on the website widget and On Cliengo Event fires. The agent reads the transcript with List Conversation Messages, pulls the contact with Get Contact, and takes the UTM attribution Cliengo recorded at first engagement. It creates or updates the matching record in Pipedrive with the campaign source attached to the deal, not just the contact, then moves the Cliengo conversation forward with Move Conversation To Phase. The rep opening the deal sees which campaign produced it and what the visitor actually said, in the same place.

Drafted Reply, Sent as the Agent

A conversation comes in overnight on WhatsApp. The agent reads the thread with List Conversation Messages, reads the internal handover notes with List Conversation Notes so it does not contradict what a colleague already told this customer, and drafts a reply. Rather than posting it silently, it writes the draft into the thread as an Internal Note type message for the morning rep, who edits and sends it as a Text message from their own account. The customer's next reply lands in the same conversation, and the whole exchange stays on one record.

Reopening a Premature Closure

A nightly check lists conversations closed in the last day and reads each one's final messages. Where the customer's last message was a question rather than a confirmation, the agent runs Open Conversation to return the thread to the active queue and posts an internal note explaining why. Closing is reversible in Cliengo, which is precisely why this correction is safe to automate while the decision in the next section is not.

Human-in-Loop Highlight

Cliengo's contact is the join point for everything: the conversations across every channel, the activity timeline, the notes, and the attribution captured when the person first engaged. Delete Contact removes the contact and its association with past conversations, permanently, with no restore through the API. So the moment a dedup sweep finds the same buyer as a website contact and a WhatsApp contact, the agent stops. It does the work a person should not have to do, running List Contacts on both the email and the phone, pulling Get Contact History and List Contact Notes on each candidate, and listing every conversation attached to each with List Contact Conversations. Then it hands over rather than deciding, which is the digital andon cord applied to a CRM: "Two contacts look like the same person. Record A: web widget, has the paid-search UTM, 3 conversations, rated by Ana. Record B: WhatsApp, no attribution, 1 conversation, currently assigned. Which record survives, and should the other be deleted or just left unassigned?" A rep answers, and the agent executes the choice. Every routine enrichment before this point runs untouched, because Update Contact only writes the fields it is given. The one step that destroys history gets a person, which is what human-in-the-loop orchestration is for.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

26 actions

Contacts

List Contacts Searches the contact database with filters for status, channel, assigned agent, tags, rating, and creation or update date ranges. Results are paginated with a block reporting the total number of matches.
Get Contact Retrieves a single contact by ID with its full profile, including channel of origin, lifecycle status, assigned agent, rating, and the UTM attribution captured when they first engaged.
Create Contact Creates a contact on a specific channel. Only the channel and name are mandatory, with an optional initial message, owner, or arbitrary custom fields to seed the record with everything a rep needs on first view.
Update Contact Applies a partial update to an existing contact. Only the supplied fields change, which makes it safe to call from an enrichment flow that knows one new detail without overwriting the rest.
Delete Contact Permanently deletes a contact from the account. The contact and its association with past conversations are removed and cannot be restored through the API.
Get Contact History Returns the activity timeline recorded against a contact, covering status changes, assignments, and other lifecycle events. Used to audit how a lead progressed, or to give an AI step the background before it drafts anything.
List Contact Notes Returns the internal notes agents have attached to a contact. Notes are private to the team and never shown to the visitor, so they are a safe place to read prior context from.

Conversations

List Conversations Searches conversations across every channel with filters for status, tags, phase, agent, channel, date range, and UTM attribution. Cliengo keys conversations by ID and this action normalizes them into a plain array for iteration.
Get Conversation Retrieves a single conversation by ID with its channel, state, participants, assigned agent, and most recent message. State is reported in upper case.
List Contact Conversations Returns every conversation belonging to a specific contact across all channels. Used to assemble a complete interaction history before escalating a case or summarizing a relationship.
List Conversation Messages Returns the message history in order with sender, text, timestamp, and any attachments. An option also returns the internal bot command entries normally hidden from the transcript.
Send Conversation Message Posts a message into an existing conversation as an agent, the bot, or the visitor. Plain text, an image by media URL, or an agent-only remark recorded as an internal note.
Close Conversation Marks a conversation as closed and removes it from the team's active queue. Reversible with Open Conversation, which is what makes it safe to automate once a request is resolved.
Open Conversation Reopens a closed conversation and returns it to the active queue. Used when a customer replies after a case was resolved, or when a check finds that a closure was premature.
Move Conversation To Phase Moves a conversation into a different pipeline phase, which is how Cliengo models sales and support stages. Combined with the phase list, this drives a qualification funnel.
List Conversation Notes Returns the internal notes attached to a conversation, visible only to the team. This is where handover context left by a previous agent is read from.

Account Metadata

List Tags Returns every tag defined in the account. Tag IDs are required by the conversation filters, so this resolves a readable name into the ID the filters expect.
List Phases Returns the pipeline phases configured in the account. Phase IDs are needed by the phase move and the conversation phase filter.
List Channels Returns the messaging channels connected to the account, such as website widgets, WhatsApp numbers, and social inboxes. A channel ID doubles as the website identifier used when creating contacts.
List Users Returns the agents and administrators in the account. Their IDs assign contacts and conversations and identify the sender when posting an agent message.
Get Current User Returns the user the configured token authenticates as. Used as a connection health check, or to discover the agent ID a flow should send on behalf of.
Get Account Returns the account profile including company details and configuration, for flows that need to check what the current subscription allows.
List Webhooks Returns the webhook subscriptions registered on the account with their target URL, subscribed event types, and active state. Useful for auditing which external systems receive Cliengo events, including subscriptions created outside FlowRunner.

List WhatsApp Channels Returns the WhatsApp channels connected to the account. Each channel ID is required by the template operations, so this is the first call when building a WhatsApp flow.
List WhatsApp Templates Returns the approved templates registered on a channel. WhatsApp permits template messages only outside the 24-hour customer service window, so a name from this list is required before sending.
Send WhatsApp Template Message Sends an approved template to one or more recipients in a single call, optionally with a media header. Phone numbers must be in E.164 format and template variables are supplied positionally. The response reports successful and failed recipients separately.

Triggers

1 triggers

Event Triggers

On Cliengo Event Fires when the selected Cliengo event occurs, covering conversation lifecycle changes, new messages, notes, phase moves, tag changes, and contact create, update, status, assignment, and delete events. Delivers the documented webhook envelope with the event name, its timestamp, and the affected conversation or contact. FlowRunner registers the subscription when the flow is enabled and removes it when the flow is disabled, so no subscription is left behind when a flow is retired.

Frequently Asked Questions

What can FlowRunner do with Cliengo?

FlowRunner agents can run List Contacts, Get Contact, and Create Contact in Cliengo, plus 23 more actions.

Does connecting Cliengo to FlowRunner require OAuth?

No. Cliengo connects to FlowRunner with an API key, no OAuth flow required.

Can Cliengo trigger a FlowRunner workflow automatically?

Yes. Cliengo supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Cliengo

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us