Resources · Make integration

NeverBounce Make integrationAutomate NeverBounce with Make.

Stop bad addresses before they reach your CRM or your mailing list. The NeverBounce Make integration gives you 2 action modules: one checks a single email, the other calls any part of the NeverBounce API. This guide shows how to link your key and build a first check, step by step.

Try the NeverBounce integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the NeverBounce Make integration do for you?

The NeverBounce Make integration lets a Make scenario (the automation you build, a chain of steps) send an email address to NeverBounce and get the verification result back. You then decide what happens next: keep the contact, flag it or drop it, with no code.

A cleaner sign-up form. Someone fills in a form handled by another app. The next module, Get an Email Verification, checks the address before the contact lands anywhere, so a typo never becomes a record.

Safer imports for sales. A sales rep adds prospects to a sheet or a CRM. Each new row goes through NeverBounce first, and the scenario only pushes the addresses you choose to trust. The Airtable Make integration can serve as the source of this kind of list.

Anything the two modules skip. Make an API Call reaches the rest of the NeverBounce API with the same connection, so you are not stuck with only single checks.

What the app does not do in Make: it has no trigger, so NeverBounce never starts a scenario on its own. Another app, or the schedule of the scenario, has to kick things off. If you are also looking at n8n, the n8n vs Make comparison lays out both tools, and the Make pricing page explains how operations are counted.

Connect

How do you connect NeverBounce to Make?

  1. 01

    Create an API key in NeverBounce

    In your NeverBounce account, open the Custom Integration Apps section and create a new custom integration app. Its overview page then shows an API key: copy it, you will paste it into Make in a moment.

  2. 02

    Add a NeverBounce module in Make

    In your scenario, click the + and search for NeverBounce, then pick a module. Click Create a connection. A connection is your NeverBounce account linked to Make once, then reused by every NeverBounce module.

  3. 03

    Name the connection and paste the key

    The Connection name field is optional, but a clear name helps when several accounts coexist. Paste the API key you copied, or follow the instructions shown on screen, and save.

First scenario

Your first scenario: check each new email with NeverBounce

GoalWhen a new contact arrives in another app, Make asks NeverBounce whether the address is valid.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. This first module comes from the app that holds your contacts, such as a form or a spreadsheet.

  2. 02

    Pick where the emails come from

    Choose the module of that other app that returns new contacts, connect its account and fill its fields. Each contact it returns becomes a bundle, one item passed to the next module.

  3. 03

    Add Get an Email Verification

    Click the + on the right, search for NeverBounce and pick Get an Email Verification. Select your connection, then map the email coming from the first module into it.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time, and you can open each module to read the bundles it received, including what NeverBounce sent back about the address.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module (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 the NeverBounce modules do

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

NeverBounce1

Get an Email Verification

Action

In Make“Single verification allows you to verify individual emails and gather additional information pertaining to the email.”

You get a verdict on one email address at a time, plus extra details NeverBounce holds about it, right inside your scenario. That result lets the following modules keep, flag or skip the contact.

When to use it
place it just after a new lead, sign-up or imported row, before the address is written to your CRM or a mailing tool.
Watch out
it handles one address per bundle, so a long list costs one operation per address on your plan.
NeverBounce2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This one opens the rest of the NeverBounce API to your scenario, using the connection you already set up, so you can reach a NeverBounce function that no ready-made module covers.

When to use it
pick it only when Get an Email Verification does not do what you need, for example another kind of request described in the NeverBounce API documentation.
Watch out
you write the request yourself here, so read the NeverBounce API reference first and test the call with Run once.
Need help

Need help automating NeverBounce with Make?

A person reads every message.

FAQ

NeverBounce and Make: frequent questions

01Is the NeverBounce Make integration free?
Yes, on the Make side. NeverBounce is a standard app, so it works from the Free plan, which allows 2 active scenarios, runs at most every 15 minutes, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. NeverBounce itself has its own subscription, which you handle with NeverBounce directly.
02What do you need to connect NeverBounce to Make?
An active NeverBounce account and an API key. You create that key in NeverBounce by opening the Custom Integration Apps section, creating a new custom integration app and copying the key from its overview page. In Make, you add a NeverBounce module, click Create a connection, optionally name it, and paste the key. The same connection then serves both NeverBounce modules. If the key ever changes, update it in that one connection and every module follows.
03Can a NeverBounce scenario in Make start in real time?
Not from NeverBounce, because the app has no trigger in Make. The scenario has to start elsewhere: with a trigger from another app, such as the one that receives your leads, or with the schedule on the first module, which runs every 15 minutes by default and no more often than every 15 minutes on the Free plan. If that other app offers an instant trigger, it calls Make through a webhook as soon as something happens.
04What if the NeverBounce module you need is missing in Make?
Use Make an API Call. It reuses your NeverBounce connection and lets the scenario call any part of the NeverBounce API, so you are not limited to single checks with Get an Email Verification. You need to know which request to send, so keep the NeverBounce API documentation open. The Make documentation for this app is AI-generated from the NeverBounce docs, so check anything important directly with NeverBounce. Test each new call with Run once before switching the scenario on.
05Should you use Make or n8n with NeverBounce?
It depends on the tool your team already runs. In Make, NeverBounce offers 2 modules: a single email check and a generic API call, both set up in a visual editor. The same app often has an n8n node too. Compare the two editors on your own use case, the modules you need and how your team works, rather than on the app alone. The n8n vs Make comparison linked above gives a fuller picture of each tool, criterion by criterion.
Same platform

Other docs you might need on this stack.

Browse all integrations