ACTION_ID: person_work_email_verification_by_allegrow
NAME: Allegrow: Email Verification
CATEGORY: enrich
CREDITS: 0.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 Allegrow returned for the email.

  How to use the value downstream:
    - "safe" (Safe)
        Valid and safe to send to. Includes both catch-all and
        non-catch-all addresses that pass Allegrow's validation.
        Filter to this if you want strict deliverability.
    - "block_bounce_risk" (Block Bounce Risk — Invalid)
        Will likely bounce if emailed. Should not be sent to.
    - "dead_email" (Dead Email — Invalid)
        The mailbox does not exist, though it may not bounce
        immediately due to server catch-all settings. Should not
        be sent to.
    - "do_not_mail_abuse" (Do Not Mail / Abuse)
        Valid mailbox, but carries a high risk of producing spam
        reports. Should not be sent to.
    - "some_risk" (Some Risk — Inconclusive)
        The address shows signs that warrant caution. Recommended
        to re-run verification after 30 days before deciding
        whether to send.
    - "spamtrap" (Spamtrap)
        Valid email, but identified as a high-risk spam trap.
        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 == "safe"` for strict
  deliverability. Treat any other value as filtered out.
- Allegrow surfaces extra risk classes (`spamtrap`,
  `do_not_mail_abuse`, `some_risk`) that simpler verifiers don't —
  useful when sender reputation is the priority.

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

Pattern: person_work_email_waterfall -> person_work_email_verification_by_allegrow -> outreach.

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

Use person_work_email_verification_by_allegrow for Allegrow-grade email validation.

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

Need a different verifier
  -> person_work_email_verification_by_zerobounce,
     person_work_email_verification_by_neverbounce, person_work_email_verification_by_million_verifier
     (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