How to Use the Official BounceBan n8n Node

This guide will walk you through installing and configuring the BounceBan node within your n8n workflows to verify single email addresses.

Update:

BounceBan is now an official N8N node, and you can skip to step 2 to use it within n8n directly.

Note: You will need admin permissions for your n8n instance to complete this step. 

1. Navigate to your n8n Settings.

2. Go to Community nodes.

3. Click Install.

4. In the npm Package Name field, enter: n8n-nodes-bounceban

5. Check the confirmation box below the package name to confirm you understand the risks of installing a community node.

6. Click the Install button.

Once the node is installed, you can add it to any workflow.

1. Add the Node: Go to your workflow canvas and click the + sign to add a new action. Search for "BounceBan" and select the "Verify a single email address" action.

2. Configure Credentials:

• In the node's settings panel, find the "Credential to connect with" field.

• Select "Create new credential" from the dropdown.

• A new window will open. Enter your BounceBan API Key in the required field. (You can get your key from your BounceBan API Settings).

• Click the Save button.

3. Choose the Email Address:

• Find the "Email Address" field in the node's settings.

• Drag the email address output from your previous node (e.g., from a trigger or another step) and map it to this field.

4. Test the Integration:

• Click "Test step" (or "Execute step") in the n8n interface.

• You should see the verification result from BounceBan returned in the node's output. You can now use this data in the subsequent steps of your workflow.

FAQ

1. How long does the email verification process take? Most verifications are completed within a few seconds. However, some emails—specifically those protected by greylisting or advanced security measures—may take up to 10 minutes to verify. Unlike other services that might return an "Unknown" result immediately to save time, BounceBan takes the necessary time to ensure the highest accuracy.

2. If a result isn't returned immediately, do I need to set up a separate API call to check the status? No. The n8n node is designed to handle this automatically. It will manage the waiting period and polling for you, ensuring you receive the final result without needing to build complex loop logic or separate API calls.

3. Which processing mode should I choose (Sequential vs. Concurrent)?

• Verify Email Sequentially (default): Use this default mode if your trigger sends data to BounceBan one item at a time (e.g., a webhook trigger).

• Verify Email in Batch (Concurrent): If your trigger processes multiple emails at once (e.g., a Google Sheets trigger reading rows), we highly recommend this mode. It submits requests to BounceBan concurrently rather than waiting for one verification to finish before starting the next, resulting in significantly faster processing speeds.

4. How are credits calculated when using the n8n node? The pricing is identical to using our Web App or direct APIs. Each successful verification costs 1 credit. There are no additional fees for using the n8n integration.

5. Am I charged for repeated verifications of the same email? If you resubmit the same email address for verification via the node within 30 minutes of the initial submission, no credits will be deducted. This ensures you are not charged twice if you need to re-run a workflow shortly after the first attempt.