Resources · Make integration

Data24-7 Make integrationAutomate Data24-7 with Make.

Can Make check and enrich your contact data for you? The Data24-7 Make integration gives you 7 action modules and no trigger. This guide is for sales and ops teams who want clean lists, and it walks you from the API password to a first working scenario.

Try the Data24-7 integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Data24-7 Make integration do for you?

The Data24-7 Make integration links your Data24-7 account to Make, a visual tool where you build a scenario (an automation made of bricks called modules). Each of its 7 modules is an action: Make sends it one record at a time and passes the answer to the next step, so a lookup you used to run by hand happens inside the flow.

A cleaner call list. Before a sales rep dials, a scenario can pass each number through Do-Not-Call, then through Carrier24-7, and only keep the rows you decide to keep. The module names describe the lookup; read the output of a test run to see exactly what comes back.

Richer lead records. A form or CRM hands over a name and an address, and Phone Append or Email Append tries to add the missing contact detail before the record lands in your tool. When the input is a phone number instead, Reverse Phone Append works the other way round.

Context on web visitors. IP Address Lookup takes an address captured by a signup form and returns what Data24-7 knows about it, which helps a marketer sort traffic before anyone follows up.

What Make will not do here: there is no trigger, so Data24-7 never starts a scenario on its own, and there is no generic API call module to reach endpoints outside the 7. Make's own documentation for this app is flagged as AI-generated, so test each module on real data. If you are weighing tools, the n8n vs Make comparison lays out the differences, and the Make pricing page explains how operations are counted.

Connect

How do you connect Data24-7 to Make?

  1. 01

    Create an API password in Data24-7

    Log in to Data24-7 and open the Accounts section, then click API Key/Password and API Version 1 & 2. Type a password and click Change Password if you never set one. Your username is simply your account email.

  2. 02

    Add a Data24-7 module in Make

    In your scenario, add any Data24-7 module and click Create a connection. The Connection name field is optional, but a clear label helps when several people share the same Make team.

  3. 03

    Paste the credentials and save

    Enter the username and the API password you copied, or follow the on-screen instructions, and save. The connection (your Data24-7 account linked to Make once) is then reused by every Data24-7 module you add later.

First scenario

Build your first scenario with Data24-7

GoalWhen a new lead reaches your form or CRM, Make appends a phone number with Data24-7 and checks it against the Do-Not-Call module.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since Data24-7 has no trigger, pick the app where your leads live as the first module.

  2. 02

    Add Phone Append

    Click the + on the right of that first module, search Data24-7 and choose Phone Append. Link your account with Create a connection, then map the lead fields from the previous module.

  3. 03

    Chain the Do-Not-Call check

    Add Do-Not-Call after it and map the number Phone Append returned (check it in the first test run). Each bundle (one lead moving through the chain) now carries both answers.

  4. 04

    Test with Run once

    Click Run once and open the bubble above each module to read the bundles it received. This is where you learn what Data24-7 actually returns for your data.

  5. 05

    Schedule and switch on

    Set the clock on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What each Data24-7 module does

Data24-7 gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Data24-71

Carrier24-7

ActionIn the docs only

Sends a phone number to Data24-7 and brings back its carrier lookup, as the module name suggests, so a scenario can tell what kind of line it is dealing with before acting on it.

When to use it
place it ahead of a texting or calling step when the route depends on the line behind the number.
Watch out
the documentation lists no fields for it, so run it once on a known number and read the output before you build filters on it.
Data24-72

Do-Not-Call

ActionIn the docs only

Gives your sales flow a gate: each number goes to Data24-7 for a Do-Not-Call check, and the answer rides along with the lead so later modules can route it differently.

When to use it
right before a lead is pushed into a dialer or a call list for your reps.
Watch out
the module only returns an answer; Make does nothing with it until you add a filter or a router that acts on the result.
Data24-73

Email Append

ActionIn the docs only

Tries to fill the missing email on a contact record by asking Data24-7, based on what the name suggests, so a lead captured by phone or by postal address can also join an email sequence.

When to use it
when a form or an import delivers contacts without an address to write to.
Watch out
the documentation does not say which inputs it needs, so test with a few real records and check what the first bundle returns.
Data24-74

IP Address Lookup

ActionIn the docs only

Turns a raw IP address into the information Data24-7 holds about it, which gives a marketer or a support agent some context on a signup before anyone replies to it.

When to use it
after a web form or an app that records the visitor IP, to tag or sort new entries.
Watch out
it works on one address per bundle, so a list of many visitors costs one operation for each of them.
Data24-75

Phone Append

ActionIn the docs only

Asks Data24-7 for a phone number to add to a contact you only know by other details, so a list gathered from events or newsletters becomes something your sales team can actually call.

When to use it
in a lead enrichment flow, before the record is written to your CRM.
Watch out
map the fields from the previous module carefully; test on a few complete records first, since the documentation does not say which details it needs.
Data24-76

Reverse Phone Append

ActionIn the docs only

Works in the opposite direction from Phone Append: you start from a number and Data24-7 returns what it holds on that number, going by the module name, which saves a manual search for every missed caller.

When to use it
when inbound calls or SMS leave you with a number and nothing else.
Watch out
the page cannot tell you which fields come back; one Run once on a real number shows it faster than guessing.
Data24-77

Text@

ActionIn the docs only

Belongs to the texting side of Data24-7, going by its name and key, and lets a scenario hand a phone number to that service without leaving Make, so a text step sits right next to your checks.

When to use it
after Carrier24-7 or Do-Not-Call has cleared the number and you want the next step in the same flow.
Watch out
the official documentation gives no description of this module, so confirm its exact behavior on a test number first.
Need help

Need help automating Data24-7 with Make?

A person reads every message.

FAQ

Data24-7 and Make: common questions

01Is the Data24-7 Make integration free?
Yes, on the Make side. Data24-7 is a standard app, available from the Free plan. 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 drop the interval to 1 minute and lift the scenario cap. You still need an active Data24-7 account with an API key, which is billed by Data24-7, not by Make.
02What do you need to connect Data24-7 to Make?
You need an active Data24-7 account and API access. In Data24-7, open Accounts, then API Key/Password and API Version 1 & 2, and set an API password if none exists. Your username is the email of the account. In Make, add a Data24-7 module, click Create a connection, give it a name if you like, and paste the username and API password. That one connection then serves all 7 modules, so you set it up only once.
03Does the Data24-7 Make integration have a trigger?
No. All 7 Data24-7 modules are actions, so the app never starts a scenario by itself. You start the flow another way: with a trigger from the app that holds your leads, such as a form or a CRM, or with the schedule set on the first module, which runs every 15 minutes by default on a new scenario. Data24-7 modules then sit in the middle of the chain and process each bundle that reaches them.
04What if a Data24-7 module you need is missing in Make?
It depends on what you need. This app has no Make an API Call module, so you cannot reach Data24-7 endpoints outside the 7 modules from inside this integration. First check whether one of the existing modules, combined with a filter or a router, already covers the case. If it does not, another app may, or the team can look at your use case and suggest a workable path for it.
05Should you use Make or n8n for Data24-7?
It depends on how you like to build. On Make, Data24-7 comes with 7 ready modules, one shared connection and a visual editor where Run once shows each bundle, which suits a team that wants to start fast. Many apps also have an n8n node, so check whether Data24-7 has one before deciding. Compare the tools on the modules each offers for your case and on how your team prefers to work.
Same platform

Other docs you might need on this stack.

Browse all integrations