ACTION_ID: person_work_email_verification_by_neverbounce
NAME: NeverBounce: Email Verification
CATEGORY: Person Enrichment
CREDITS: 1

Verify email validity.

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

  How to use the value downstream:
    - "valid" (Safe)
        Confirmed as a real email address that is currently
        accepting mail. Filter to this if you want strict
        deliverability.
    - "invalid" (Don't Send)
        Verified as a bad, non-existent, or inactive address.
        Sending here will cause bounces. Should not be sent to.
    - "catchall" (Risky)
        The domain is configured to accept all mail, regardless
        of whether the specific mailbox exists, making it
        impossible to verify definitively. Include if you want
        broader reach and accept the trade-off.
    - "disposable" (Don't Send)
        Temporary, short-term email addresses (e.g. Mailinator)
        often used to avoid giving a real personal address.
        Should not be sent to.
    - "unknown" (Conditional)
        The server did not provide a definitive answer — usually
        due to technical issues or high-security, low-reputation
        mail servers. Typically safe to send if you have a
        high-reputation dedicated IP; risky otherwise.

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 == "valid"` for strict
  deliverability. Treat `"unknown"` as conditional — safe to send
  only from a high-reputation IP.
- 1 credit per check — pricier than Allegrow / MillionVerifier
  (0.1 each). Reach for NeverBounce when you specifically want
  NeverBounce's classification.

5. WHERE IT FITS IN A WORKFLOW

Pattern: person_work_email_waterfall -> person_work_email_verification_by_neverbounce -> outreach.

6. WHEN TO USE

Use person_work_email_verification_by_neverbounce for NeverBounce email validation.

7. WHEN NOT TO USE

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

Last updated: 2026-04-30.