ACTION_ID: person_work_email_verification_by_bounceban NAME: BounceBan: Email Verification CATEGORY: Person Enrichment CREDITS: 0.5 (0 on your own BounceBan key) Verify whether an email is deliverable, including catch-all and gateway-protected emails. 1. INPUTS bounceban_api_key (type: boolean, optional) — BounceBan API key Whether to use a personal BounceBan API key for this run instead of Floqer's. Allowed values: true / false (default false). Set to true only if you've connected your own BounceBan account on the Floqer Connections page; with it on and no key connected, the row fails with a missing connection error. Runs on your own key are not charged Floqer credits. Accepted on Configure Action, but reading the action back leaves this field out. email (type: email, required) — Email The email address to verify. It is trimmed and lowercased before the check. A value that isn't shaped like an email fails the row before any charge. 2. OUTPUTS result (type: string) — Verification result. How to use the value downstream: - "deliverable" (Safe) Safe to send. Filter to this if you want strict deliverability. - "risky" (Conditional) May bounce. Check `score`; higher is better. - "undeliverable" (Don't Send) Will bounce. Should not be sent to. - "unknown" (Conditional) BounceBan could not determine a result. The row still succeeds, and this answer is not cached, so a later run asks BounceBan again. score (type: number) — Deliverability confidence from 0 to 100; higher is better. email (type: string) — The email that was verified, in lowercase. is_disposable (type: boolean) — Whether the email is on a disposable domain. is_accept_all (type: boolean) — Whether the domain accepts all emails (catch-all). is_role (type: boolean) — Whether the email is a role address (e.g. sales@). is_free (type: boolean) — Whether the email is on a free provider (e.g. gmail.com). smtp_provider (type: string) — Email provider of the domain (e.g. Google). Empty when BounceBan can't identify one. mx_records (type: raw_array) — The domain's MX records. Empty when the domain has none. verified_at (type: string) — When BounceBan verified the email. A cached answer keeps its original time. 3. HOW TO CONFIGURE Configure Action body: { "inputs": { "email": "{{person_work_email_waterfall_1.work_email}}", "bounceban_api_key": false } } 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. Leave `bounceban_api_key` false (or omit it) to run on Floqer's key; set it true to run on your own key. 4. KEY NOTES - Filter on `result == "deliverable"` for strict deliverability. Use `score` to decide on "risky". - 0.5 credits per check on Floqer's key, 0 on your own. Cached answers are free, and the cache is shared across keys. - BounceBan waits up to 30 seconds per check. A slower check fails the row with "BounceBan is still verifying this email. Run the row again in a minute." The check keeps running at BounceBan, so a rerun can pick up the answer. The failed try is refunded, so on Floqer's key the rerun that answers is the only charge. On your own key, BounceBan does not bill a rerun of the same email within 30 minutes. - On your own key, the row fails with a specific message when BounceBan rejects the key, the BounceBan account is out of credits, the key reached its quota, or BounceBan is rate limiting it. - A row that ends in an error produces no outputs, and its Floqer credits are refunded. 5. WHERE IT FITS IN A WORKFLOW Pattern: person_work_email_waterfall -> person_work_email_verification_by_bounceban -> outreach. 6. WHEN TO USE Use person_work_email_verification_by_bounceban for BounceBan email validation, including catch-all and gateway-protected emails, or when you want a 0-100 score alongside the result. 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_neverbounce, person_work_email_verification_by_zerobounce (https://floqer.com/docs/action-detail/.txt) Last updated: 2026-11-04.