# LiveChat integrations: chats and chat users

> Start a chat, add a user to a chat and update a customer in LiveChat, and start a workflow when LiveChat sends “Incoming chat”.

**Canonical page:** https://tray.ai/connectors/livechat-integrations/
**Categories:** Customer service
**Connects through:** HTTP Connector

## Overview

LiveChat is customer service software for chatting with website visitors, letting agents answer, transfer and close chats and keep customer records. Tray.ai connects to LiveChat through the HTTP Connector, so your workflows can call the LiveChat API alongside the rest of your stack.

## Use cases

### Chats

Read and create chats in LiveChat from any Tray.ai workflow. The LiveChat API covers calls such as list chats and start a chat.

- List chats
- Start a chat
- Get a chat

### Events

Create events in LiveChat from any Tray.ai workflow. The LiveChat API covers calls such as send a message event and upload a file.

- Send a message event
- Upload a file

### Chat users

Create and delete chat users in LiveChat from any Tray.ai workflow. The LiveChat API covers calls such as add a user to a chat and remove a user from a chat.

- Add a user to a chat
- Remove a user from a chat

### Customers

Read and update customers in LiveChat from any Tray.ai workflow. The LiveChat API covers calls such as get a customer and update a customer.

- Get a customer
- Update a customer
- Ban a customer

### LiveChat events

Start a Tray.ai workflow the moment something happens in LiveChat. LiveChat sends events such as incoming chat and chat deactivated to a Tray.ai webhook trigger.

- Incoming chat
- Chat deactivated
- Chat transferred

## Challenges Tray.ai solves

### Keeping LiveChat 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 LiveChat 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 LiveChat 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 LiveChat 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 LiveChat?

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

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

The LiveChat API uses basic authentication and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated LiveChat connector?

LiveChat runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated LiveChat connector from the LiveChat 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/