Resources · Make integration

LiveChat Make integrationAutomate LiveChat with Make.

What if every closed chat or new tag in LiveChat kicked off the next task on its own? The LiveChat Make integration gives you 7 modules: 6 instant triggers and 1 API action. This guide walks support and sales teams through the connection, a first scenario and each module.

Try the LiveChat integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the LiveChat Make integration do for your team?

The LiveChat Make integration links your LiveChat account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches an app or acts in it. With LiveChat, those bricks react to what happens in your chats (a new conversation, a tag, a closed thread) and pass the details to any other app you use.

Tag-based routing. Your agents already tag conversations as sales, billing or bug. Put Watch Thread Tagged at the start of a scenario and each tag becomes a signal: a sales tag can add a row to a lead table, as shown on the Airtable Make integration page, while a bug tag can open a ticket in your tracker.

A follow-up once the conversation ends. Watch Chat Deactivated fires when the open thread of a chat is closed. That moment is a natural hook for a satisfaction email, a CRM note or a message to the account owner.

A pulse on who joins a chat. Watch User Added to the Chat and Watch User Removed from a Chat cover both customers and agents, so a manager can see when a colleague steps into a conversation or leaves it.

What the integration does not do: it lists no search module and only one action, Make an API Call. Anything beyond the six triggers goes through that module and the LiveChat API. If you are weighing both tools, the n8n vs Make comparison lays out the differences, and the Make training helps you build this kind of scenario with the team.

Connect

How do you connect LiveChat to Make?

  1. 01

    Add a LiveChat module

    In your Make account, open a scenario and add any LiveChat module. Because every trigger here is instant, Make first asks you to click Create a webhook, then Create a connection. A connection is your LiveChat account linked to Make once and reused by every LiveChat module.

  2. 02

    Name the connection

    The Connection name field is optional, yet worth filling. A clear label such as the team or the LiveChat license it belongs to saves guesswork when several people share the same Make organization later.

  3. 03

    Authorize with OAuth

    LiveChat authenticates through OAuth, and you need an active LiveChat account. Enter the credentials copied from LiveChat, or follow the instructions Make shows on screen to finish the connection. The advanced setup uses a Client ID and a Client secret created in LiveChat.

First scenario

Build your first scenario with LiveChat

GoalWhen an agent tags a thread in LiveChat, Make receives it at once and runs the LiveChat API call you chose for that tag.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas. That button adds the first module, which will start everything that follows.

  2. 02

    Pick Watch Thread Tagged

    Search for LiveChat, choose Watch Thread Tagged, click Create a webhook and then Create a connection. From now on, LiveChat tells Make each time a thread gets a tag.

  3. 03

    Add the API call

    Click the + on the right of the trigger and add Make an API Call from LiveChat. Pick the endpoint you need in the LiveChat API documentation, then map the thread data the trigger received.

  4. 04

    Test with Run once

    Click Run once, then tag a thread in LiveChat. Make shows the bundles each module received, a bundle being one item passed from a module to the next. Check that the API call got the right thread.

  5. 05

    Switch it on

    Save and switch the scenario on. With an instant trigger, there is no interval to wait for: LiveChat calls Make as soon as a tag lands, and each module run counts as one operation on your plan.

Triggers

Which LiveChat events can start a scenario?

6 modules start a scenario when something happens in LiveChat. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by LiveChat as soon as it happens.

LiveChat1Watch Chat Deactivated

Watch Chat Deactivated

Instant trigger

In Make“Triggers when a chat is deactivated by closing the currently open thread.”

Your scenario starts the moment a conversation wraps up: this trigger fires when a chat is deactivated because its open thread was closed. It is the cleanest end-of-chat signal the integration offers.

How it fires
instant, LiveChat calls Make through a webhook as soon as the thread closes, shown by the lightning badge on the module.
When to use it
send a follow-up message, log the finished conversation in your CRM or alert the account manager after a support exchange.
Watch out
it listens for the closing of the thread, not for the arrival of a message, so pair it with Watch Incoming Chat when you need both ends of the conversation.
LiveChat2Watch Incoming Chat

Watch Incoming Chat

Instant trigger

In Make“Triggers when a chat is coming with a new thread.”

You get a scenario that springs into action as soon as a visitor opens a conversation. The trigger fires when a chat comes in with a new thread, so each fresh discussion becomes a bundle Make can pass along.

How it fires
instant, LiveChat notifies Make through a webhook the moment the new thread starts.
When to use it
ping the sales channel when a visitor starts chatting, or create a lead in your CRM before the agent even replies.
Watch out
every new thread fires it, so add a filter in the scenario if you only care about some of them.
LiveChat3Watch Thread Tagged

Watch Thread Tagged

Instant trigger

In Make“Triggers when a thread is tagged.”

Tags your agents already apply turn into automatic actions with this trigger, which fires whenever a thread receives a tag. It is the easiest way to let the people in the chat decide where the conversation goes next.

How it fires
instant, LiveChat sends the event to Make through a webhook right after the tag is added.
When to use it
route a thread tagged as a bug to your ticketing tool, or copy a thread tagged as a hot lead into a sales table.
Watch out
one scenario receives every tag, so add a filter after the trigger to keep only the tags that matter for that flow.
LiveChat4Watch Thread Untagged

Watch Thread Untagged

Instant trigger

In Make“Triggers when a thread is untagged.”

Corrections stay in sync thanks to this trigger: it fires when a tag is removed from a thread. That lets a later scenario undo or update what an earlier tag set in motion.

How it fires
instant, LiveChat calls Make through a webhook as soon as the tag disappears.
When to use it
an agent removes an urgent tag after solving the issue, and you want the matching ticket or table row to reflect that change.
Watch out
it only knows that a tag left the thread, so the scenario still has to find the record the earlier tag created in the other app.
LiveChat5Watch User Added to the Chat

Watch User Added to the Chat

Instant trigger

In Make“Triggers when a user (customer or agent) is added to a chat.”

Managers gain visibility on staffing with this trigger, which fires when a user joins a chat. That user can be a customer or an agent, so the same event covers transfers and new participants.

How it fires
instant, LiveChat notifies Make through a webhook as soon as someone is added.
When to use it
log each time a senior agent is pulled into a conversation, or tell a team lead in your messaging app that a colleague has joined a tricky chat.
Watch out
customers and agents both fire it, so add a filter if the scenario should react to agents only.
LiveChat6Watch User Removed from a Chat

Watch User Removed from a Chat

Instant trigger

In Make“Triggers when a user (customer or agent) is removed from a chat.”

This trigger closes the loop on participants: it fires when a user, customer or agent, is removed from a chat. Paired with the previous trigger, it gives you a full picture of who was in a conversation.

How it fires
instant, LiveChat calls Make through a webhook the moment the user leaves the chat.
When to use it
update a shared board when an agent hands a conversation over, or record the exit of a participant for your own reporting.
Watch out
leaving a chat and closing it are two different events; for the end of the conversation, use Watch Chat Deactivated instead.
Modules

What else can Make do in LiveChat?

LiveChat gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

LiveChat1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module opens the whole LiveChat API to your scenario: it sends any authorized request to an endpoint you choose, reusing the connection you already created. It is the only action of the integration, the route for everything the triggers leave out.

When to use it
after a trigger, when you need LiveChat itself to do something in return, such as acting on the thread that just fired.
Watch out
you pick the endpoint and build the request yourself, with the LiveChat API documentation open.
Need help

Need help automating LiveChat with Make?

A person reads every message.

FAQ

Questions about the LiveChat Make integration

01Is the LiveChat Make integration free?
Yes, LiveChat is a standard app in Make, available from the Free plan. That plan allows 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 and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in operations per month. You still need your own LiveChat subscription, which is billed by LiveChat.
02What does it take to connect LiveChat to Make?
You need an active LiveChat account and a Make account. The connection uses OAuth: add a LiveChat module, click Create a webhook if the module is instant, then Create a connection and follow the authorization steps. For an advanced setup, you create your own app in the LiveChat Developer Console and paste its Client ID and Client secret into Make. The connection is made once and reused by every LiveChat module in your scenarios.
03Do LiveChat triggers in Make fire in real time?
Yes. All 6 LiveChat triggers are instant: LiveChat calls Make through a webhook as soon as the event happens, whether it is a new chat, a tag, a closed thread or a participant joining. No polling interval applies to them, unlike scheduled triggers that Make checks every 15 minutes by default. Each time a trigger fires, the modules that follow run and count as operations on your plan. Test each one with Run once before switching the scenario on.
04What if the LiveChat module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the LiveChat API with the connection you already have, so actions without a ready-made module stay within reach. The integration has no search module and only this one action, so it is the route for anything beyond the six triggers. You will need the LiveChat API documentation to pick the endpoint and shape the request. It reuses the same connection, so no extra setup is needed.
05Should a team pick Make or n8n for LiveChat?
It depends on what your team needs to build. In Make, LiveChat comes with 7 modules: 6 instant triggers covering chats, tags and participants, plus an API call module for the rest. If those events match your workflow, you can start in Make without writing code. Check the node list on the n8n side before choosing, and compare both tools on the features your scenarios depend on rather than on reputation. The n8n vs Make comparison on this site goes deeper.
Same platform

Other docs you might need on this stack.

Browse all integrations