Resources · Make integration

ZeroBounce Make integrationAutomate ZeroBounce with Make.

Can Make check every new email address before it reaches your list? The ZeroBounce Make integration gives you 4 action modules: address validation, credit balance, API usage and an open API call. This guide shows builders how to connect the account and run a first scenario.

Try the ZeroBounce integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the ZeroBounce Make integration do?

The ZeroBounce Make integration lets a Make scenario, the automation you build in Make, send email addresses to your ZeroBounce account and get the check back without opening ZeroBounce. Each module is one brick of that scenario, and all four ZeroBounce modules are actions: they act when another step hands them an address.

Screen signups before they hit your CRM. A form tool or a spreadsheet starts the scenario, then Validate Emails checks the address it received. Filtering on that answer keeps bad addresses out of the next app.

Watch your credits. Validation needs an active credit balance. Get Credit Balance reads what is left, so a scenario can warn someone on Slack or by email before the balance runs dry.

Report on usage. Get API Usage pulls the usage figures of your API key into a sheet, handy when several teams share one ZeroBounce account.

ZeroBounce has no trigger in Make, so something else has to start the scenario: another app, or the schedule of Make itself. Anything the three named modules skip goes through Make an API Call. Before you size your plan, read Make pricing; if you are weighing tools, n8n vs Make lays out the criteria, and Make training covers scenario building from zero.

Connect

How do you connect ZeroBounce to Make?

  1. 01

    Generate an API key in ZeroBounce

    You need an active ZeroBounce account. Log in, open the dashboard, go to the API section or the API key management area, and click the button that generates a new key. Copy the key shown on screen.

  2. 02

    Add a ZeroBounce module in Make

    In your scenario, add any ZeroBounce module and click Create a connection. A connection is your ZeroBounce account linked to Make once and reused by every ZeroBounce module afterward.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, then follow the on-screen instructions to save the connection.

First scenario

Your first scenario: validate each new contact

GoalWhen a new contact arrives from another app, Make sends the address to ZeroBounce and gets the validation back.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. It comes from the app that collects your contacts, such as a form tool or a sheet.

  2. 02

    Add Validate Emails

    Click the + on the right of that first module, search for ZeroBounce and pick Validate Emails. Select the connection you created, or click Add to create it.

  3. 03

    Map the email address

    In the module settings, map the address coming from the first module. Each contact travels as one bundle, meaning one item passed from a module to the next.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and check what ZeroBounce returned for your test contact.

  5. 05

    Schedule and switch on

    On the first module, set the Scheduling clock, every 15 minutes by default, then switch the scenario on. Each run of each module counts as one operation on your Make plan.

Modules

What can ZeroBounce do in Make?

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

ZeroBounce1

Get API Usage

Action

In Make“Gets usage of API.”

Get API Usage returns the usage figures of your ZeroBounce API key, so a scenario can drop them into a sheet or a message without you logging in.

When to use it
several teams or tools share one key and someone needs to keep an eye on how fast it is used.
Watch out
it reads usage, not what is left to spend; for the remaining credits, pick Get Credit Balance instead.
ZeroBounce2

Get Credit Balance

Action

In Make“Shows credits you have left on your account.”

With Get Credit Balance, the scenario learns how many credits remain on your ZeroBounce account and can act on that number, for instance by alerting the person who tops it up.

When to use it
place it before Validate Emails and add a filter, so validation only runs while credits are available.
Watch out
it costs a Make operation each time it runs, like any module.
ZeroBounce3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module reaches any endpoint of the ZeroBounce API from your scenario, reusing the same connection, so you are not stuck when the three named modules stop short.

When to use it
the ZeroBounce feature you need has no dedicated module in Make.
Watch out
you build the request yourself from the ZeroBounce API documentation, so test it with Run once before switching the scenario on.
ZeroBounce4

Validate Emails

Action

In Make“Validates an email. The API requires that you have an active credit balance and will never consume a credit for any unknown result.”

Validate Emails sends an address to ZeroBounce and hands you back its verdict, which later modules can filter on to keep bad contacts out of your tools.

When to use it
right after a signup, an import or a new lead, before the address lands in your CRM or mailing list.
Watch out
your account needs an active credit balance, and an unknown result never consumes a credit.
Need help

Need help automating ZeroBounce with Make?

A person reads every message.

FAQ

Questions about the ZeroBounce Make integration

01Is the ZeroBounce Make integration free?
Yes, on the Make side. ZeroBounce is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and count usage in credits, meaning operations, per month. ZeroBounce itself runs on its own subscription and credits, which you check on the ZeroBounce pricing page, since validation needs an active credit balance.
02What does it take to connect ZeroBounce to Make?
An active ZeroBounce account and an API key. Log in to ZeroBounce, go to the API section or the API key management area from the dashboard, generate a new key and copy it. In Make, add a ZeroBounce module, click Create a connection, give it a name if you like and paste the key. The connection is then reused by all four ZeroBounce modules, so you only do this once per account.
03Does the ZeroBounce Make integration react in real time?
No, ZeroBounce has no trigger in Make, neither scheduled nor instant. The scenario has to start elsewhere. The usual option is a trigger from another app, for example the form or the sheet where contacts arrive, with Validate Emails placed right after it. The other option is the schedule of Make: set the clock on the first module, every 15 minutes by default, or down to 1 minute on a paid plan, and the scenario runs Get Credit Balance or Get API Usage on that rhythm.
04What if a ZeroBounce module is missing in Make?
Use Make an API Call. It calls any endpoint of the ZeroBounce API with the connection you already have, so a feature without its own module is still within reach. You write the request from the ZeroBounce API documentation, then test it with Run once and read the bundle that comes back. The official Make page on ZeroBounce also warns that its text was generated with AI from vendor docs and may contain mistakes, so check important details with ZeroBounce directly.
05Make or n8n for ZeroBounce: which one fits?
It depends on the tool your team already runs. In Make, ZeroBounce comes with 4 modules, including Make an API Call for everything else, and it works from the Free plan within that plan's limits. The same app often has an n8n node as well, so look at what that node covers before choosing. Compare the modules each side offers for your exact use case and where the rest of your automations live. No ranking of the two tools applies here, only the fit with your stack.
Same platform

Other docs you might need on this stack.

Browse all integrations