When chat session ends in Tawk.to, check if the email is valid with Email List Validation and create a user in WordPress
When a Tawk.to chat ends, the visitor’s email is checked with Email List Validation and a WordPress user is created for them, so people you talk to in live chat can get an account on your site.
tawk.to
Email List Validation
WordPress3 steps Setup ~5 min Used on 1.7k sites Free to import
What this workflow does
Live chat is often the first real conversation with a prospect or customer. If you want those visitors to end up with an account on your WordPress site, for a portal, a free trial area or a support login, this workflow handles it once the chat is over, with an email check along the way.
The Tawk.to trigger, Chat End, fires when a chat session ends. The chat's visitor details become available to map, including an email when the visitor gave one. FlowMattic sends that address to Email List Validation with Verify Single Email, and the result becomes data you can map. The last step, WordPress New User, creates an account on your site from the visitor's details.
As imported, the check doesn't decide anything: every ended chat goes on to the New User step whatever the verification says. Add a Filter between the two to create accounts only for addresses that pass. Chats where the visitor left no email can't produce a user, and Task History shows the error for those runs. For an email that is already registered, WordPress creates no second account and the step returns the existing user's ID.
Turning trial enquiries into accounts
Visitors ask about your product in Tawk.to and leave their email. After the chat, they get a WordPress account for your trial area, with the address checked first.
Support portal sign-up
Customers who reach you through chat get a WordPress login for your help center, so their next request can go through the portal.
Keeping a record of address quality
Even before you add a Filter, Task History shows each chat visitor's verification result next to the account created, which shows how many chat emails are mistyped.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
tawk.to Chat EndFires when a chat session ends in Tawk.to. The visitor details from the chat are passed on, including an email address if the visitor provided one.
- Email List Validation Verify Single Email
Checks the visitor's email address with Email List Validation. Map the email from the Tawk.to chat into the step. The verification result can be used by later steps.
- WordPress New User
Creates a WordPress user on your site from the chat visitor's details. Map the email and name into the step, and use a test chat to confirm the account is set up as you want.
What you need
- FlowMatticCore
- Tawk.to AccountAccount
- Email List Validation AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Add a Filter between Email List Validation and WordPress that continues only when the result shows a valid address. Without it, every chat with an email gets an account.
- Turn on a pre-chat form in Tawk.to that asks for an email, if you haven't. The trigger can only pass on an address the visitor actually gave, and New User needs one.
- Add a Filter between the Tawk.to trigger and the Email List Validation step that stops chats with no email, so they don't use a verification check or leave a New User error in Task History.
Questions about this workflow
Does Email List Validation stop invalid addresses from becoming WordPress users?
Not as imported. The result is passed on, but nothing checks it, so the New User step runs for every chat. Add a Filter on the result between the Email List Validation step and the WordPress step to make the check count.
What happens if a Tawk.to visitor already has a WordPress account?
WordPress won't create a second user with the same email. The New User step returns the ID of the account the visitor already has, so they keep the login they had, and Task History shows that ID.
What if the Tawk.to visitor never gave an email?
Then there's no address to verify or to create the account with, and the later steps return errors for that chat. A pre-chat form that asks for an email avoids this.
Do I need an Email List Validation account?
Yes. The verification runs through your Email List Validation account, which you connect when you import the workflow.
More Support workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted