Resources · Make integration

D7SMS Make integrationAutomate D7SMS with Make.

Can Make send a text message through D7SMS when something happens in another tool? Yes. The D7SMS Make integration gives you 3 action modules, with Send SMS at the center. This page connects your account, builds a first scenario and explains when each module earns its place.

Try the D7SMS integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the D7SMS Make integration do for you?

The D7SMS Make integration links your D7SMS account to Make so a scenario, the automation you build in Make, can send text messages for you. Each step of that scenario is a module, and D7SMS brings three of them: one sends an SMS, one reads your account balance, one calls any other part of the D7SMS API.

Alert the right person without opening a dashboard. Put a trigger from another app first, a new form entry or a new booking, then add Send SMS. Make passes each item, called a bundle, to D7SMS, and the text goes out with the details you mapped. Booking tools such as the one on the 10to8 Make integration page are a natural starting point.

Keep an eye on your sending budget. Before a large batch, a Check Balance step reads what is left on the account and passes it on, so the rest of the scenario works with a known figure.

Reach what the listed modules skip. D7SMS exposes more in its API than three modules show. Make an API Call reuses your connection and lets you call any endpoint of that API.

What Make does not give you here: D7SMS has no trigger module, so Make cannot start a scenario on its own when D7SMS sends or receives something. The run always begins elsewhere, in another app or on a schedule. The same app often has an n8n node too; the n8n vs Make comparison helps you choose, and the Make training covers the editor from zero.

Connect

How do you connect your D7SMS account to Make?

  1. 01

    Generate your API token in D7SMS

    In your D7SMS dashboard, open the developer applications section, click Generate auth token for your application and copy the token shown on screen. You need an active D7SMS account for this, so sign up first if you have none.

  2. 02

    Add a D7SMS module in Make

    In your scenario, add any D7SMS module, for example Send SMS, and click Create a connection. The connection is your D7SMS account linked to Make once, then reused by every D7SMS module you add later.

  3. 03

    Name it and paste the token

    The Connection name field is optional, but a clear name helps once you run several accounts. Paste the API token you copied, or follow the on-screen instructions, then save. Make now lists the connection in the module.

First scenario

Your first scenario: a text message when a new lead arrives

GoalWhen a new entry lands in another app, Make sends a text message through D7SMS.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. That first module decides when the whole scenario starts.

  2. 02

    Pick the starting app

    D7SMS has no trigger, so search the app where the event happens, a form or a CRM for instance, pick its trigger and connect that account.

  3. 03

    Add Send SMS

    Click the + on the right of the first module, search D7SMS, choose Send SMS and select the connection you created. Map the data it needs from the previous module.

  4. 04

    Test with Run once

    Click Run once, then create a test entry in the starting app. Read the bundles each module received, and check that the text reached your own phone.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From here Make handles each new entry without you.

Modules

What each D7SMS module does

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

D7SMS1

Check Balance

ActionIn the docs only

This module asks D7SMS how much is left on your account and hands that answer to the next step, so the scenario can react before it runs dry.

When to use it
place it right before a large send, so the balance is visible in the bundles you read after a Run once test.
Watch out
the Make documentation for D7SMS is marked as AI-generated, so confirm with D7SMS what the balance covers before building decisions on it.
D7SMS2

Make an API Call

ActionIn the docs only

Here you reach any endpoint of the D7SMS API with the connection you already set up, which covers whatever the two dedicated modules leave out.

When to use it
a feature you rely on in D7SMS has no module in Make and you still want it inside the same scenario.
Watch out
you write the request yourself, so keep the D7SMS API documentation open and test each call with Run once before switching on.
D7SMS3

Send SMS

ActionIn the docs only

Send SMS delivers a text message from your D7SMS account, built from the data the earlier modules passed along, so a customer or a colleague hears about an event without anyone typing it.

When to use it
a booking is confirmed, a form is submitted or an order ships and someone should get a short heads-up on the phone.
Watch out
each bundle reaching this module sends one message, so a trigger returning many items sends many texts.
Need help

Need help automating D7SMS with Make?

A person reads every message.

FAQ

Questions about the D7SMS Make integration

01Is the D7SMS Make integration free?
Yes, on the Make side. D7SMS is a standard app, available from the Free plan onward. The Free plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs and 5 minutes of execution per run. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Make counts each module execution as one operation against your plan. Sending messages through D7SMS itself follows your D7SMS subscription, described on the D7SMS pricing page.
02What do you need to connect D7SMS to Make?
An active D7SMS account and an API token. In the D7SMS dashboard, go to the developer applications section, click Generate auth token for your application and copy the token. Then, in Make, add any D7SMS module, click Create a connection, optionally give it a name and paste the token. That one connection serves every D7SMS module in all your scenarios, so you only do this once per account, and every new scenario simply picks it from the list.
03Does the D7SMS Make integration react in real time?
It depends on what starts the scenario, because D7SMS has no trigger module of its own. The scenario begins with another app. If that app offers an instant trigger, one that calls Make through a webhook as soon as something happens, the text goes out right after the event. If it uses a scheduled trigger, Make checks at the interval you set on the first module, every 15 minutes by default. You can also start the scenario on a plain schedule.
04What if a D7SMS module is missing in Make?
Use Make an API Call. It reuses your D7SMS connection and lets you call any endpoint of the D7SMS API from the scenario, so features without a dedicated module stay within reach. You write the request following the D7SMS API documentation. Note that the Make documentation for this app is marked as AI-generated and may contain mistakes, so check important details with D7SMS directly before relying on them in a live scenario.
05Should you use Make or n8n for D7SMS?
It depends on the criteria that matter to your team rather than on the app. On Make, D7SMS gives you three action modules, Send SMS, Check Balance and Make an API Call, and it is available on every plan including Free. The same app often has an n8n node as well, so compare the editor, the plan that fits your volume and what your team already knows. Check on each side which D7SMS actions are available before you decide.
Same platform

Other docs you might need on this stack.

Browse all integrations