# LiveAgent integrations: tickets and contacts

> Create a ticket, create a contact and create a company in LiveAgent. Connect LiveAgent to the rest of your customer service stack with Tray.ai.

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

## Overview

LiveAgent is a help desk that gathers email, live chat, calls and social messages into one ticket queue for customer support teams. Tray.ai connects to LiveAgent through the HTTP Connector, so your workflows can call the LiveAgent API alongside the rest of your stack.

## Use cases

### Tickets

Read, create, and delete tickets in LiveAgent from any Tray.ai workflow. The LiveAgent API covers calls such as list tickets and create a ticket.

- List tickets
- Create a ticket
- Get a ticket

### Contacts

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

- List contacts
- Create a contact
- Update a contact

### Companies

Read, create, update, and delete companies in LiveAgent from any Tray.ai workflow. The LiveAgent API covers calls such as list companies and create a company.

- List companies
- Create a company
- Update a company

### Agents

Read and update agents in LiveAgent from any Tray.ai workflow. The LiveAgent API covers calls such as list agents and get an agent.

- List agents
- Get an agent
- Update an agent

### Tags

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

- List tags
- Create a tag
- Update a tag

## Challenges Tray.ai solves

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

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

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

The LiveAgent API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated LiveAgent connector?

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