StopBouncingEmail Verification for n8n
Add real-time email verification to any n8n workflow using the StopBouncing REST API. Validate leads at the point of capture, enrich CRM contacts, or run automated list cleaning pipelines — all without leaving n8n.
How to Connect StopBouncing to n8n
Uses n8n's HTTP Request node. Works with n8n Cloud, n8n Desktop, and self-hosted n8n.
Create a StopBouncing API key
In the StopBouncing dashboard, go to API Keys and create a key. Copy the key — you will add it to your n8n credentials.
Add an HTTP Request node in n8n
In your n8n workflow, add an HTTP Request node where you want to verify an email address. This can be after a form submission, CRM update, lead import, or any other trigger.
Configure the API request
Set the HTTP Request node Method to GET. Set the URL to the StopBouncing verification endpoint with the email as a query parameter. Under Authentication, choose 'Header Auth' and add an Authorization header with value 'Bearer YOUR_API_KEY'.
Branch on verification result
The API returns a JSON response with a 'status' field: 'valid' (deliverable), 'invalid' (does not exist), 'unknown' (catch-all or unverifiable), or 'disposable'. Add an IF node to route valid and invalid addresses to different branches in your workflow.
API Request and Response
GET https://www.stopbouncing.com/api/v1/verify?email={{$json.email}}
Authorization: Bearer YOUR_API_KEY
// Response
{
"email": "user@example.com",
"status": "valid",
"credits_remaining": 4999
}
// status values:
// "valid" → Mailbox confirmed — safe to send
// "invalid" → Address does not exist — remove from list
// "unknown" → Catch-all or unreachable — cannot confirm
// "disposable" → Temporary throwaway address — block or skipThe full API reference is available at stopbouncing.com/api-docs.
n8n Email Verification Use Cases
Real-time lead qualification
Connect a webhook trigger (from Typeform, Tally, or a custom form) to StopBouncing verification. Immediately classify each lead as valid or invalid before it enters your CRM or email sequence. Block invalid addresses from entering your database at all.
CRM data enrichment
Schedule a daily n8n workflow that reads contacts from your CRM, verifies their email addresses against the StopBouncing API, and updates a custom field with the verification status. Keep your CRM email data fresh without manual effort.
Bulk CSV pipeline
Use n8n's Read Binary File and Spreadsheet nodes to process a CSV export, loop through each row, verify each address via the API, and write the results to a new CSV. Automate the entire bulk verification workflow end-to-end.
Signup form protection
After a form submission, verify the submitted email address before confirming registration or triggering a welcome email. If the address is invalid or disposable, route the workflow to a rejection branch — preventing fake signups from entering your system.
Frequently Asked Questions
Is there a native n8n node for StopBouncing?
There is no dedicated n8n community node for StopBouncing. The HTTP Request node in n8n provides full access to the StopBouncing REST API — a GET request with the email address and your API key returns the verification result in JSON. This is straightforward to configure and works across all n8n deployment types (cloud, desktop, self-hosted).
How do I handle rate limits in an n8n loop?
The StopBouncing API allows up to 60 requests per minute per API key. If you are looping through a large email list in n8n, add a Wait node between iterations set to at least 1100ms to stay safely within the limit. For higher throughput, create additional API keys in the StopBouncing dashboard and cycle through them using an n8n expression — each key has its own 60/min quota.
Can I verify emails from a Google Sheets trigger in n8n?
Yes. Use the Google Sheets trigger node to detect new rows, then pipe each email address through an HTTP Request node calling the StopBouncing API. Write the verification result back to a 'Status' column in the sheet using the Google Sheets update node. This creates a fully automated email verification pipeline driven by a spreadsheet.
What do the verification status values mean?
The StopBouncing API returns a 'status' field with one of four values: 'valid' means the mailbox exists and is accepting mail; 'invalid' means the address does not exist and should be removed; 'unknown' means the result could not be confirmed — typically a catch-all domain or a provider blocking SMTP checks — never treat these as invalid; 'disposable' means a temporary throwaway address. The response also includes 'credits_remaining' so you can monitor usage in your workflow.
Add email verification to your n8n workflows
No subscription. Pay per verification. Credits never expire.
Get started freeFrom €0.0006 per verification · 100 free credits on signup · Full API documentation