What Email Verification Does
When a contact reaches the Email Verification action, Kyrios checks whether the contact’s email address is valid and safe to email.
This helps prevent:
Invalid email sends
High bounce rates
Poor sender reputation
Deliverability issues
Prerequisites
Email Verification Must Be Enabled
Email Verification must be enabled for the account before the workflow action can run.
Contact Must Not Be Excluded
If a contact is excluded from verification, the Email Verification action will be skipped.
How to Add Email Verification to a Workflow
Step 1: Open Workflow Builder
Click the + icon in the workflow builder to add a new action.
Step 2: Search for Email Verification
Search for Email Verification in the workflow action list.
Step 3: Select Email Verification
Select the Email Verification action from the list.
Step 4: Save the Email Verification Action
Save the action after adding it to the workflow.
Step 5: Confirm the Action Was Added
Confirm that the Email Verification step appears inside the workflow.
How to Use Verification Results in Conditions
Use a Condition step after Email Verification to decide what happens next.
Recommended structure:
Email Verification → Condition Check → Action Based on Result
Step 1: Add a Condition After Email Verification
Add a Condition step immediately after the Email Verification action.
Step 2: Select the Verification Field
Choose isEmailVerified as the condition field.
Step 3: Configure True and False Branches
Set the condition so the workflow separates valid and invalid emails.
True = email is verified
False = email is not verified
Step 4: Add Actions to Each Branch
Add the correct action under each branch.
Example:
True → Send Email
False → Mark as DND or add a cleanup tag
Step 5: Add Notes or Tracking Actions
Use notes, tags, or internal tracking actions to record verification results during testing.
Testing Email Verification
Use Execution History to confirm that contacts are verified and routed correctly.
Check:
Whether the Email Verification action ran
Whether the contact was verified
Which branch the contact followed
Whether the correct follow-up action ran
Best Practice Recommendation
Use this workflow structure:
Email Verification
Condition using isEmailVerified
Action based on result
Example:
Verified = send email
Not verified = mark as DND
This protects sender reputation and keeps email automation cleaner.
Common Issues and Fixes
Email Verification Is Skipped
Check that Email Verification is enabled for the account and that the contact is not excluded from verification.
Condition Does Not Work
Make sure the Condition uses the isEmailVerified field and has separate true and false paths.
Emails Are Still Bouncing
Place Email Verification before any email-sending action in the workflow.
FAQ
Does Email Verification cost extra?
Charges may apply depending on your plan and account settings.
What happens if Email Verification is disabled?
The Email Verification action is skipped.
Can I use isEmailVerified inside a Condition?
Yes. Use isEmailVerified to branch the workflow based on email validity.
What does Email Verification check?
It checks email format, domain validity, mailbox existence, and risky email types.
Should I mark invalid emails as DND?
Yes. Marking invalid emails as DND helps prevent future failed sends.
Does Email Verification work with all workflow triggers?
Yes. It can be used in any workflow where the contact has an email address.
Will this improve deliverability?
Yes. Reducing invalid sends helps lower bounce rates and protect sender reputation.