Email Verification Action in Sparkforge Workflows

The Email Verification action validates a contact's email address inside a workflow before any send action runs. It catches invalid addresses, catch-alls, disposables, and known spam traps so they don't damage your bounce rate or sender reputation.

What it checks

• Syntax and formatting
• Domain validity
• Mailbox existence
• Risky address types — catch-alls, disposables, spam traps

Prerequisites

• Email Verification must be enabled for the sub-account.
• The contact must not be on the verification exclusion list.

If either condition fails, the action is skipped and the workflow continues without verification.

Add the Email Verification action

1. In the Workflow Builder, click the + icon to add an action.
2. Search for Email Verification and add it.
3. Confirm Email Verification is enabled for the sub-account.
4. Confirm the contact isn't on the exclusion list.
5. When a contact reaches the action, Sparkforge checks the email and stores the result on the contact record.
6. If verification fails or is skipped, the next steps are bypassed for that contact.

Branch on the verification result

1. Add a Condition action immediately after Email Verification.
2. Use the isEmailVerified field as the condition.
3. Set the true branch to send the email.
4. Set the false branch to mark the contact as DND, tag for review, or move to a cleanup list.
5. Test with both valid and invalid contacts and check the Execution History to confirm classification.

Recommended pattern

Email Verification → Condition (isEmailVerified) → Action by branch. Verified contacts get the send. Unverified contacts get marked DND or routed to a cleanup tag. This protects sender reputation and improves inbox placement over time.