Workflows now include an Email Verification action that checks whether a contact's email address is valid, risky or invalid before the workflow sends anything. Put it ahead of your email steps and the bad addresses never receive a send, which keeps your bounce rate down and your sender reputation intact.

What does the action check?

It tests the address and returns one of three results: valid, risky or invalid. The workflow can then behave differently depending on which one comes back, so you are not treating a confirmed-good address the same as one that will almost certainly bounce.

How do I add it to a workflow?

Add it as a step of its own, before anything that sends an email. The result is then available to the steps that follow, so you can branch on it.

1. Open the workflow you want to protect.
2. Add the Verify Email action.
3. Place it before any email step.
4. Use the result to decide whether the workflow continues, branches or stops.

What should I do with each result?

Send to the valid ones, and route the rest somewhere useful rather than dropping them. A risky address is often worth a different approach, such as reaching out by SMS or WhatsApp instead.

• Valid, so let the workflow continue to the email step
• Risky, so branch to another channel or tag the contact for review
• Invalid, so stop the workflow and keep the send off your record

Why bother, if a bad address just bounces?

Because the bounce is the damage. Mailbox providers watch how many of your sends fail, and a run of bounces pushes your later emails towards spam folders, including the ones customers are waiting for. Verifying first means your list cleans itself as it runs, instead of you exporting it and checking it by hand.

You will find this as the Verify Email action in the action list inside the workflow builder.

This update was originally released in April 2026. Menu locations may have changed since.