ACTION_ID: person_work_email_verification_by_zerobounce
NAME: ZeroBounce: Email Verification
CATEGORY: enrich
CREDITS: 1

Verify email validity.

INDEX:
  1. Inputs
  2. Outputs
  3. How to configure
  4. Key notes
  5. Where it fits in a workflow
  6. When to use
  7. When not to use

================================================================================
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 ZeroBounce returned for the email.

  How to use the value downstream:
    - "safe"
        The only status that is guaranteed not to bounce. Filter to
        this if you want a strict deliverability bar — every email
        you send will reach an inbox.
    - "catch-all"
        The receiving domain accepts mail for any address, so the
        email will deliver, but ZeroBounce cannot confirm the
        mailbox actually belongs to the intended person. Include
        this if you want broader reach and accept that some sends
        may land at a generic catch-all inbox rather than the
        target prospect.
    - any other value (e.g. invalid, unknown, spamtrap, abuse,
      do_not_mail)
        Should not be sent to. Treat as filtered out for outreach.


================================================================================
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 == "safe"` for the strictest
  deliverability bar. `"catch-all"` is acceptable when reach
  matters more than mailbox-level confirmation.
- 1 credit per check. Highest-strictness option of the four
  verifiers — its `"safe"` class is the only ZeroBounce status
  guaranteed not to bounce.

================================================================================
5. WHERE IT FITS IN A WORKFLOW
================================================================================

Pattern: person_work_email_waterfall -> person_work_email_verification_by_zerobounce -> outreach.

================================================================================
6. WHEN TO USE
================================================================================

Use person_work_email_verification_by_zerobounce for ZeroBounce email validation.

================================================================================
7. WHEN NOT TO USE
================================================================================

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

================================================================================

This file is maintained manually. Last updated: 2026-04-30.
Full interactive reference: https://floqer.com/docs/reference
Action catalog: https://floqer.com/docs/action-catalog.txt