AFI
Tawk.to Live Chat
Tawk.to is a free live chat and messaging platform for websites. Advanced Form Integration captures Tawk.to chat events (typically chat-end, where a transcript and visitor info become available) and routes the data to any of 200+ destinations.
What you’ll need
- A Tawk.to account with the chat widget installed on your site.
- The Advanced Form Integration plugin installed and activated.
- The Tawk.to webhook configured to point at your AFI inbound endpoint (we’ll set this up below).
How AFI receives Tawk.to data
Tawk.to doesn’t fire WordPress hooks the way form plugins do. Chat happens entirely in Tawk.to’s cloud. AFI catches Tawk.to data via Tawk.to’s outbound Webhooks feature: you point a Tawk.to webhook at your AFI endpoint, and Tawk.to POSTs chat events (chat start, chat end, ticket created) to AFI as they happen.
Configure the Tawk.to webhook
- Log in to your Tawk.to dashboard.
- Click your profile icon and go to Administration.
- Pick the property (site) you want to connect.
- Open Settings → Webhooks.
- Click + Add Webhook.
- Set the Endpoint URL to your AFI inbound URL. See Inbound Webhooks for how to generate one. (The shape is
https://yoursite.com/?adfoin_inbound_webhook=abc123.) - Tick the events you want to capture: at minimum, Chat End.
- Save.
Capture sample data in AFI
Once the Tawk.to webhook is saved, have a quick test chat on your site and end it. Then in AFI, go to Inbound Webhooks, find your endpoint, and click Capture Sample Payload. AFI parses the Tawk.to JSON and exposes the visitor name, email, message transcript, page URL, and other fields for mapping.
Create the integration
- Go to WP Admin → AFI → Add New.
- In Trigger → Form/Data Provider, select Tawk.to Live Chat (or Inbound Webhooks if you set this up via the inbound webhook flow).
- In Form/Task Name, choose the Tawk.to webhook.
- In Action → Platform, pick the destination and complete the field mapping using the captured Tawk.to fields.
- Optional: configure Conditional Logic.
- Click Save Integration.
Useful integrations
- HubSpot CRM / Pipedrive / Zoho: turn every chat-end visitor into a CRM contact.
- Slack: ping the team in real time when a chat happens.
- Mailchimp / Brevo: add chat visitors to a follow-up email segment.
- Google Sheets: log every chat for analysis.
Conditional logic example
Goal: only push chats where the visitor left an email address to your CRM (skip anonymous browsers).
Open the integration’s Conditional Logic panel, add a condition with the email field, Not Equal To, value blank. Anonymous chats are skipped; chats where the visitor identified themselves flow to the CRM.
Troubleshooting
Tawk.to webhook configured but AFI doesn’t receive
Tawk.to retries failed webhooks for 24 hours. Check AFI → Log for inbound POSTs. If nothing appears, confirm the URL pasted in Tawk.to matches exactly what AFI shows in Inbound Webhooks.
Field labels look generic
The Tawk.to payload uses keys like visitor.name, visitor.email, chatMessages. AFI flattens nested keys with dot notation. Use the Capture Sample Payload flow on a real chat to learn what’s available.