feat(enrichment): add ZeroBounce, NeverBounce, and MillionVerifier email verification

[waleedlatif1]

Summary

• Add three email-verification integrations — ZeroBounce, NeverBounce, and MillionVerifier (tools, blocks, icons, hosted-key support, and BYOK wiring), mirroring the existing Findymail/Prospeo pattern
• Add an Email Verification table enrichment that runs a verifier waterfall (ZeroBounce → NeverBounce → MillionVerifier), surfacing a normalized status + deliverable
• These are Clay's most popular bounce/verification providers (ZeroBounce is Clay's default verifier) — closes the email-verification gap, a category Sim previously had nothing in

Type of Change

• New feature

Testing

Tested manually — tsc --noEmit clean (0 errors), Biome clean, 28/28 enrichment + hosting tests passing, api-validation gate passing. Each integration independently validated against the providers' live API docs (endpoints, auth params, status vocabularies, response fields, error handling).

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jun 8, 2026 9:31pm

[cursor]

PR Summary

Medium Risk
New third-party API integrations affect enrichment/table runs and hosted-key billing, but they follow existing enrichment/BYOK patterns without changing auth or core execution.

Overview
Adds ZeroBounce, NeverBounce, and MillionVerifier as first-class email-verification integrations: workflow blocks (verify + get credits), HTTP tools with normalized status/deliverable, hosted-key pricing/rate limits, workspace BYOK, docs, and catalog wiring.

Also introduces an Email Verification table enrichment that waterfalls those three verify tools (ZeroBounce → NeverBounce → MillionVerifier), skipping providers that return unknown so rows get a definitive verdict when possible.

^{Reviewed by Cursor Bugbot for commit ae83d18. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

This PR adds three email-verification integrations — ZeroBounce, NeverBounce, and MillionVerifier — each with verify-email and get-credits tools, corresponding block definitions, BYOK wiring, hosted-key support, icon assets, and documentation pages. It also introduces an Email Verification table enrichment that runs a provider waterfall (ZeroBounce → NeverBounce → MillionVerifier), surfacing a normalized status + deliverable field.

• Tools & hosting: Each provider follows the established Findymail/Prospeo pattern with user-only API-key visibility, .catch(() => ({})) guards on all response.json() calls, and envelope-level error detection (ZeroBounce and MillionVerifier return HTTP 200 with { error } on auth failure).
• Enrichment waterfall: mapOutput falls through to the next provider on unknown or missing status, accepting any other verdict (including spamtrap, abuse, do_not_mail, unverified) as definitive — consistent with the stated design.
• Registry & BYOK: All three providers are registered in the tool, block, and BYOK-key schemas, and their icons appear correctly in the workspace settings Enrichment section.

Confidence Score: 5/5

Safe to merge — all three providers follow the established tool/block/BYOK pattern, JSON-parse guards and envelope-error detection are consistent, and the enrichment waterfall logic is correctly designed.

All new tools correctly guard against non-JSON 200 responses, detect HTTP-200 error envelopes (ZeroBounce and MillionVerifier), and surface failures rather than silently succeeding with empty data. The enrichment waterfall falls through only on indeterminate verdicts and accepts all definitive statuses. BYOK wiring is complete across the Zod schema, type union, block registry, and workspace settings UI. No correctness issues were found.

No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/enrichments/email-verification/email-verification.ts	Email-verification enrichment waterfall; falls through on unknown or empty status across all three providers; MillionVerifier's unverified is correctly treated as a definitive verdict since it's the terminal provider.
apps/sim/tools/zerobounce/verify_email.ts	ZeroBounce verify-email tool; normalizes catch-all status, guards JSON parse on both error and success paths, checks the error envelope on 200 responses.
apps/sim/tools/zerobounce/get_credits.ts	ZeroBounce get-credits tool; correctly detects auth failure from the HTTP-200 error envelope, consistent with NeverBounce/MillionVerifier pattern.
apps/sim/tools/neverbounce/verify_email.ts	NeverBounce verify-email tool; uses STATUS_MAP for normalization, echoes back input email (API doesn't return it), correctly surfaces the data.status !== 'success' envelope error.
apps/sim/tools/millionverifier/verify_email.ts	MillionVerifier verify-email tool; STATUS_MAP handles the ok→valid rename and unverified status; error envelope checked consistently with get-credits pattern.
apps/sim/app/workspace/[workspaceId]/settings/components/byok/byok.tsx	Adds all three new providers to the PROVIDERS list and PROVIDER_SECTIONS.Enrichment ids array; BYOK UI wiring is complete.
apps/sim/lib/api/contracts/byok-keys.ts	Adds zerobounce, neverbounce, millionverifier to the Zod provider-id enum; matches tools/types.ts BYOKProviderId union.

Sequence Diagram

sequenceDiagram
    participant Table as Enrichment Table
    participant Runner as Waterfall Runner
    participant ZB as ZeroBounce
    participant NB as NeverBounce
    participant MV as MillionVerifier

    Table->>Runner: email-verification enrichment (email)
    Runner->>ZB: zerobounce_verify_email(email)
    alt "status != unknown"
        ZB-->>Runner: "{ status, deliverable }"
        Runner-->>Table: write result
    else "status == unknown or failure"
        ZB-->>Runner: null / unknown
        Runner->>NB: neverbounce_verify_email(email)
        alt "status != unknown"
            NB-->>Runner: "{ status, deliverable }"
            Runner-->>Table: write result
        else "status == unknown or failure"
            NB-->>Runner: null / unknown
            Runner->>MV: millionverifier_verify_email(email)
            alt "status != unknown"
                MV-->>Runner: "{ status, deliverable }"
                Runner-->>Table: write result
            else all unknown
                MV-->>Runner: null
                Runner-->>Table: no result (cell empty)
            end
        end
    end

Loading

_{Reviews (3): Last reviewed commit: "fix(byok): render new email-verify provi..." | Re-trigger Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit f62d59a. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit dcd4687. Configure here.}

[TheodoreSpeaks]

@greptile review

Addressed in latest pushes:

• BYOK providers missing from sections (Cursor): added zerobounce/neverbounce/millionverifier to the Enrichment PROVIDER_SECTIONS.ids so they render in the workspace BYOK settings UI.
• Merge with staging: resolved blocks/registry.ts against the BlockMeta refactor — moved tags off each new block's BlockConfig into {Service}BlockMeta exports and registered them in BLOCK_META_REGISTRY.
• Hosted rate limits: raised ZeroBounce + MillionVerifier per-workspace limits 60→1200 req/min (sized to upstream ceilings: ZeroBounce 80k/10s, MillionVerifier 160/sec). NeverBounce held at 60 pending its account-configured throttle.
• The two ZeroBounce 200-status P1s were already fixed in f62d59a.