Resources · Make integration

tawk.to Make integrationAutomate tawk.to with Make.

What happens after a visitor closes the chat window on your site? The tawk.to Make integration gives you 3 instant triggers that fire on chats and tickets. This guide is for support and sales teams who want those conversations to land in other tools without copying them by hand.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the tawk.to Make integration do?

The tawk.to Make integration lets tawk.to start a scenario, which is the automation you build in Make, whenever a chat begins, a chat ends or a new ticket appears. It only listens: all 3 modules are triggers, and what happens next is handled by the other apps you add after them.

A ticket that reaches the right person. Watch New Ticket starts the flow the moment a ticket is created, so a scenario can pass it to your task tool, your CRM or a team channel instead of waiting for someone to check the inbox.

A live alert when a visitor starts talking. Watch Chat Starts fires on the first message of a chat, whether the visitor or an agent sends it. A sales team can use that signal to ping whoever is on duty.

A record of every finished conversation. Watch Chat Ends fires when a chat closes, which is the natural point to log it in a spreadsheet or a CRM for later follow-up.

What Make does not do here: this app has no action or search module and no Make an API Call module, so Make cannot reply to a chat or edit a ticket inside tawk.to. If you are still weighing tools, the n8n vs Make comparison lays out the differences, the Make pricing page explains plans, and the Make training helps if scenarios are new to you.

Connect

How do you connect tawk.to to Make?

  1. 01

    Add a tawk.to module

    In your scenario, click the + and search for tawk.to, then pick one of the three triggers. A module is one brick of a scenario. Make then asks you to set up the link with your account, through Create a connection or Add.

  2. 02

    Name the link and authorize it

    Naming it is optional, but a clear label helps once several people build scenarios. Then authorize Make on the tawk.to page, or paste the key tawk.to gives you. That link is your connection, reused by every tawk.to module.

  3. 03

    Save the connection

    Click Save. The triggers are instant: tawk.to calls Make through a webhook as soon as something happens. Once the scenario is switched on, each chat or ticket event reaches the module without any interval to set.

First scenario

Build your first scenario with tawk.to

GoalWhen a new ticket is created in tawk.to, Make sends it on to another app your team already checks.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module. An empty canvas is normal at this stage.

  2. 02

    Pick Watch New Ticket

    Search for tawk.to and choose Watch New Ticket. Click Create a connection or Add to link your account. Make keeps that connection for every later tawk.to module.

  3. 03

    Add the destination

    Click the + on the right of the trigger and pick the app that should receive the ticket. Map the data coming from Watch New Ticket into its fields. Each ticket travels as one bundle, a single item passed along.

  4. 04

    Test with Run once

    Click Run once, then create a test ticket in tawk.to. Make runs the scenario one time, and you can open each module to read the bundle it received.

  5. 05

    Switch it on

    When the test looks right, switch the scenario on. With an instant trigger there is no interval to tune: every new ticket starts a run, and each module run counts as one operation on your plan.

Triggers

tawk.to triggers in Make

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

tawk.to1Watch Chat Ends

Watch Chat Ends

Instant trigger

In MakeTriggers when a chat ends.

Starts your scenario the moment a chat closes, so a finished conversation can turn into a log entry, a follow-up task or a note on a contact without anyone doing it by hand.

How it fires
instant, tawk.to calls Make through a webhook as soon as the chat ends.
When to use it
after a sales chat, to log the exchange in your CRM while it is still fresh.
Watch out
it waits for the chat to close, so pick Watch Chat Starts instead when your team needs to react while the visitor is still there.
tawk.to2Watch Chat Starts

Watch Chat Starts

Instant trigger

In MakeTriggers when the first message in a chat is sent by a visitor or agent.

Gives you an early signal: the scenario starts on the first message of a chat, whether a visitor or one of your agents sent it.

How it fires
instant, tawk.to calls Make through a webhook as soon as that first message is sent.
When to use it
to alert the person on duty in a team channel so a visitor asking about pricing does not sit unanswered.
Watch out
a first message from one of your agents also starts the scenario, so an alert built on it covers chats your team opens as well as chats visitors open.
tawk.to3Watch New Ticket

Watch New Ticket

Instant trigger

In MakeTriggers when a new ticket is created.

Turns every new tawk.to ticket into the start of a scenario, which lets you route requests to the tools where your team actually works.

How it fires
instant, tawk.to calls Make through a webhook as soon as the ticket is created.
When to use it
when support requests should appear in a task board or a shared sheet the moment a customer submits them.
Watch out
the trigger only sees new tickets; Make has no tawk.to module to update or close them afterward.
Need help

Need help automating tawk.to with Make?

A person reads every message.

FAQ

Questions about tawk.to and Make

01Is the tawk.to Make integration free?
Yes. tawk.to is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans raise those ceilings, with a 1 minute minimum interval and unlimited active scenarios, and usage is counted in operations per month. This page does not cover the price of tawk.to itself.
02What is needed to connect tawk.to to Make?
A tawk.to account and a few clicks. The documentation lists no special prerequisite. You add a tawk.to module, click Create a connection, optionally name it, authorize Make on the tawk.to page or paste the key tawk.to provides, then click Save. The documentation also notes that adding webhooks to your tawk.to account does not require a connection, so do not be surprised if Make only asks you for a webhook at that step.
03Do the tawk.to triggers in Make react in real time?
Yes. All 3 tawk.to triggers are instant, not scheduled. tawk.to calls Make through a webhook as soon as a chat starts, a chat ends or a ticket is created, so the scenario runs right after the event instead of waiting for a polling interval. The 15 minute default schedule of new scenarios applies to scheduled triggers, which this app does not have. In practice, you switch the scenario on and each event starts a run on its own, with every module run counted as one operation on your plan.
04What if a tawk.to module is missing in Make?
It depends on what is missing. The app only offers three triggers and has no Make an API Call module, so Make cannot send a message or change a ticket inside tawk.to. The practical route is to let the trigger start the scenario and do the rest in another app, such as a CRM or a task tool. For a need that goes beyond that, the team at the agency can look at your case.
05Should tawk.to be automated with Make or n8n?
It depends on the tool your team already uses. The same app often has an n8n node too, so both can usually listen to tawk.to. Compare them on the triggers each one offers for tawk.to, on how comfortable your team is with the editor, and on the plan that matches your volume. With Make, the three instant triggers cover chat starts, chat ends and new tickets, and each module run counts as one operation.