Resources · n8n integration

BounceBan n8n integrationAutomate BounceBan with n8n.

A dead email address costs more than the message it wastes. The BounceBan n8n integration brings one verification operation into n8n, backed by a single API credential, and it covers catch-all addresses, the ones that accept everything and tell a basic test nothing.

Community node This node is not shipped with n8n: it is a community package (n8n-nodes-bounceban) you install from Settings › Community nodes on a self-hosted instance. npm

Try the BounceBan integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the BounceBan n8n integration cover?

BounceBan checks whether an email address can actually receive mail, and its stated angle is catch-all addresses, the ones that accept everything and tell a basic test nothing. In n8n the check becomes a node with a single resource and a single operation, email.validateEmail, which takes one address and passes the verification result to whatever comes next in the workflow.

The first place it earns its keep is the signup form. A workflow picks up the new address, runs the verification, and only then appends the row to Google Sheets or fires the welcome message through Gmail. Bad addresses never reach the list, so the sending reputation stays where it was.

A second pattern runs on an existing file. A batch of prospects comes in, the node checks each address, and the workflow splits the output into a clean branch and a branch that needs a look. When a whole import turns out to be unusable, Stop and Error ends the run with a message instead of letting the rest of the nodes work on nothing.

The third one is a notification loop. Sales adds a contact, the address gets verified, and the verdict lands in a channel through Slack so the person who typed the address can fix it while the context is fresh. The Webhook URL field is worth knowing here: BounceBan can POST the verification result event to a URL of your choice, and a failed delivery is retried up to 2 more times shortly after.

When something sits outside the node, the HTTP Request node calls any endpoint of the BounceBan API directly and reuses the same credential through predefined authentication. One operation covers the core job, so that fallback is there for the rest of the API rather than for daily use.

Two limits are worth stating up front. There is no BounceBan trigger node, so a workflow around it always starts with something else, and the package is a community node, which rules out instances that cannot install one. Node version is 1, and the operation works on a single address per call, with Processing Mode deciding whether items run one after another or concurrently.

Connect

How do you install and connect the BounceBan node?

  1. 01

    Install the community package

    The node does not ship with n8n. On a self-hosted instance, open Settings, then Community nodes, and install the npm package n8n-nodes-bounceban (version 1.1.1). n8n Cloud only accepts verified community nodes, so check that side before planning a workflow around it. Nothing is billed by n8n for installing a community node.

  2. 02

    Create the BounceBan credential

    Once the package is installed, go to the Credentials menu in n8n and create the BounceBan credential there. A credential is created once and reused across every workflow on the instance, so there is no need to repeat the setup in each node. The node has no authentication selector: the credential is the only thing to set, and the exact fields to fill are not documented in the source used for this page, so check them in n8n when you create it.

  3. 03

    Drop the node into a workflow

    Add the BounceBan node, pick the credential from its dropdown, and select the Email resource with the Verify Single Email operation. Fill Email Address with a static value such as example@domain.com while testing, then swap it for an expression like {{ $json.email }} that reads the address from the previous node. Run the node once to see the shape of what comes back.

Actions

What can the BounceBan node do?

The BounceBan node exposes 1 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceVerify Single Email
Email✓

Email

1 operation
01

Verify a single email address

email.validateEmail

What you see in n8n

Notes & use cases

The operation sends one address to BounceBan and returns its verification result to the next node, catch-all addresses included.

Key parameters

  • Email Address: the address to check, typed as example@domain.com or read from the item with {{ $json.email }}. Required.
  • Processing Mode: sequential, the default, verifies one email at a time; batch runs items concurrently.
  • Mode: regular assumes nothing about the owner's company domain; deepverify assumes it matches and lifts the success rate on accept-all addresses.
  • Disable Catchall Verify: at 1, only basic SMTP verification runs and those addresses return result: 'unknown', score: -1, credit cost 0.
Use cases
vetting a freshly submitted address before it becomes a contact record.
Need help

Need help automating BounceBan with n8n?

A person reads every message.

FAQ

BounceBan and n8n, common questions

01Is the BounceBan n8n integration free?
On the n8n side, yes. The BounceBan node is a community node distributed as the npm package n8n-nodes-bounceban, and n8n charges nothing to install or run it. It is not bundled with the product, so it has to be installed from Settings, then Community nodes, on a self-hosted instance; n8n Cloud only accepts verified community nodes. What BounceBan itself costs for verifications is a separate matter and is not covered here. One detail is worth noting: when catch-all verification is disabled, the affected addresses come back with a credit cost of 0.
02What credentials does the BounceBan node need?
One BounceBan credential, created once from the Credentials menu in n8n. Every workflow on the instance can then select it from the node dropdown, with nothing to paste again anywhere else. The node itself has no authentication selector, so there is no choice to make between methods: the credential is the whole setup. Keep in mind that the package has to be installed before the credential type shows up in the list, since a community node brings its own credential definition with it. The exact fields to fill are not documented in the source used for this page, so check them in n8n when you create it.
03What are the limits of the BounceBan node in n8n?
The node exposes 1 resource and 1 operation, and its maximum version is 1, so the surface is deliberately small: one address verified per call. Processing Mode decides whether items run one at a time or concurrently, which is the only lever on throughput inside the node. Anything else in the BounceBan API has to go through the HTTP Request node, which calls any endpoint directly and reuses the same credential through predefined authentication. And since this is a community node, an instance that cannot install community nodes cannot run it at all.
04Does BounceBan have a trigger node in n8n?
No. There is no BounceBan trigger in n8n, so a workflow built around it starts with something else. Three options cover nearly everything. A Schedule Trigger runs the workflow at a fixed interval, which suits a list that gets cleaned every morning. An n8n Webhook node gives you a URL that a third-party service calls, which suits a form or an app that can post on submission. Or another tool's trigger opens the workflow, and the BounceBan node sits further down the chain as one step among others.
05n8n or Make for verifying emails?
It depends on where the workflow has to live. Make is a hosted automation platform with no self-hosting option, billed per operation, with a visual logic that many teams find quick to pick up. n8n can be self-hosted with Docker or npm, or used on n8n Cloud, and a workflow is the same in both cases. That choice matters here more than usual: the BounceBan node is a community node, and community nodes install on a self-hosted instance, while n8n Cloud only takes verified ones. Data control and cost model point the same way.
Same platform

Other docs you might need on this stack.

Browse all integrations