Integration · Help desk
AI agents for LiveAgent
Find and read tickets and their messages, open tickets, change status, department, agent and tags, keep the ticket's sidebar note, and look up contacts in LiveAgent.
- Actions
- 13
- Read
- 9
- Write
- 4
Actions
What your agents can do in LiveAgent
13 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 9
Look things up. Nothing changes.
Find tickets
Lists tickets, 10 a page by default, oldest first unless sorted otherwise, filtered with LiveAgent's filters.
Get a ticket
Reads one ticket by its ID (or code).
List ticket messages
Reads a ticket's conversation as message groups (an email, a chat, a call, an internal note …), oldest first, 10 groups a page.
Get the ticket's sidebar note
Reads the note in a ticket's sidebar, the agents' running notes about the customer or case.
Find contacts
Lists contacts, 10 a page by default, optionally filtered with LiveAgent's filters JSON, like {"company_id":"abc123"} or [["date_created","D>=","2026-01-01"]].
Get a contact
Reads one contact by ID (a ticket's owner_contactid).
List agents
Lists agents, 100 a page.
List departments
Lists departments.
List tags
Lists tags.
Write 4
Create, change or send.
Create a ticket
Opens a ticket in a department with a subject and a message.
Update a ticket
Changes a ticket's status (N new, C open, A answered, R resolved, W postponed, B spam), its agent, its department, its subject or its tags.
Set the ticket's sidebar note
Replaces the note shown in the ticket's sidebar (agents only; the customer never sees it).
Create a contact
Adds a contact with a first and last name, emails, phones, a job title, a note and a company ID.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your LiveAgent account.
What you enter
- API v3 key
Settings
- LiveAgent address
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your LiveAgent data
Ask a question in plain words. The agent can find tickets, get a ticket or list ticket messages in LiveAgent, then answers with what it found.
- 02
Let an agent update LiveAgent
Have the agent create a ticket or update a ticket in LiveAgent as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent LiveAgent and Slack: it can find tickets in LiveAgent and post a summary to a Slack channel in the same run.
FAQ
LiveAgent and MyDeepAgents
Can MyDeepAgents connect to LiveAgent?
Yes. The LiveAgent connector has 13 actions: 9 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect LiveAgent?
Paste an API key from your LiveAgent account. You'll need: API v3 key. The connection also asks for: LiveAgent address. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in LiveAgent without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs.
Can I use LiveAgent in workflows as well as agents?
Yes. Every LiveAgent action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put LiveAgent to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.