Better compatibility with Zapier and other CRM's

Community Discussion
1

PLEASE PLEASE PLEASE, expand the functionality with Zapier.

We currently use Zapier to automatically import the new chat lead into our CRM, Hubspot. Currently, we can only get the Name, Email, Phone, Zip Code, and IP City in to Hubspot using the initial chat form fields and some thoughtful extraction methods in Zapier.

It’s not very intuitive, despite it being super basic info.

The other data that would be SUPER HELPFUL is if we could get the First Agent or All Agents that answered the chat available as a data point, and the actual message transcript, so we can automatically import that into Hubspot as well using Zapier.

The other HUGE thing would be if Tawk.to could listen for Google Ads identifiers from the URL or certain tracking cookies, (the GCLID and Hubspot tracking cookie) and allow us to carry that into Hubspot automatically for Ad tracking and Web analytics tracking.

These are pretty basic feature requests for this type of software. VERY important for proper tracking.

Can we please get these features soon?

2

Hi lorenzoenns,

Thank you for your request. Our team is currently exploring expanding Zapier functionality and opening up data points for more integrations with our system and your feedback has been noted for consideration.

Keep an eye out for updates and let us know if there is anything else you would wish to see improved.

3

Hello,
I have the same need, I need Tawk.to could listen for Google Ads identifiers from the URL or certain tracking cookies, (the GCLID and Hubspot tracking cookie) and allow us to carry that info our CRM automatically for Ad tracking and Web analytics tracking.
You can do something for this point or that has to be resolve from Tawk.to.
Thanks in advance

4

Hi Andreas,

Thanks for sharing your suggestion to improve identifiers on Google Ads for tracking and web analytics.

We’ve passed it along to our product team for review. While we can’t guarantee a timeline, we’re always working to improve tawk.to based on feedback like yours.

Let me know if you have any questions, feedback, or other suggestions. Happy to help.

5

Do i need to be on a specific plan with Tawk to use it in a Zap.

I created a Zap that triggers upon new ticket created and it test succesfful all the way through, no reason it shouldn’t work. Basically it creates contact in another application. When new chat is opened.

Zapier support is nada, i’m on the $29/month plan, and its a two step zap, it should work but each time I turn on the Zap it turns right back off.

So to test I isolated and created a zap for each app. For example I had Tawk.to trigger the same action as a different zap which is SMS by Zapier (Sends me an SPS), and basically said if a new chat, text me and all test were successful I received the text, BUT when I endabled the Zap it turned itself OFF again.

I setup the Zap witht he other APP that i originally attempted to use with Tawk and enabled the Zap for it, and it turned on and ran fine.

Sooo do I need to upgrade my license with Tawk to allow for Zapier to connect, should I use a webhook instead or is there something in the setting in Tawk I need to adjust as it appears Tawk is the issue. The crazy parrt is I can connect my Tawk.to account in Zapier and the connection test run fine, no issues, only issues after the Zap is attempted to be enabled.

6

Hi,

Thanks for reaching out and sharing those details!

You don’t need to be on any specific plan with tawk.to to use it with Zapier — the integration is available to all users, including free accounts.

However, in order for the Zap to work properly, you need to make sure that the right event is set up in tawk.to to trigger the Zap. Just connecting your tawk.to account and passing Zapier’s test isn’t enough — the actual action in tawk.to that triggers the event (like creating a new ticket or chat) must occur within the app itself during live usage for Zapier to pick it up.

If your Zap is turning off automatically, it’s often because:

  • Zapier didn’t receive any real data after activation.
  • The trigger is not being fired as expected.
  • Or there’s a setup step missing in tawk.to that’s needed to generate the trigger event.

If you’re trying to capture new chat activity, make sure your trigger in Zapier is based on “New Chat Started” or “New Ticket Created” depending on your workflow, and that those actions are actively happening.

Let us know what exact trigger you’re using in the Zap — we can help confirm how to set it up on tawk.to’s end to ensure it fires correctly. If needed, using a webhook is also a good workaround.

7

I’m curious to know if anyone is having issues when enabling a Zap with Tawk.to as the trigger. I’ve worked with Zapier support on this for several days and finally got a reply that makes sense, that said, Zapier Support isn’t able to resolve the issue since the error is coming from Tawk.to servers,

The zap is a simple two step Zap with tawk.to as the trigger.
I"m able to setup the Zap,
All test during setup are successful. The zap runs fine when manually testing it during setup or edit stages it runs without issue and sends the data to the CRM exactly how I set it up to do.

  • The ISSUE occurs when attempting to enable the zap, and the reason it is disabling itself is bc Tawk servers are giving the server 500 error.

If you have a Zap setup using Tawk as the trigger or action and its turned on, I would expect it to work as it should
BUT
If you were to create a new Zap with Tawk as the trigger and you would be able to setup the zap successfully and all test during the setup are successful. I’m willing ot bet if you did this and then attempted to publish the zap , you would see that it turns right back off, and any attempt to turn it on results in the same thing.

RESPONSE

500

alt-svc: h3=“:443”; ma=86400
cf-cache-status: DYNAMIC
cf-ray: 96a645ca6c862a30-IAD
connection: close
content-length: 35
content-type: application/json
date: Tue, 05 Aug 2025 12:24:38 GMT
server: cloudflare
strict-transport-security: max-age=0; includeSubDomains; preload
x-content-type-options: nosniff

{
“ok”: false,
“error”: “server_error”
}

8

Hi @llinton180,

Thanks for sharing the details.

We haven’t had any other reports of this. tawk.to triggers in Zapier are working normally for other users. The fact that your tests succeed but the Zap fails only when turning it on suggests something account or property-specific on your end, not a general outage.

A few things worth checking:

  1. Permissions — Make sure the Zapier connection is authenticated with an Owner/Admin account for that property. Webhook subscriptions can fail if the connected user doesn’t have full rights.
  2. Re-authenticate — In Zapier → My Apps → tawk.to → Reconnect, then try enabling the Zap again.
  3. Different property/account test — Try creating the same Zap using a different tawk.to property (or a different account login) to see if the issue repeats.
  4. Minimal repro — Create a new Zap with only a single tawk.to trigger, then publish. If that fails too, it confirms the problem is tied to the subscription call from your account.
9

thanks for the reply, and just wanted to confirm each of those have been tested even with a single step zap, and no other apps. I’'ve connected and reconnected my account
I think the fact that I can creeate the Zap successfully (which means my account is connected, it pulls the data from Tawk.to into Zapier during

So it shows this proves that my account, and everything should work but enabling the Zap and the task that happen during the process of turning it on, this is between Zapier and Tawk.to, meaning Zapier has to setup a webhook, and few other for the zap to be enabled and work correctly so its Zapier attempting to connect to Tawk.to via api.tawk not me (when enabling or turning on the Zap) t

The issue only occurs after I have setup the Zap successfully when I attempt toe enable it

unfortunately there is no way for me to provide a screenshot of the error message that Zapier provided to me, this is the error log that is happening each time Zapier attempts to connect to tawk so

RESPONSE

500

alt-svc: h3=“:443”; ma=86400
cf-cache-status: DYNAMIC
cf-ray: 96a645ca6c862a30-IAD
connection: close
content-length: 35
content-type: application/json
date: Tue, 05 Aug 2025 12:24:38 GMT
server: cloudflare
strict-transport-security: max-age=0; includeSubDomains; preload
x-content-type-options: nosniff

{
“ok”: false,
“error”: “server_error”

Zapier says it best below in quotes:

"I want to start out by clarifying why you’re experiencing an error when trying to turn on the Zap compared to setting it up and testing it: When you turn the Zap on, our system reaches out to Tawk to set up a webhook subscription on their end. This allows them to send us a webhook request to notify us about new chat starting events, which in turn triggers your Zap. This webhook subscription process only occurs when turning the Zap on, not during any testing or setup phases.

Next, when you contacted Tawk, did you share the log output I previously sent you? That log shows the 500 error Tawk returned to us when we attempted to set up the webhook subscription on their end. If not, I recommend reaching back out to them with that specific log. This will help them investigate the specific request causing the issue, so they can focus in on that."

10

LOL iits bogus to me that people don’t duplicate issues or really any troubleshooting… after like 4 days Zapier did do troubleshooting and the error message indicates that its Tawk not alllowing Zapier to connect and do there thing

One could duplicate the issue by logging into Zapier, create a zap with Tawk.to as the trigger, and once setup, click Publish. You will see that the Zap attempts to turn on but when you refresh or go back to the dashboard it will be turned off. You can attempt to turn it on again, and it will turn right back off

If that isn’t the case, I will apologize

11

Hi @llinton180, thanks for your message. We’ll test this internally, and get back to you ASAP.

13

We found the issue – looks like you are an “agent” of the property.

Only property “admins” can set up and configure webhooks.

Please contact your property admin to upgrade your role.

This can be done from Admin > User Management > Property Members.