ACTION_ID: person_work_email_verification_by_million_verifier
NAME: Million Verifier: Email Verification
CATEGORY: Person Enrichment
CREDITS: 0.1

Email Verification.

1. INPUTS

email (type: email, required)
  The email address to verify.

2. OUTPUTS

email_verification_status (type: string) — Email Verification Status. Indicates the
  deliverability classification Million Verifier returned for the
  email.

  How to use the value downstream:
    - "ok" (Valid)
        The email address exists, is active, and is safe to send to.
        Generally covered by Million Verifier's 100% money-back
        guarantee. Filter to this if you want strict deliverability.
    - "catch_all" (Risky)
        The server accepts all emails sent to it, regardless of
        whether the specific mailbox exists. Risky — often indicates
        a low-quality or inactive user. Include if you want broader
        reach and accept some sends may land in a generic inbox.
    - "unknown" (Risky)
        The system cannot determine if the address is valid or
        invalid, often due to server timeouts or security settings.
        Treat with caution.
    - "disposable" (Bad)
        Temporary email addresses (used for short-term access) and
        likely to be inactive within minutes. Should not be sent to.
    - "invalid" (Bad)
        The email address does not exist or is inactive, with a high
        likelihood of bouncing. Should not be sent to.

3. HOW TO CONFIGURE

Configure Action body:

{
  "inputs": {
    "email": "{{person_work_email_waterfall_1.work_email}}"
  }
}

Pass the email to verify as `email` — typically `{{ref}}` to an
upstream `person_work_email_waterfall` output, or `{{input.email}}`
if the email is already on the row.

4. KEY NOTES

- Filter on `email_verification_status == "ok"` for strict
  deliverability. Use `"catch_all"` only when you accept some sends
  may land in a generic mailbox.
- Cheapest of the four verifiers (0.1 credits) — the right default
  for high-volume verification when sender reputation is not
  critical.

5. WHERE IT FITS IN A WORKFLOW

Pattern: person_work_email_waterfall -> person_work_email_verification_by_million_verifier -> outreach.

6. WHEN TO USE

Use person_work_email_verification_by_million_verifier for MillionVerifier email
validation.

7. WHEN NOT TO USE

Need a different verifier
  -> person_work_email_verification_by_allegrow, person_work_email_verification_by_zerobounce,
     person_work_email_verification_by_neverbounce
     (https://floqer.com/docs/action-detail/<action_id>.txt)

Last updated: 2026-04-30.