ACTION_ID: person_verified_work_email_waterfall NAME: Find Verified Work Email CATEGORY: Person Enrichment CREDITS: 0.2-37.3 varies by finders and verifiers Find a person's work email and confirm it with a chain of email verifiers before returning it. Takes full_name + company_domain (best) or a LinkedIn uniform resource locator (URL). Only an email that a verifier confirms as good is returned, unless the verifier list is emptied (see email_verifiers). 1. INPUTS full_name (string, optional) - Full Name The prospect's full name. A single string, or composed inline from two upstream fields, for example "{{input.first_name}} {{input.last_name}}". company_domain (url, optional) - Company Domain The prospect's company domain (for example "acme.com"), usually from an upstream output. This is what pins the resolved email to the intended company, unless linkedin_url is passed too (see KEY NOTES). linkedin_url (url, optional) - LinkedIn URL LinkedIn URL of the prospect. Must be a flagship LinkedIn URL; see KEY NOTES. email_finders (stepDownSearch, optional) - Email Finders The ordered waterfall of email finders. It offers the same providers as the email_providers field of person_work_email_waterfall; the default order below is the current one for this action. Resolve the live set rather than hard-coding it: POST .../actions/{action_instance_id}/options/email_finders (body: {}) Default order (orientation only; resolve the options endpoint for the live list): hunter, leadmagic, prospeo, Wiza, datagma, apollo, findymail, Lightning, DataSync, Kitt AI Floqer credits per finder that returns an email: hunter 1, leadmagic 1, prospeo 1, Wiza 1, datagma 1, apollo 1, findymail 1 per search mode, Lightning 0.1, DataSync 0.1, Kitt AI 0.5. FullEnrich, Moltsets, BetterEnrich and Anymail Finder are selectable but not pre-selected, and run only on the user's own application programming interface (API) key (`requires_own_key: true` in the options). Snov is not offered. Which inputs each finder searches with: domain + name only: hunter, leadmagic, datagma, DataSync LinkedIn URL only: Wiza, Lightning either (uses whichever prospeo, apollo, BetterEnrich, Anymail Finder is passed, or both): both, one per search findymail (domain + name first, then the mode: LinkedIn URL) email_verifiers (stepDownSearch, optional) - Email Verifiers The ordered chain of verifiers that checks every email a finder returns. Resolve the live set the same way: POST .../actions/{action_instance_id}/options/email_verifiers (body: {}) All seven are on by default, in this order, with the Floqer credits each check costs: ZeroBounce 0.5 credits per check MillionVerifier 0.1 credits per check NeverBounce 1 credit per check Allegrow 0.1 credits per check LeadMagic 0.25 credits per check BounceBan 0.5 credits per check Kitt AI 0.15 credits per check ⚠ ZeroBounce, first by default, can answer valid for a mailbox that does not exist at some catch-all domains, and a good answer ends the check (see person_work_email_verification_by_zerobounce.txt). Names are resolved per field: the verifier named LeadMagic is a different entry from the leadmagic finder in email_finders. Use the `value` the options endpoint returns for each field. Passing an empty array clears the list: the action then runs no verifier and returns the first email a finder finds, unchecked, as person_work_email_waterfall does with no validator. Get Action reads a cleared list back as "". ⚠ Sending "" (for example, mirroring that readback onto another action) does not clear the list: the stored list is kept, so a new action keeps the default chain. Always send [] and check the GET. A list whose verifiers are all names the action no longer offers fails every row with a missing input error. Both lists are set with Configure Action, as arrays of names, in the order they run. The next finder runs only when the previous one returns no confirmed email; the next verifier is asked only when the previous one answers unsure. Omit an entry to skip it entirely. To run a finder or a verifier on the user's own API key instead of Floqer credits, pass `{"name": "", "use_own_key": true}` in place of the bare name. A bare name keeps the key state already stored for that entry, so a reorder never changes which key an entry runs on. To move an entry back to Floqer's key, pass `{"name": "", "use_own_key": false}`. With `use_own_key` off, the entry runs on Floqer's key and Floqer credits, even when a key for that provider is saved. FullEnrich and Moltsets are the exception: they have no Floqer-billed mode and run only on the user's own key, so Configure Action returns an `own_key_required` warning when either is configured without `use_own_key: true`. Full rules (key state, reorder-only updates, warnings) are in concepts.txt §8 "Waterfall provider fields". Required combinations: every input is optional, but at least one of full_name, company_domain or linkedin_url is needed, or the row fails with a missing input error. A useful row has one of: - full_name AND company_domain together (recommended), OR - linkedin_url. Passing all three unlocks every finder (highest raw coverage). 2. OUTPUTS work_email (type: email) - The verified work email of the contact. Only an email that a verifier confirmed as good is written here; with an empty email_verifiers list, the first email found. provider (type: string) - Provider The email finder that returned work_email, as named in the provider list (e.g. "Hunter"). Empty when no email is written. 3. HOW TO CONFIGURE Configure Action body: { "inputs": { "full_name": "{{input.full_name}}", "company_domain": "{{input.company_domain}}", "linkedin_url": "{{input.linkedin_url}}", "email_finders": ["hunter", "prospeo", "leadmagic"], "email_verifiers": [ "MillionVerifier", {"name": "ZeroBounce", "use_own_key": true}, "NeverBounce" ] } } Resolve both option endpoints first and use the returned values: POST .../actions/{action_instance_id}/options/email_finders (body: {}) POST .../actions/{action_instance_id}/options/email_verifiers (body: {}) Omitting email_finders or email_verifiers keeps the stored (default) list. Supply full_name + company_domain together (recommended), or linkedin_url. A row with none of the three inputs fails with a missing input error. 4. KEY NOTES - How finding and verifying work together. Finders run in email_finders order. Each email a finder returns is checked by the verifiers in email_verifiers order until one gives a definitive answer. Each answer is the verifier's own status value: - good: the email is returned and the row is done. ZeroBounce valid; MillionVerifier ok; NeverBounce valid; Allegrow safe; LeadMagic valid. - bad: the email is discarded and the next finder runs. ZeroBounce invalid, spamtrap, abuse, do_not_mail; MillionVerifier invalid, disposable; NeverBounce invalid, disposable; Allegrow block_bounce_risk, dead_email, do_not_mail_abuse, spamtrap; LeadMagic invalid. - unsure: the next verifier checks the same email. ZeroBounce catch-all, unknown; MillionVerifier catch-all, catch_all, unknown; NeverBounce catchall, unknown; Allegrow some_risk; LeadMagic catch_all, valid_catch_all, unknown. `error` (a failed check) is also recorded as unsure. Any status not listed here counts as unsure. When every verifier is unsure, the email is discarded and the next finder runs. Its email gets the full verifier chain again. - Repeat addresses are not checked again. When a later finder returns an address already checked earlier in the same row, the action moves straight to the next finder, with no verifier calls and no verifier charge. The finder that returned it is still charged. - No confirmed email means the row fails, in the same way person_work_email_waterfall fails when no finder returns an email. There is no fallback to an unconfirmed or catch-all address. A failed row can mean "no email found" or "emails found, none confirmed"; the cell detail view in the Floqer user interface lists every finder and every verifier answer. - When no verifier can check a found email (every check failed), the row stops with an error and later finders do not run. The finder that found the email keeps its charge; the failed checks are not charged. When the checks failed because the 200-second limit below ran out, the error is PROVIDER.VERIFIERS_TIMED_OUT ("The email verifiers did not answer within 200 seconds. Run the row again later."); otherwise it is PROVIDER.ALL_VERIFIERS_FAILED. - Out of credits at any step (finder or verifier) stops the row with the standard out-of-credits status. A member who reaches the member credit quota stops the row the same way, with the quotaLimitReached status instead. Finders and verifier checks already charged for the row keep their charge. - Credits. Each row is charged: - the finder cost for every finder that returns an email, even when that email is later rejected (a finder that finds nothing or fails is refunded), plus - the cost of every verifier check that ran. A verifier answer served from cache is not charged. MillionVerifier refunds a catch-all answer. A check that fails (an outage, a rate limit, a rejected key, or an Allegrow check still pending after its status polls) is refunded, and the next verifier is asked. The verifiers for one found email have 200 seconds in all: a verifier still running then counts as a failed check, shown as "Timed out" in the cell detail view, and the verifiers after it are not asked or charged. A verifier is not called, and not charged, when less than about one second of the limit is left. When no verifier answered before the limit, the row stops with the timeout error described above and later finders do not run. A verifier set to use_own_key with no saved key runs on Floqer's key and is charged Floqer credits, as a finder is. A verifier whose pinned key was since deleted, or whose saved-key lookup fails, is recorded as error, is not charged, and the next verifier is asked. The CREDITS header range bounds the default finder and verifier lists: - Low end 0.2: one 0.1-credit finder hit (Lightning or DataSync) confirmed by a 0.1-credit verifier (MillionVerifier or Allegrow), for example after a refunded ZeroBounce check. With ZeroBounce answering first (uncached), the cheapest confirmed row is 0.6. With email_verifiers emptied, the row can cost 0.1. Cached answers can lower any of these. - High end 37.3: all ten default finders return an email (7.7 credits), findymail in both of its search modes (1 more), and each of those eleven emails is a new address that every one of the seven verifiers (0.5 + 0.1 + 1 + 0.1 + 0.25 + 0.5 + 0.15 = 2.6 credits) answers unsure: 8.7 + 11 x 2.6 = 37.3. Adding an own-key finder (FullEnrich, Moltsets, BetterEnrich, Anymail Finder) raises the ceiling by up to 2.6 credits each for the verifier chain. Removing verifiers lowers it. Ordering the cheap verifiers first lowers the typical cost, not the ceiling: at the ceiling every verifier answers unsure, so all of them are charged in any order. An entry that runs on a key the user saved does not spend Floqer credits; an entry set to use_own_key with no key saved runs on Floqer credits. - The LinkedIn URL must be the flagship form, linkedin.com/in/. Sales Navigator URLs and the encrypted member identifier (ID) form (linkedin.com/in/ACoAA...) are not accepted. Convert first with enrich_person_linkedin_profile and wire its `person_linkedin_url` output into linkedin_url (the scrape has no output named `linkedin_url`; referencing it resolves empty). With full_name + company_domain also passed, a non-flagship URL silently drops the LinkedIn-only finders: lower coverage, no error. Passed alone, it leaves no finder that can use it and the row fails. - The domain + name path is only as accurate as the company_domain passed. A wrong upstream domain yields a verified email at the wrong company: verification confirms the mailbox accepts mail, not that it belongs to the intended person. - ⚠ With linkedin_url passed, a finder can return an address at a domain other than company_domain: Wiza, Lightning and findymail in its LinkedIn search mode always; prospeo even when company_domain is passed too (given name, company_domain and LinkedIn URL, it returned the person's address at another organization); apollo, BetterEnrich and Anymail Finder when company_domain is not passed. Verification still marks it good, because a verifier confirms only that the mailbox accepts mail. For a strict match to company_domain, omit linkedin_url, and gate downstream steps on a formula that compares the part of work_email after "@" with company_domain. - The action emits only `work_email`. The deciding verifier and its answer are visible in the cell detail view, not as an output field. To keep a verification status on the row, set email_verifiers to [] and add a standalone verifier action on work_email downstream; it outputs `email_verification_status`. - API metadata on POST /actions/add reports `required: true` for full_name, linkedin_url and company_domain. That is stricter than the real rule: the runtime accepts the at-least-one-of pattern in §1. Follow the §1 inputs section, not the schema metadata. 5. WHERE IT FITS IN A WORKFLOW Pattern: enrich_person_linkedin_profile -> person_verified_work_email_waterfall -> outreach. It replaces the legacy person_work_email_waterfall -> standalone verifier -> filter chain. No separate verifier step is needed. 6. WHEN TO USE Use whenever a workflow needs a prospect's work email. This is the work email action; the legacy person_work_email_waterfall is not available for new nodes. A catch-all or unknown answer from one verifier is passed to the next verifier instead of ending the search. 7. WHEN NOT TO USE Need any work email, unchecked -> this action with email_verifiers set to [] (see §1) Already have the email and only need a verification status on the row -> action-detail/person_work_email_verification_by_zerobounce.txt -> action-detail/person_work_email_verification_by_million_verifier.txt -> action-detail/person_work_email_verification_by_neverbounce.txt -> action-detail/person_work_email_verification_by_allegrow.txt Need a personal email -> action-detail/personal_email_by_linkedin_url_waterfall.txt Need a phone number -> action-detail/personal_phone_number_by_linkedin_url_waterfall.txt Last updated: 2026-11-15.