# Cliengo integrations: contacts and conversations

> Create a contact, send a message and create a tag in Cliengo, and start a workflow when Cliengo sends “Conversation created”.

**Canonical page:** https://tray.ai/connectors/cliengo-integrations/
**Categories:** Sales
**Connects through:** HTTP Connector

## Overview

Cliengo is a chatbot and conversation platform for sales teams that captures leads from websites, WhatsApp, and social channels, with live chat handoff and a contact inbox. Tray.ai connects to Cliengo through the HTTP Connector, so your workflows can call the Cliengo API alongside the rest of your stack.

## Use cases

### Contacts

Read, create, update, and delete contacts in Cliengo from any Tray.ai workflow. The Cliengo API covers calls such as search contacts and create a contact.

- Search contacts
- Create a contact
- Update a contact

### Conversations

Read, create, and update conversations in Cliengo from any Tray.ai workflow. The Cliengo API covers calls such as list conversations and get a conversation.

- List conversations
- Get a conversation
- Send a message

### Tags

Read, create, update, and delete tags in Cliengo from any Tray.ai workflow. The Cliengo API covers calls such as list tags and create a tag.

- List tags
- Create a tag
- Update a tag

### Phases

Read, create, and update phases in Cliengo from any Tray.ai workflow. The Cliengo API covers calls such as list phases and create a phase.

- List phases
- Create a phase
- Assign a phase to a conversation

### WhatsApp templates

Read and create whatsapp templates in Cliengo from any Tray.ai workflow. The Cliengo API covers calls such as list WhatsApp templates and create a WhatsApp template.

- List WhatsApp templates
- Create a WhatsApp template
- Send template messages

### Webhooks

Read, create, update, and delete webhooks in Cliengo from any Tray.ai workflow. The Cliengo API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- Update a webhook

## Challenges Tray.ai solves

### Keeping Cliengo credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Cliengo credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Cliengo API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Cliengo API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Cliengo?

Yes. Tray.ai connects to Cliengo through the HTTP Connector, which calls the Cliengo API directly. Any call the Cliengo API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Cliengo?

The Cliengo API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Cliengo connector?

Cliengo runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Cliengo connector from the Cliengo API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/