StopBouncingEmail Verification for Zapier
Add real-time email verification to any Zapier workflow using Webhooks by Zapier and the StopBouncing REST API. Validate leads from form submissions, CRM updates, and spreadsheet imports — before invalid addresses reach your marketing tools.
How to Add Email Verification to a Zap
Uses Webhooks by Zapier (Professional plan or higher) or Code by Zapier.
Create a StopBouncing API key
In the StopBouncing dashboard, go to API Keys and create a new key. Copy the key — you will use it in your Zapier action configuration.
Add a Webhooks by Zapier action
In your Zap, after the trigger (form submission, CRM lead, spreadsheet row), add a Webhooks by Zapier action and choose the GET method. This is available on Zapier Professional and higher plans.
Configure the webhook call
Set the URL to the StopBouncing API endpoint with the email address as a query parameter (mapped from your trigger). Under 'Headers', add an Authorization header with the value 'Bearer YOUR_API_KEY'. Set the response type to JSON.
Add a Filter or Path step
After the Webhooks action, add a Zapier Filter step that checks the 'status' field from the StopBouncing response. Filter to continue only when status equals 'valid'. Or use Zapier Paths to route valid, invalid, and unknown addresses to different downstream apps.
Zapier Configuration Reference
Webhooks by Zapier — GET action: URL: https://www.stopbouncing.com/api/v1/verify Query string params: email → map from your trigger step Headers: Authorization → Bearer YOUR_API_KEY Response (parsed JSON): status → "valid" / "invalid" / "unknown" / "disposable" credits_remaining → your remaining credit balance email → the verified address Filter step: Only continue if: status (Text) Exactly matches valid
Zapier Email Verification Use Cases
Verify Typeform or Jotform submissions
Trigger a Zap on new form submissions. Verify the email before passing the lead to Salesforce, HubSpot, Mailchimp, or any other downstream app. Invalid and disposable addresses are filtered out before they contaminate your CRM.
Validate leads before CRM entry
For any Zap that creates CRM contacts, add a Webhooks verification step before the CRM action. Only valid email addresses get added as new contacts. This keeps your CRM clean and prevents bounced emails from damaging your sender reputation.
Google Sheets lead processing
When a new row is added to a Google Sheet (from a manual import or another Zap), verify the email address and write the verification result ('Valid', 'Invalid', 'Catch-All') back to a column in the sheet using the Google Sheets action.
Protect email marketing subscriptions
Before subscribing a contact to Mailchimp, Klaviyo, or any other email marketing platform via Zapier, verify their address first. This prevents invalid and disposable addresses from inflating your subscriber count and triggering bounce rate warnings.
Frequently Asked Questions
Is there a native Zapier integration for StopBouncing?
There is no dedicated StopBouncing app in the Zapier marketplace. The Webhooks by Zapier action (available on Professional and higher Zapier plans) provides access to any REST API including StopBouncing. A GET request with the email and API key returns the verification result as JSON that can be used in downstream Zap steps.
What Zapier plan do I need for the Webhooks action?
The Webhooks by Zapier action requires a Zapier Professional plan or higher. If you are on a Starter plan, consider using Zapier's Code by Zapier action (JavaScript) to make the HTTP request programmatically — this requires writing a small fetch() call but is available at lower Zapier tiers.
How do I use Code by Zapier instead of Webhooks?
In Zapier, add a Code by Zapier action with JavaScript. Use the fetch() API to call the StopBouncing endpoint: const res = await fetch('https://www.stopbouncing.com/api/v1/verify?email=' + inputData.email, { headers: { Authorization: 'Bearer ' + inputData.apiKey } }); const data = await res.json(); output = { status: data.status, credits_remaining: data.credits_remaining }; Then use the output.status field in downstream Zap steps.
Can I use Paths in Zapier to route valid vs invalid emails?
Yes. Add a Zapier Paths step after the Webhooks verification action. In Path A (for valid addresses), set the condition to 'status exactly matches valid'. In Path B (for invalid), set the condition to 'status exactly matches invalid'. Add a third path for 'unknown' (catch-all or unverifiable) if your use case requires separate handling. Each path then routes to the appropriate downstream app.
Add email verification to your Zapier workflows
No subscription. Pay per verification. Credits never expire.
Get started freeFrom €0.0006 per verification · 100 free credits on signup · Full API documentation