StopBouncingEmail Verification for Make (Integromat)
Add real-time email verification to any Make scenario using the StopBouncing REST API. Validate leads at the point of entry, enrich contact databases, and automate list cleaning — without writing any code.
How to Use StopBouncing in Make
Uses Make's HTTP module. Available on all Make plans including Free.
Create a StopBouncing API key
In the StopBouncing dashboard, go to API Keys and generate a new key. Copy the key — you will use it in your Make HTTP module.
Add an HTTP module to your Make scenario
In your Make scenario, add an HTTP → Make a request module at the point where you want to verify an email address. This can follow any trigger — a form submission, a new CRM row, a spreadsheet update, or a webhook.
Configure the HTTP module
Set the URL to the StopBouncing verification endpoint with the email address as a query parameter. Set the Method to GET. Under Headers, add a header named 'Authorization' with the value 'Bearer YOUR_API_KEY'. Set Parse response to Yes.
Route on the verification result
After the HTTP module, add a Router and create branches based on the 'status' field in the JSON response. Route 'valid' addresses to your main flow — CRM import, confirmation email, etc. Route 'invalid' and 'disposable' addresses to a rejection or logging branch.
HTTP Module Configuration
URL: https://www.stopbouncing.com/api/v1/verify
Method: GET
Query parameters:
email: {{1.email}} ← your mapped email field
Headers:
Authorization: Bearer YOUR_API_KEY
Response (JSON):
{
"email": "user@example.com",
"status": "valid", // valid / invalid / unknown / disposable
"credits_remaining": 4999
}Full API reference at stopbouncing.com/api-docs.
Make Scenario Use Cases
Typeform or Tally form validation
Trigger a Make scenario when a form is submitted. Verify the submitted email before routing the response to your CRM, email platform, or Slack notification. Block invalid or disposable addresses from entering your tools.
Google Sheets email enrichment
Watch a Google Sheet for new rows. For each new row, verify the email address via StopBouncing and write the verification status back to a dedicated column. Build a fully automated email validation pipeline in a spreadsheet.
Airtable contact database cleaning
Schedule a Make scenario that reads Airtable records, verifies each email address, and updates an 'Email Status' field. Keep your Airtable contact base clean without manual effort.
Webhook lead qualification
Accept leads from any webhook source and immediately verify the email address before the lead enters your CRM or sales pipeline. Route qualified leads (valid email) to one path and unqualified leads (invalid or disposable) to a separate tracking or rejection path.
Frequently Asked Questions
Is there a native Make module for StopBouncing?
There is no dedicated Make marketplace module for StopBouncing. The HTTP → Make a request module in Make provides full access to the StopBouncing REST API. Configure a GET request to the verification endpoint with the email as a query parameter and your API key as a Bearer token in the Authorization header. The JSON response is straightforward to map in any Make scenario.
How do I handle rate limits when processing a large list in Make?
Make's iterator processes items sequentially by default. You can add a delay between iterations using Make's built-in delay tools, or process your list in a lower-frequency scheduled scenario rather than all at once. For high-volume processing, consider using the StopBouncing bulk CSV upload instead of per-address API calls.
Can I store my API key securely in Make?
Yes — use Make's custom connection or store the API key as a text variable in a scenario's variables. Avoid hardcoding the key directly in module configurations that are visible to scenario collaborators. For team environments, use Make's connection manager so the key is stored at the connection level, not the module level.
What Make plan do I need for the HTTP module?
The HTTP → Make a request module is available on all Make plans, including the free plan. The number of scenario operations you can run per month depends on your Make subscription tier — each HTTP request to the StopBouncing API consumes one Make operation.
Add email verification to your Make scenarios
No subscription. Pay per verification. Credits never expire.
Get started freeFrom €0.0006 per verification · 100 free credits on signup · Full API documentation