The Email Address Validation step checks whether an email address looks real and deliverable before you send to it. It is a best-effort check that catches clearly bad addresses and flags risky ones, which lowers your bounce rate and protects your sending reputation. A passing address is a strong signal, not a guarantee of delivery.

• Validate addresses from a form, CSV, or scraped page before adding them to an outreach list
• Filter out invalid and undeliverable addresses ahead of a Send Email step
• Flag disposable or role-based addresses so you can route or exclude them
• Clean a contact list as part of a scheduled maintenance workflow

Provide the email address, either a static value or a reference like {{stepId.email}}. The step checks it and returns the fields below. Most workflows branch on the valid field with a Condition step. If the check cannot complete, the step reports success as false instead of failing the run, so a temporary outage does not stop the workflow.

• valid: True or false for "safe to send". This is the field most workflows branch on.
• result: The detailed verdict, one of these values:
  • valid: The mailbox looks like it exists and can receive mail.
  • invalid: The address is malformed, or its domain or mailbox does not exist. Do not send to it.
  • catch-all: The domain accepts mail for any address, so a specific mailbox cannot be confirmed. It might deliver, it might bounce.
  • risky: The address may deliver but carries a higher chance of bouncing or low engagement, for example a catch-all or role address.
  • unknown: The mail server did not give a clear answer, so deliverability could not be determined.
• reason: A short, human-readable explanation of the result.
• disposable: True when the address comes from a throwaway, temporary inbox service.
• role: True when the address is role-based: it reaches a function or team (like info@ or support@) rather than a named person.
• success: Whether the check ran at all. Separate from valid: success tells you the address was checked, valid tells you the outcome.
• error: A message describing what went wrong when the check could not complete. Empty when it succeeds.

Is email validation 100% accurate?

No. It is a best-effort check, not a guarantee. It reliably catches malformed addresses and dead domains and flags risky ones, but some mail servers accept every address (catch-all) or give no clear answer (unknown), so a specific mailbox cannot always be confirmed. An address marked valid can still bounce. The goal is to reduce bounces and protect your sending reputation, not to promise delivery.

What happens if validation cannot run?

The step reports success as false and marks the address as not valid, and the workflow continues instead of failing the run. That way a temporary outage never blocks a workflow. Branch on the success field if you want to retry or handle those addresses differently.