Resources · Zapier integration

LiveAgent Zapier integrationAutomate LiveAgent with Zapier.

LiveAgent Zapier integration: 2 triggers that spot new customers, 4 actions that add customers, open conversations and sort people into groups, and 0 search steps. Here is what each one does, what it costs on your plan, and where it breaks.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LiveAgent Zapier integration does for your helpdesk

The LiveAgent Zapier integration links your LiveAgent helpdesk to the rest of your tools through Zapier, a service that runs automations without code. It notices when a customer appears in LiveAgent, and it can add customers, move them between groups or open a conversation for you, from steps you set up once.

Three results come up again and again. A customer list nobody retypes: Add New Customer creates the contact from an email address that arrived somewhere else. Groups that stay current: Add Customer to Group and Remove Customer From Group move a customer in or out of a named group when their situation changes. A conversation that starts without anyone opening the helpdesk: Create Conversation writes a subject and a message into the department you pick.

What Zapier does not do here matters just as much. Both triggers watch for new customers only, so nothing fires on a new conversation or a new message. There is no search step either: a Zap cannot look up an existing LiveAgent customer before it acts. And neither trigger is instant. Zapier checks on a timer, so a new customer reaches your Zap at the next check, not the moment it is added.

Comparing tools before you build? See our LiveAgent Make integration page and our Make vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, in plain English, so the rest of the page reads without a manual.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event that starts a Zap. Here, a new customer showing up in LiveAgent; once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes or sends something for you, like opening a LiveAgent conversation.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts exactly those.
Polling vs instant
Polling: Zapier asks the app for new items on a timer. Instant: the app calls Zapier as it happens. Both LiveAgent triggers poll.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already stored in an app so later steps can use it. LiveAgent offers none on Zapier.
Connection
Your LiveAgent account linked to Zapier once, then reused by every step of every Zap that touches LiveAgent.
Cost

What LiveAgent on Zapier really costs

The trigger never costs a task, and neither does Zapier checking LiveAgent for new customers, however often it looks. Only a completed action is billed. An action that fails is not counted.

  • Premium appNo, works on Free
  • Free plan100 tasks a month, 2-step Zaps
  • Trigger checks0 tasks
  • BilledEach successful action

LiveAgent is not a premium app, so it works on the free plan: 100 tasks a month and unlimited Zaps, but two steps per Zap. Add a second action, a filter or a search and you get a multi-step Zap (anything beyond one trigger and one action), which needs a paid plan. A Zap running Add Customer to Group then Create Conversation costs two tasks per customer. The grid shows how often Zapier checks for new customers on each plan.

Connect

Connect LiveAgent to Zapier in 3 steps

  1. 01

    Open your connections

    In your Zapier account, open the Apps page and click + Add connection. Before you start, have a LiveAgent account at hand, plus read or write access on anything you do not own and want the Zap to touch.

  2. 02

    Pick LiveAgent

    Type LiveAgent in the search box of the dialog, select it, then click Add connection. A new tab opens on the LiveAgent side, where you sign in with your usual account.

  3. 03

    Sign in and grant access

    Sign in to LiveAgent in that tab and grant Zapier access to the account. From there, every LiveAgent step you add to a Zap can reuse this connection without asking again.

First Zap

Your first Zap: file new customers into a group

GoalEvery new LiveAgent customer who meets your condition lands in the right group, with nobody sorting by hand.

  1. 01

    Create the Zap

    Start a new Zap in Zapier. You build it in order: the app and event that start it, then the step that follows, then the fields you map between them.

  2. 02

    Set the trigger

    Choose LiveAgent, then New Customer (Experimental) as the event, and select your connection. It is the one whose description carries the note uses API v3.

  3. 03

    Test on a real customer

    Test the trigger. Zapier brings back the three most recent customers of the connected account, so you map from a real record instead of guessing.

  4. 04

    Add the filter

    Click the plus icon and add a Filter. Fill the three boxes: the field to look at, the rule, and the value to compare with. Use a text rule on text, or it never passes. This filter makes the Zap multi-step, so it needs a paid plan.

  5. 05

    Add the action

    Add LiveAgent with Add Customer to Group. Map the customer email into Email Address, type the group name into Name of Group, then test and read what came back.

  6. 06

    Publish

    Click Publish to switch the Zap on. It handles customers added from now on; the ones already in LiveAgent stay where they are.

Triggers

LiveAgent triggers on Zapier

2 events start a Zap when something happens in LiveAgent. Zapier checks for them at the interval your plan allows.

1

New Customer (Experimental)

Polling trigger

In Zapier“Triggers when a new customer is added to system. (uses API v3).”

Starts your Zap each time a new customer is added to LiveAgent, and its description carries the note uses API v3. The new customer's details are then available to every step after it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
for a new Zap that should react to fresh customers, for instance to file them into a group or open a first conversation.
Watch out
the label says Experimental, so test it on a real customer before you publish, and keep the other trigger in mind if that test leaves you unsure.
2

New Customer

Polling trigger

In Zapier“Triggers when a new customer is added to system.”

A second way to catch the same event, a customer added to LiveAgent. Unlike its Experimental sibling, its description carries no version note at all.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
when a Zap you built earlier already runs on it and does its job, keep it rather than rebuilding everything on the other trigger.
Watch out
pick one of the two per Zap. Running both on the same account means each new customer starts two Zaps and can cost tasks twice.
Actions

LiveAgent actions on Zapier

LiveAgent gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Customer to Group

Action

In Zapier“Add customer to group.”

Puts a customer into a named LiveAgent group, found by email address.

When to use it
right after the trigger, to file the customer under the group your team works from.
Watch out
Email Address and Name of Group are both required, and the group name is typed by hand, so copy it exactly as it reads in LiveAgent.
2

Create Conversation

Action

In Zapier“Creates new conversation.”

Opens a fresh conversation in LiveAgent, with a subject and a message body, in the department you choose and addressed to a recipient email.

When to use it
when something that happens in another app should land in front of your support team as a conversation they can answer.
Watch out
five fields are required, and Email Address must be the user ID or email of an agent or customer who already exists.
3

Add New Customer

Action

In Zapier“Adds new contact/customer to system.”

Creates a contact in LiveAgent from one required field, the customer's email.

When to use it
when someone signs up or writes to you elsewhere and should exist in LiveAgent before any group or conversation step runs.
Watch out
if another Zap watches new customers on the same account, this action sets it off in turn, so keep the two from feeding each other.
4

Remove Customer From Group

Action

In Zapier“Removes customer from particular group.”

Takes a customer out of a particular group, matched on the email address and the group name, both required.

When to use it
paired with Add Customer to Group, so a customer whose situation changes leaves the old group as they join the new one.
Watch out
this step and Add Customer to Group make two tasks per move, and together they need a paid plan in a single Zap.
When it breaks

When the LiveAgent integration breaks

Zapier attaches no help article to LiveAgent, and no rate limit specific to the app is published. What breaks is general Zapier behavior, and it hits this app like any other.

Four cases cover most surprises. If one of them stops a Zap and the cause is not obvious, see Zapier troubleshooting.

  • Nothing from before the Zap

    A Zap only reacts to customers added after you publish it. Customers already in LiveAgent are not picked up, and moving that backlog is a separate job.
  • A Zap that feeds itself

    Add New Customer writing into the account that New Customer watches can restart the Zap again and again, and burns through your task count fast.
  • Flood protection on big batches

    After a bulk import or a migration into LiveAgent, the trigger may return a huge batch at once, and Zapier's flood protection can hold it back.
  • No double starts

    On a polling trigger, Zapier keeps track of the customers it has already seen, so the same customer does not start the Zap twice.
Need help

Need help automating LiveAgent with Zapier?

A person reads every message.

FAQ

LiveAgent Zapier integration: FAQ

01Is the LiveAgent Zapier integration free?
Yes, as long as your Zap stays at two steps. LiveAgent is not a premium app, so it runs on the free Zapier plan, which gives 100 tasks a month and unlimited Zaps. The catch is the shape of the Zap: the free plan allows one trigger and one action, nothing more. Add a second LiveAgent action, a filter or a search, and the Zap becomes multi-step and needs a paid plan. Your LiveAgent subscription is a separate question that Zapier pricing does not cover.
02How many tasks does a LiveAgent Zap use?
One task per successful action, and nothing for the trigger. Zapier checking LiveAgent for new customers costs nothing however often it runs, and an action that fails is not counted. A Zap that adds a customer to a group and then opens a conversation uses two tasks per customer, so 100 tasks cover 50 customers. The real drain is a loop: an Add New Customer step writing into an account that a New Customer trigger watches can start the Zap over and over.
03Does LiveAgent trigger Zaps in real time?
No. Both LiveAgent triggers are polling triggers: Zapier asks LiveAgent for new customers at a fixed interval set by your plan. That is every 15 minutes on Free, every 2 minutes on Professional and every minute on Team and Enterprise. On paid plans you can change how often it checks, and you can run a check by hand from the editor. That type is decided on the LiveAgent side, so no setting in the editor turns these triggers into instant ones.
04What does it take to connect LiveAgent to Zapier?
A LiveAgent account you can sign in to, plus read or write access on anything you do not own and want the Zap to touch. The connection starts from the Apps page of your Zapier account with + Add connection: you pick LiveAgent, sign in in the tab that opens and grant access. If you plan to use Create Conversation, also check that the department exists and that the creator email belongs to an existing agent or customer.
05Which LiveAgent New Customer trigger should you pick?
Either one catches a customer added to LiveAgent, and both poll at the interval of your plan. The only visible difference is the description: New Customer (Experimental) has a short note saying it relies on version 3 of LiveAgent's connection, New Customer has no such note. Building from scratch? The Experimental one is the natural pick, but its label is a good reason to test it on a real customer first. Whichever you choose, run only one of the two per account, or each new customer starts two Zaps.
06What if the LiveAgent action you need does not exist?
Then no Zapier setting will create it: the list is fixed by the integration. What you get is 4 actions (add a customer, file them in a group, take them out, open a conversation) and no search step, so updating a ticket that is already open or finding a known customer is out of reach here. Two honest routes remain. Reshape the flow so that it starts from a new customer and ends with one of those 4 actions. Or look at the same app on Make or n8n, since each tool publishes its own list of operations.
07Zapier, Make or n8n for LiveAgent?
Pick by criteria rather than by brand. Start with the operations: if the 2 triggers and 4 actions on this page cover your flow, Zapier gets you running fastest, and a one-trigger, one-action Zap stays on the free plan. Then look at the shape of the flow: a filter or a second action pushes you to a paid Zapier plan, so check how Make and n8n count steps and runs for the same job. Finally weigh speed: both triggers here poll, so the check interval of your plan sets how fast a new customer shows up.