Resources · Make integration

Bouncer Make integrationAutomate Bouncer with Make.

Bad email addresses cost you bounces and sender reputation, so why not catch them before they reach your list? The Bouncer Make integration gives you 3 action modules. This guide connects your account, builds a first scenario and explains when each module earns its place.

Try the Bouncer integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Bouncer Make integration do for you?

The Bouncer Make integration lets a Make scenario (the automation you build in Make, a chain of steps) send an email address to Bouncer and get the check back, with no code. You use it to decide what happens next to a contact based on what Bouncer says about the address.

A cleaner CRM from day one. A sales team collecting leads from a web form can place Verify Single Email right after the form app. Each address gets checked before the contact is created, and a filter can keep the doubtful ones aside for a human look.

No surprise when your balance runs dry. Check Credits reads how many credits remain on your Bouncer account. A marketing ops lead can run it before a big import and send an alert to the team chat when the number looks low.

Everything else Bouncer exposes. Make an API Call reaches any endpoint of the Bouncer API with the same connection, for the jobs the two ready-made modules do not cover.

Know the limits: Bouncer has no trigger in Make, so a scenario always starts from another app or from a schedule. Bouncer's page in the Make docs also warns that it was written with AI help and should be checked against Bouncer's own documentation. New to the editor? The Make training walks through the basics, Make pricing explains how operations are counted, and if you are also weighing n8n, the n8n vs Make comparison sets the two side by side.

Connect

How do you connect your Bouncer account to Make?

  1. 01

    Generate your API key in Bouncer

    Sign in to Bouncer, open the API section from the menu on the left, then click Generate API Key. Copy the key that appears on screen. You need an active Bouncer account for this.

  2. 02

    Open a connection from a Bouncer module

    In your Make scenario, add any Bouncer module and click Create a connection. A connection is your Bouncer account linked to Make once, then reused by all three modules. You can type a label in Connection name if you like.

  3. 03

    Paste the key and save

    Paste the API key you copied from Bouncer into the credentials field and confirm. Once the connection is saved, the module is ready to use. If the screen shows extra instructions, follow them as displayed.

First scenario

Your first scenario: verify each new lead's email

GoalWhen a new lead arrives in the app you already use for forms or sign-ups, Make asks Bouncer to verify the address before anything else happens.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where new leads show up first (a form tool or a CRM), since Bouncer has no trigger of its own.

  2. 02

    Add Verify Single Email

    Click the + to the right of that first module, search for Bouncer and choose Verify Single Email. Select your connection or create it with the API key.

  3. 03

    Map the email address

    In the email field, map the address coming from the first module. Each lead flows through as one bundle, a single item passed from one module to the next.

  4. 04

    Test with Run once

    Click Run once and submit a test lead. Then read the bundles each module received: the Bouncer one shows what came back for your test address.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default) and turn the scenario on. From then on, each new lead gets its address checked.

Modules

What each Bouncer module does

Bouncer gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Bouncer1

Check Credits

Action

In Make“Checks amount of available credits on the account.”

Tells you how many credits are left on your Bouncer account, so a scenario can react before the balance stops your checks. Nothing about your contacts changes.

When to use it
place it ahead of a large import or a list cleanup, then route an alert to your team when the balance looks too thin for the job.
Watch out
this module only reads the balance; it cannot top it up, so the refill still happens in Bouncer.
Bouncer2

Make an API Call

Action

In Make“Make an API Call”

Opens the whole Bouncer API to your scenario, reusing the connection you already created, for any request that the two ready-made modules do not offer.

When to use it
reach for it only when Verify Single Email and Check Credits fall short, for example to call another endpoint listed in Bouncer's API documentation.
Watch out
you write the request yourself, so keep Bouncer's API reference open to get the path and parameters right.
Bouncer3

Verify Single Email

Action

In Make“Verifies single email address in real time.”

Sends one email address to Bouncer and hands back its verdict, so the rest of the scenario can keep, flag or drop the contact. Each check runs once per bundle, which Make counts as one operation on your plan.

When to use it
right after a sign-up, a demo request or a new CRM contact, before the address joins a mailing list.
Watch out
it handles one address per run; a list of contacts means one run per contact.
Need help

Need help automating Bouncer with Make?

A person reads every message.

FAQ

Bouncer and Make: frequent questions

01Is the Bouncer Make integration free?
Yes, on the Make side. Bouncer is a standard app, so its modules work from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need your own active Bouncer account, and its subscription is set on Bouncer's pricing page, not in Make.
02What do you need to connect Bouncer to Make?
An active Bouncer account and an API key. In Bouncer, open the API section in the left menu, click Generate API Key and copy the key shown. In Make, add a Bouncer module, click Create a connection, give it a name if you want, then paste the key. That single connection serves all three Bouncer modules, including Make an API Call, so the setup happens only once per account and every new scenario can pick it from the list.
03Can a Bouncer scenario start by itself in Make?
Not from Bouncer. The app has no trigger module, scheduled or instant, so the scenario has to begin somewhere else. The usual start is the trigger of the app where addresses appear, such as a form tool or a CRM, with Verify Single Email placed right after it. Another route is a schedule set on the first module, every 15 minutes by default, or the instant trigger of an app that calls Make as soon as it has a new address.
04What if a Bouncer module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Bouncer API from inside the scenario and reuses the connection you already set up, so nothing new needs to be authorized. The listed modules cover single email checks and the credit balance; anything beyond those goes through this module. Keep Bouncer's own API reference at hand, because the Make documentation for this app notes it was drafted with AI and should be checked against the vendor.
05Should you use Make or n8n for Bouncer?
It depends on the tool your team already runs. In Make, Bouncer comes with three modules: single email verification, a credit check and Make an API Call for the rest of the API, all usable from the Free plan. Many apps also have an n8n node, so check whether one exists for Bouncer before deciding. Pick the platform where your other automations already live, since the address check is rarely a scenario on its own.
Same platform

Other docs you might need on this stack.

Browse all integrations