Integration

Cliengo integration

Cliengo is a conversational marketing and lead capture platform (chatbots on web chat, WhatsApp, Facebook and Instagram). An agent can search, create, update and delete contacts (leads), list and manage conversations (messages, notes, assignment, transfer, close, reopen, pipeline phases, pausing the chatbot to answer as a human), manage tags, phases, channels, chatbots, users and webhook subscriptions, and send approved WhatsApp template messages (which spend WhatsApp balance). Not exposed: automations, Google Ads linking, chatbot flow and fulfillment settings, business hours, teams, conversation export, WhatsApp campaign reports, event history and the opt-out list, account integrations and account updates. Webhook secrets, custom headers and URLs, and channel and chatbot test links are not returned. Authentication is a Connect API token (sk_live_..., created in Cliengo under Integrations, Connect API) sent as Authorization: Bearer; the token's permissions decide which tools answer (403 otherwise). This file targets production (connect.cliengo.com); sk_test_ stage tokens do not work here. Rate limit per token by plan: 100 to 2,000 requests per minute.

Connect Cliengo How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Cliengo.Built from the 79 Cliengo tools below, on the connection you add once.

What you can do with Cliengo

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Conversation, 15 operations

assign_conversationAssign conversationPOSTAssigns a conversation to an operator (user id from list_users) and returns the conversation.
assign_phase_to_conversationAssign phase to conversationPATCHMoves a conversation to a pipeline phase (phaseId from list_phases). The vendor documents no response body.
close_conversationClose conversationPOSTCloses a conversation; isLead (required) says whether it resulted in a lead.
create_conversationCreate conversationPOSTCreates a conversation on a channel (channelId, companyId from get_account, channel WEB, WHATSAPP, FACEBOOK or INSTAGRAM, from = the originator).
delete_conversationDelete conversationDELETEDeletes a conversation by id (from list_conversations).
get_conversationGet conversationGETReturns one conversation by id: channel, status, participants, assignment, intervention times, phase, amount, tags and campaign data.
get_conversations_by_contactGet conversations by contactGETLists the conversations of one contact (id from search_contacts).
list_conversation_channelsList conversation channelsGETReturns the channel types (WEB, WHATSAPP, FACEBOOK, INSTAGRAM) that have active conversations.
list_conversationsList conversationsGETLists conversations with filters (status, tags, dates, channel, phase, agent, intervention, UTM, text). data is a map keyed by conversation id, not an array. Paged.
list_conversations_by_phaseList conversations by phaseGETGroups conversations by pipeline phase. Takes the same filters as list_conversations.
mark_conversationMark conversationPOSTMarks a conversation as read (read true) or unread (read false). The vendor documents no response body.
open_conversationOpen conversationPOSTReopens a closed conversation (status becomes ACTIVE).
set_chatbot_stateSet chatbot statePATCHPauses (OFF) or resumes (ON) the native chatbot in one conversation, for example to answer with add_conversation_message. Returns only the new chatbotState.
transfer_conversationTransfer conversationPOSTTransfers a conversation to another operator (user id from list_users) and returns the conversation.
update_conversation_contactUpdate conversation contactPUTUpdates the name, email or phone of the contact of a conversation. The vendor documents no response body.

Webhook, 9 operations

create_webhookCreate webhookPOSTSubscribes a URL to conversation events: Cliengo POSTs each event there. Active by default. Each delivery carries the secret in the X-Webhook-Secret header.
delete_webhookDelete webhookDELETEDeletes a webhook subscription and its whole delivery history permanently.
get_webhookGet webhookGETReturns one webhook subscription by id (from list_webhooks): events, channel, state and retries.
get_webhook_logsGet webhook logsGETReturns the delivery log of a webhook: each attempt's event, payload sent, HTTP status, error and success. Paged with offset and limit.
list_webhooksList webhooksGETLists the webhook subscriptions of the company, newest first, optionally for one channel (websiteId).
ping_webhookPing webhookPOSTSends a test POST to a URL to check it is reachable before creating a webhook (10 second timeout). No webhook needs to exist.
test_webhookTest webhookPOSTSends a real test event of the given type to a webhook; the payload carries test true and the delivery is logged.
toggle_webhookToggle webhookPATCHActivates (isActive true) or deactivates (false) a webhook without deleting it; a deactivated webhook gets no deliveries but keeps its settings and logs.
update_webhookUpdate webhookPUTUpdates a webhook subscription's events, active state, retries or custom headers. Only the fields sent change. The destination URL cannot be changed here: delete the webhook and create a new one.

User, 8 operations

create_userCreate userPOSTCreates a user (agent) with a name, email and optional role (values from list_user_roles).
delete_userDelete userDELETEDeletes a user by id (from list_users).
get_current_userGet current userGETReturns the user the API token belongs to.
get_userGet userGETReturns one user by id (from list_users).
invite_userInvite userPOSTInvites a person by email to join the company as a user, with an optional role. Cliengo sends them an invitation.
list_user_rolesList user rolesGETLists the user role names accepted by create_user, update_user and invite_user.
list_usersList usersGETLists the users (agents) of the company with name, email, role and active state. Paged with offset and limit.
update_userUpdate userPUTUpdates a user's name, email or role (values from list_user_roles).

Channel, 7 operations

assign_chatbot_to_channelAssign chatbot to channelPUTAssigns (action ADD) or removes (REMOVE) a chatbot on a channel. A channel has one chatbot at a time: ADD replaces any chatbot assigned before.
create_channelCreate channelPOSTCreates a channel of the given type: WEBSITE (with url), WHATSAPP_API or WHATSAPP_BUSINESS (with phone), FACEBOOK or INSTAGRAM.
delete_channelDelete channelDELETEDeletes a channel (soft delete) and unassigns its chatbot. For Facebook, Instagram and WhatsApp Business channels it also disconnects the channel on the Meta platform.
disconnect_channelDisconnect channelPOSTRequests the disconnection of a WHATSAPP_API channel on the origin platform (the only type supported); the channel gets disconnectionRequested true.
get_channelGet channelGETReturns one channel by id (from list_channels), including chatbot.id, the chatbot assigned to it.
list_channelsList channelsGETLists the active channels of the account (website, WhatsApp, Facebook, Instagram) with their connection state and assigned chatbot. Not paged.
update_channelUpdate channelPATCHUpdates a channel's label or title. Protected fields are ignored silently.

Contact, 7 operations

add_contact_tagAdd contact tagPOSTAdds a tag to a contact and returns the updated contact.
bulk_delete_contactsBulk delete contactsPOSTDeletes several contacts at once by id (from search_contacts). The vendor answers 207 (multi-status) with no documented body.
create_contactCreate contactPOSTCreates a contact (lead) on a channel (websiteId) with a name, optionally email, phone, status, assigned agent, a first note and custom fields.
delete_contactDelete contactDELETEDeletes a contact by id (from search_contacts).
get_contactGet contactGETReturns one contact by id (from search_contacts): contact data, status, rating, assigned agent, entry method and campaign (UTM) data.
search_contactsSearch contactsGETSearches contacts (leads) with filters: free text, email, name, phone, status, channel, assigned agent, entry method, tags, rating, creation and update dates. Paged (page, limit up to 100).
update_contactUpdate contactPATCHUpdates a contact's name, email, phone, status or assigned agent. Send the fields to change.

Chatbot, 6 operations

create_chatbotCreate chatbotPOSTCreates a chatbot from the account's base template. It starts with no channels: assign them with update_chatbot_channels.
delete_chatbotDelete chatbotDELETEDeletes a chatbot (soft delete). Its channels are not deleted.
get_chatbotGet chatbotGETReturns one chatbot by id. The chatbot id is not the channel id: read chatbot.id from get_channel.
list_chatbotsList chatbotsGETLists all chatbots of the account with their muted state and assigned channels. Not paged.
update_chatbotUpdate chatbotPATCHUpdates a chatbot's isMuted, title or name. A muted chatbot stops answering visitors. Assign channels with update_chatbot_channels.
update_chatbot_channelsUpdate chatbot channelsPUTChanges a chatbot's channel list in one step: ADD adds channelId (no duplicate), REMOVE removes it, CLEAN empties the whole list (channelId not needed).

Phase, 5 operations

create_phaseCreate phasePOSTCreates a pipeline phase (inbox stage) with a name and optional position (order).
delete_phaseDelete phaseDELETEDeletes a phase by id (from list_phases).
get_phase_countsGet phase countsGETCounts the conversations in each phase. Takes the same filters as list_conversations.
list_phasesList phasesGETLists the pipeline phases (inbox stages) of the conversations, in order.
update_phaseUpdate phasePUTRenames a phase or changes its position. Send the fields to change.

Tag, 4 operations

create_tagCreate tagPOSTCreates an operator tag with a name and optional hex color.
delete_tagDelete tagDELETEDeletes a tag by id (from list_tags).
list_tagsList tagsGETLists the operator tags of the company with their colors.
update_tagUpdate tagPUTUpdates a tag; name is required by the vendor, color is optional.

Whatsapp template, 4 operations

create_whats_app_templateCreate whats app templatePOSTSubmits a new WhatsApp template to Meta or Gupshup for approval (starts pending). For IMAGE, VIDEO or DOCUMENT first get a mediaId from upload_whats_app_template_media.
list_whats_app_templatesList whats app templatesGETLists the WhatsApp templates of a channel: approved, pending and rejected.
update_whats_app_templateUpdate whats app templatePUTSets a template active or inactive on the Cliengo side (soft delete), by its name, or replaces its header mediaId. Provider approval states cannot be set.
upload_whats_app_template_mediaUpload whats app template mediaPOSTUploads a media file used to CREATE a template with an IMAGE, VIDEO or DOCUMENT header; returns a mediaId for create_whats_app_template.

Plan, 3 operations

get_planGet planGETReturns one plan by id (from list_plans).
list_active_plansList active plansGETLists only the plans that can be subscribed to today.
list_plansList plansGETLists all Cliengo plans with their limits and prices in USD and ARS.

Account, 2 operations

get_accountGet accountGETReturns the authenticated Cliengo account (company): id, name, main email, active plan and account flags.
get_account_planGet account planGETReturns the plan of the account: tier, annual billing, lead, conversation, channel and user limits, and price in USD and ARS.

Conversation note, 2 operations

create_conversation_noteCreate conversation notePOSTAdds an internal note to a conversation, optionally with tags and quoted message ids.
list_conversation_notesList conversation notesGETLists the internal notes of a conversation.

Message, 2 operations

add_conversation_messageAdd conversation messagePOSTSends a message in a conversation for real: the visitor receives it on the channel (web chat, WhatsApp...). Pause the bot first with set_chatbot_state to answer as a human.
list_conversation_messagesList conversation messagesGETLists the messages of a conversation; includeCommands true also returns internal command events. Not paged.

Whatsapp message, 2 operations

send_whats_app_template_messagesSend whats app template messagesPOSTSends an approved WhatsApp template to one or more phone numbers for real; each send spends WhatsApp balance. Returns the successful and failed messages.
upload_whats_app_message_mediaUpload whats app message mediaPOSTUploads a media file (up to 16 MB) and returns a public mediaUrl to send with send_whats_app_template_messages for IMAGE, VIDEO or DOCUMENT templates.

Contact note, 1 operation

create_contact_noteCreate contact notePOSTAdds a note (message) to a contact. The vendor documents no response body.

Whatsapp campaign, 1 operation

get_whats_app_campaignGet whats app campaignGETReturns a WhatsApp campaign with the delivery status of each message sent (recipient phone, status, failure reason) and counts by status.

Whatsapp channel, 1 operation

list_whats_app_channelsList whats app channelsGETLists the channels that can send WhatsApp template (HSM) messages, with provider and hsmLineStatus; each id is the channelId for the other WhatsApp tools.

Use Cliengo from Claude Code, Cursor or Codex

Connect Cliengo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Cliengo operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Cliengo

Create your workspace
Sign up free. Nothing to install.
Connect Cliengo once
Add your Cliengo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.