Resources · Make integration

LiveAgent Make integrationAutomate LiveAgent with Make.

What if every new LiveAgent customer set off the next step on their own? The LiveAgent Make integration gives you 17 modules: one scheduled trigger, 13 actions and 3 searches. This guide is for support leads who want to connect the account and run a first scenario.

Try the LiveAgent integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the LiveAgent Make integration do for your support team?

The LiveAgent Make integration links your help desk to Make, a tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. With it, contacts, contact groups and tickets in LiveAgent can be created, read, changed or removed by a scenario instead of by hand.

A ticket opened for every new customer. Watch Contacts spots contacts added in LiveAgent, and Create a Ticket opens a follow-up ticket for each one, so a welcome call or an onboarding check never depends on someone remembering it.

Tidy contact groups. When data arrives from a form, a shop or a spreadsheet, List Groups finds the matching contact group and Create a Group opens it if it is missing. Check in Update a Contact whether the group can be set there; the documentation does not say.

Tickets that follow your other tools. Get a Ticket and Update a Ticket read and change a ticket when something happens elsewhere, while List Tickets pulls a set of tickets to send to a report.

Know the limits before you start. The only trigger is scheduled, so Make checks for new contacts on the scenario's clock instead of hearing from LiveAgent the instant it happens. Nothing here watches tickets directly. For anything the listed modules skip, Make an API Call reaches the rest of the LiveAgent API with the same connection. The Make documentation for this app also warns that parts of it were written with AI help, so confirm important details with LiveAgent. If you weigh other tools, the n8n vs Make comparison lays out the differences, the Make pricing page explains plans, and the Make training covers the editor step by step.

Connect

How do you connect LiveAgent to Make?

  1. 01

    Copy your domain and API key

    In LiveAgent, open Configuration in the main menu, then System, then API. That settings page shows the domain URL and the API key your connection needs. Keep both at hand.

  2. 02

    Add a LiveAgent module

    In your Make scenario, add any LiveAgent module and click Create a connection. A connection is your LiveAgent account linked to Make once, then reused by every LiveAgent module you add later.

  3. 03

    Name it and paste the credentials

    Give it a label in Connection name if you like (this field is optional), then paste the domain and the API key you copied, or follow the on-screen instructions. Save, and the module is ready to fill.

First scenario

Your first scenario: a follow-up ticket for each new contact

GoalWhen a new contact appears in LiveAgent, Make opens a ticket so your team follows up with that customer.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Pick Watch Contacts

    Search for LiveAgent, choose Watch Contacts and select your connection, or click Create a connection if this is your first LiveAgent module.

  3. 03

    Add Create a Ticket

    Click the + on the right of the trigger, pick Create a Ticket and map data from the contact so each ticket points to the right customer.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles, the items passed from module to module, so you can check which contact produced which ticket.

  5. 05

    Schedule and switch on

    Open the clock on Watch Contacts. A new scenario runs every 15 minutes by default; the Free plan cannot go below that, paid plans go down to 1 minute. Then switch the scenario on.

Triggers

What starts a LiveAgent scenario

1 module starts a scenario when something happens in LiveAgent. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by LiveAgent as soon as it happens.

LiveAgent1Watch Contacts

Watch Contacts

Scheduled trigger

In Make“Triggers when a new customer has been created.”

Watch Contacts starts your scenario whenever a new customer lands in LiveAgent, and hands each one to the next modules as its own bundle. That makes it the natural first brick for anything that should follow a new contact.

How it fires
it is a scheduled trigger, so Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
when a fresh customer record should open a ticket, join a group or be copied to another tool.
Watch out
its description covers newly created customers only, so do not count on it to catch edits of existing contacts.
Modules

Every LiveAgent module in Make

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

LiveAgent1

Create a Contact

Action

In Make“Creates a new contact.”

Create a Contact adds a customer to LiveAgent from data another app already holds, so your agents see the person before they even write in.

When to use it
after a sign-up form or a purchase in another tool, to have the contact waiting in the help desk.
Watch out
run List Contacts first if the same person may already exist, or you risk duplicates.
LiveAgent2

Create a Group

Action

In Make“Creates a new contact group.”

Create a Group sets up a new contact group in LiveAgent, which gives you a bucket to sort customers into later in the same scenario.

When to use it
when a new client account, region or product line needs its own group of contacts.
Watch out
check with List Groups that the group does not exist yet, so each run does not add another copy.
LiveAgent3

Create a Ticket

Action

In Make“Creates a new ticket.”

Create a Ticket opens a new ticket in LiveAgent, so a request coming from somewhere else lands in the same queue your agents already work from.

When to use it
when an event outside the help desk, like a failed payment or a new contact, deserves a follow-up by the support team.
Watch out
map values from earlier modules so every ticket names its customer.
LiveAgent4

Delete a Contact

Action

In Make“Deletes a contact”

Delete a Contact removes one customer record from LiveAgent, which keeps your contact base clean when someone should no longer be there.

When to use it
when another system marks a person as removed and LiveAgent should reflect it.
Watch out
treat the deletion as final. Test with Run once on a dummy contact before pointing it at real records.
LiveAgent5

Delete a Group

Action

In Make“Deletes a contact group.”

Delete a Group removes a contact group you no longer need, so agents stop picking an outdated group when they sort customers.

When to use it
when a client account closes or a campaign group has served its purpose.
Watch out
make sure you target the right group, for example by reading it with Get a Group first; a wrong mapping removes the wrong one.
LiveAgent6

Delete a Ticket

Action

In Make“Deletes a ticket.”

Delete a Ticket erases a ticket from LiveAgent, handy for clearing out tickets a scenario created by mistake or test tickets.

When to use it
while you build and test a scenario, to remove the tickets your trial runs left behind.
Watch out
nothing in the documentation says a deleted ticket can be recovered, so keep this module away from live customer conversations unless you are sure.
LiveAgent7

Get a Contact

Action

In Make“Gets a contact.”

Get a Contact fetches the full record of one customer you point to, so later modules can use details that the incoming data did not carry.

When to use it
when a ticket or another app gives you a contact reference and you need the rest of the profile.
Watch out
it reads one known contact; to search across many, use List Contacts instead.
LiveAgent8

Get a Group

Action

In Make“Gets a contact group.”

Get a Group reads one contact group so the scenario knows exactly what it is about to touch, a useful check before an update or a deletion.

When to use it
before Update a Group or Delete a Group, to confirm you picked the right one.
Watch out
it returns a single group; to browse all of them, switch to List Groups.
LiveAgent9

Get a Ticket

Action

In Make“Gets a ticket.”

Get a Ticket pulls the current state of one ticket, which lets a scenario decide what to do next based on what the ticket says right now.

When to use it
when another tool references a ticket and you want its details in Slack, a sheet or a CRM.
Watch out
the scenario needs to know which ticket to read, so map it from an earlier module.
LiveAgent10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any part of the LiveAgent API from your scenario, reusing the same connection, so you are not limited to the contacts, groups and tickets modules.

When to use it
when the task you need is missing from the list of modules on this page.
Watch out
you write the request yourself, so keep the LiveAgent API documentation open while you set it up.
LiveAgent11

Update a Contact

Action

In Make“Updates a contact.”

Update a Contact changes an existing customer record, so the profile your agents read stays in line with what your other tools know.

When to use it
when a customer edits their details in a portal or a CRM and LiveAgent should follow.
Watch out
point it at the right contact, usually found first with List Contacts or Get a Contact.
LiveAgent12

Update a Group

Action

In Make“Updates a contact group.”

Update a Group edits a contact group that already exists. No need to delete it and build it again when its name or purpose shifts.

When to use it
say a client renames its company or a segment gets a new label in your other tools.
Watch out
read the group with Get a Group first if several look alike, so the change lands on the right one.
LiveAgent13

Update a Ticket

Action

In Make“Updates a ticket.”

Update a Ticket changes a ticket that is already open, so progress made in another tool shows up where your agents look.

When to use it
when a refund is processed or an order ships elsewhere and the related ticket should say so.
Watch out
the scenario must know which ticket to change; keep that reference from the module that created or found it.
LiveAgent14

List Contacts

Search

In Make“Gets all contacts.”

List Contacts returns your LiveAgent contacts as separate bundles, one per person, which is how you check who is already there or process many at once.

When to use it
before Create a Contact, to avoid duplicates, or to export contacts to a spreadsheet.
Watch out
each bundle it returns makes every following module run again, and each run counts as an operation on your plan.
LiveAgent15

List Groups

Search

In Make“Gets all groups.”

List Groups brings back all your contact groups, which gives a scenario the full picture before it files a customer somewhere.

When to use it
to find the group that matches incoming data, or to decide whether Create a Group is needed.
Watch out
it can return zero, one or many groups, so plan what the next module does in each case.
LiveAgent16

List Tickets

Search

In Make“Gets all tickets.”

List Tickets gathers tickets from LiveAgent into a stream of bundles, ready to be counted, copied or reviewed by the modules that follow.

When to use it
for a support report in a sheet or a digest sent to your team chat.
Watch out
a long list means many operations downstream; test with Run once first to see how many bundles come back before you add costly modules after it.
Need help

Need help automating LiveAgent with Make?

A person reads every message.

FAQ

LiveAgent and Make: common questions

01Is the LiveAgent Make integration free?
Yes, on the Make side. LiveAgent is a standard app, available from the Free plan like the 3,000+ other standard apps. The Free plan keeps 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lift those limits and count usage in credits per month. You still need your own active LiveAgent account, which LiveAgent bills separately.
02What do you need to connect LiveAgent to Make?
An active LiveAgent account and two values from it: the domain URL and the API key. Both sit in LiveAgent under Configuration, then System, then API. In Make, add any LiveAgent module, click Create a connection, optionally name it, then paste the domain and the key. The connection is stored once and every other LiveAgent module in your scenarios can reuse it, so you do not repeat the setup for each module.
03Does the LiveAgent trigger in Make work in real time?
No. Watch Contacts is a scheduled trigger: Make asks LiveAgent for new contacts on the scenario's schedule instead of being notified the moment one appears. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest interval allowed, while paid plans can go down to 1 minute. For most follow-up work on new customers, that delay is fine; if it is not, a shorter interval on a paid plan is the lever.
04What if a LiveAgent module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the LiveAgent API through the same connection, so tasks outside contacts, groups and tickets stay within reach. You will need to shape the request yourself from the LiveAgent API documentation. Keep in mind that the Make documentation for this app says part of it was written with AI help and may contain mistakes, so check anything important with LiveAgent before relying on it.
05Should you use Make or n8n for LiveAgent?
It depends on the tool your team already runs. In Make, LiveAgent comes with 17 ready modules covering contacts, groups and tickets, plus Make an API Call for the rest, and a first scenario can be tested with Run once before you switch it on. n8n often has a node for the same app, so check whether it covers what you need. The fairest test is to build the same small scenario in both and keep the one that fits your workflow.
Same platform

Other docs you might need on this stack.

Browse all integrations