This Zap: triggers on a new lead → verifies the email → branches on the result → routes to the right destination.
Step 1: Trigger
Choose whatever produces new leads in your stack — common triggers: New Row in Google Sheets, New Lead in Facebook Lead Ads, New Submission in Typeform.
Step 2: Verify the email
Add a Webhooks by Zapier → POST step (or the RocketVerifier app’s “Verify Email” action if installed):
| Field | Value |
|---|---|
| URL | https://api.rocketverifier.com/v1/verify |
| Payload Type | json |
| Data | {"email": "<email from trigger step>"} |
| Headers | Authorization: Bearer YOUR_API_KEY |
Step 3: Filter on the result
Add a Filter by Zapier step after the verification call:
Only continue if...
data__status (Text) Exactly matches deliverable
Leads that pass continue to your CRM step; leads that don’t pass this filter simply stop here (or route to a second path — see Step 4).
Step 4 (optional): Route rejected leads to a review sheet instead of discarding them
Duplicate the Zap’s path using Zapier’s Paths feature: Path A continues if status = deliverable, Path B catches everything else and appends the lead (with its verification status and score) to a separate “Needs Review” Google Sheet rather than silently dropping it — people sometimes have real but catch-all or risky-scored addresses worth a human glance before discarding.
Step 5: Push to your CRM
On the “deliverable” path, add your CRM’s Create/Update Contact action (HubSpot, Salesforce, Pipedrive, etc.), mapping the original lead fields plus the verification score if your CRM has a custom field for it.
Testing with the sandbox before going live
Temporarily swap your production API key for a sandbox key (rv_test_...) in the Webhooks step and run the Zap manually (Zapier’s “Test trigger” + “Test action” buttons) against a sample lead with an @sandbox.rocketverifier.com email, to confirm the Filter and Paths logic behaves as expected before connecting it to live form submissions.