Resources · Make integration

DeBounce Make integrationAutomate DeBounce with Make.

Want every new email address checked before it reaches your list? The DeBounce Make integration gives you 2 action modules, with no trigger of its own. This guide is for marketers and ops people who collect contacts: you connect your API key, then build a first scenario step by step.

Try the DeBounce integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the DeBounce Make integration let you automate?

The DeBounce Make integration lets a Make scenario, the automation you build in Make, send an email address to DeBounce and get the check back without leaving the flow. Each step of that flow is a module, one brick of the scenario, and DeBounce offers two of them: Email Validation and Make an API Call.

Check signups before they land in your CRM. A form or a sheet collects new contacts, Email Validation checks each address, and the next module only receives what you decide to keep. Your sales team stops chasing addresses nobody reads.

Clean an imported list, one contact at a time. Each row of your file becomes a bundle, one item passing from module to module, and DeBounce checks it on the way. Keep in mind that every check is an operation, the unit Make counts on your plan.

Reach the rest of the DeBounce API. When you need something Email Validation does not do, Make an API Call lets you send your own request to DeBounce, over the connection you already set up. Handy once you have read the DeBounce API docs and know which request you want.

What Make does not do here: DeBounce has no trigger and no search module, so a scenario always starts on another app or on a schedule. The official doc also says its content is AI-generated and asks you to verify important details with DeBounce. For the wider picture, read our Make review, check Make pricing, or weigh the two tools in n8n vs Make.

Connect

How do you connect your DeBounce account to Make?

  1. 01

    Copy your API key in DeBounce

    You need an active DeBounce account. Open the dashboard, click API Settings, and copy the API key shown on screen. Keep it at hand, Make will ask for it in a moment.

  2. 02

    Add a DeBounce module in Make

    In your scenario, add the Email Validation module and click Create a connection. A connection is your DeBounce account linked to Make once, then reused by every DeBounce module.

  3. 03

    Name it and paste the key

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

First scenario

Your first scenario with DeBounce and Make

GoalWhen a new contact arrives in another app, Make sends the address to DeBounce and passes the result along.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. The first module comes from the app where your contacts arrive, since DeBounce cannot start a flow.

  2. 02

    Pick the source of the addresses

    Search that app by name, choose the module that brings in new contacts and connect your account. Make then lists the sheets or objects it can read, so you just pick one.

  3. 03

    Add Email Validation

    Click the + on the right of the first module, search DeBounce and pick Email Validation. Select your connection, then map the email field coming from the previous module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received, including what DeBounce sent back for your test address.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From there, each new contact is checked without you opening DeBounce.

Modules

What the DeBounce modules do

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

DeBounce1

Email Validation

Action

In Make“Validates an email.”

Email Validation sends one address to DeBounce and hands the verdict to the next module, so your scenario can keep or drop the contact on its own.

When to use it
right after a form, a sheet or a CRM brings in a new contact, before the address is added to a mailing list.
Watch out
the module checks one address per run, and each run is an operation on your Make plan, so a long list costs as many operations as it has rows.
DeBounce2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call gives you access to any endpoint of the DeBounce API, using the connection you already created, without a new login.

When to use it
when Email Validation does not cover what you need and the DeBounce API documentation describes the request that does.
Watch out
here you write the request yourself, so read the DeBounce API documentation first and test the call with Run once before switching the scenario on.
Need help

Need help automating DeBounce with Make?

A person reads every message.

FAQ

Questions about the DeBounce Make integration

01Is the DeBounce Make integration free?
Yes, on the Make side. DeBounce is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Each module run counts as an operation. DeBounce itself is a separate subscription: you need an active account and an API key, and its prices are on the DeBounce pricing page.
02What do you need to connect DeBounce to Make?
An active DeBounce account and its API key. You find the key in the DeBounce dashboard under API Settings, and you copy it as displayed. In Make, you add a DeBounce module, click Create a connection, give the connection a name if you like, and paste the key. That connection is then shared by both DeBounce modules, so you only do it once per account. If you have not signed up yet, create your DeBounce account first and choose a subscription on their pricing page.
03Does the DeBounce Make integration react in real time?
No, because DeBounce has no trigger in Make: its two modules are actions, so they run inside a scenario started by something else. You have two options. Put another app first, for example the module that watches new form entries, and DeBounce checks each address it passes along. Or start the scenario on a schedule: new scenarios run every 15 minutes by default, with a minimum of 15 minutes on the Free plan and 1 minute on paid plans. If the first app offers an instant trigger, the check follows as soon as that app calls Make.
04What if the DeBounce module you need is missing in Make?
Use Make an API Call. It is one of the two DeBounce modules, and it can reach any endpoint of the DeBounce API with the connection you already set up. Everything that Email Validation does not cover goes through it: you build the request from the DeBounce API documentation, then test it with Run once. Keep in mind that the official Make doc for DeBounce states that its content is AI-generated and may contain mistakes, so confirm important details with DeBounce before relying on them.
05Should you use Make or n8n for DeBounce?
It depends on how you like to build. On Make, DeBounce comes with 2 ready modules, Email Validation for the everyday check and Make an API Call for the rest of the API, and you assemble the scenario visually. Many apps also have an n8n node, so check whether DeBounce has one before choosing. Neither tool is ranked here: compare the modules you actually need, the way each editor works, and the plan that fits your volume. Our comparison page on n8n and Make lays out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations