Email Verification in Workflows
Validate contact email addresses before sending — improve deliverability, reduce bounce rates, and protect your sender reputation.
The Email Verification action in Workflow ensures a contact's email address is valid before continuing with email-related actions. This guide walks through how it works, how to set it up, and how to branch your workflow based on the result.
What Does Email Verification Do?
When a contact reaches the Email Verification action in a workflow, the system checks whether the contact's email address is valid and safe to use for sending emails.
This helps prevent:
- Sending emails to invalid addresses
- High bounce rates
- Poor sender reputation
- Deliverability issues
Prerequisites
Email Verification will run only if the following conditions are met:
The feature must be enabled for the specific sub-account before it can be used inside workflows.
If the contact is excluded from verification, the Email Verification action will be skipped.
Step-by-Step: Add the Email Verification Action
Email verification actions help you ensure that only valid email addresses progress through your workflow. This protects your sender reputation, reduces bounce rates, and makes your email campaigns more effective. Here's how to set up and use this feature.
Click the plus (+) icon in your workflow builder to add a new action.
Search for Email Verification in the action list and add it to your workflow.
Make sure Email Verification is enabled for your sub-account. If it's not active, the action will be skipped.
Confirm that the contact you want to verify isn't excluded from email verification. Contacts can be excluded in their details, so make sure that's not the case for anyone you want checked.
When a contact is added to the workflow, the Email Verification action checks if the contact's email is valid. If so, the workflow continues to the next steps; if not, the process is skipped for that contact.
If email verification fails (for example, the email is invalid, excluded, or the feature is disabled), the workflow will skip over the next steps for that contact.
Using Email Verification Results in Conditions
Branch your workflow based on whether an email is valid or not — this lets you send emails only to real contacts and take action for invalid ones.
Add a Condition action immediately after your Email Verification action.
Use the is verified value from the email verification check as your condition. Set one branch for when it's true (valid) and another for when it's false (invalid).
Set up actions on each branch. For example, send emails to valid contacts, and either mark or suppress contacts with invalid emails.
Add notes or take other actions to track which contacts are valid or invalid during your testing.
Test your workflow with both valid and invalid contacts. Use the Execution History to confirm if emails were classified and processed correctly.
If a contact is on the excluded list for verification or if email verification is disabled at the sub-account level, those cases will also be handled automatically by the workflow logic.
Best Practice Recommendation
A recommended workflow setup is:
This creates a safer and more reliable email automation process that protects your sender reputation over time.
Summary
The Email Verification action helps improve workflow efficiency by validating email addresses before sending emails.
By combining it with the isEmailVerified condition, you can create smarter workflows that:
- Send emails only to valid contacts
- Avoid unnecessary bounces
- Protect sender reputation
- Automatically handle invalid contacts
This ensures better deliverability and cleaner contact management across your sub-account.
Frequently Asked Questions
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article