Resources · Make integration

D7 WhatsApp Make integrationAutomate D7 WhatsApp with Make.

Can Make send your WhatsApp messages through D7 on its own? Yes: the D7 WhatsApp Make integration gives you 6 action modules, from text messages to media and a balance check. This guide walks an ops or support lead through the connection, then a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the D7 WhatsApp Make integration do for you?

The D7 WhatsApp Make integration links your D7 account to Make so a scenario, the automation you build in Make, can send WhatsApp messages without you typing them. Each step of that scenario is a module, one brick that does one job, and D7 WhatsApp brings 6 of them, all actions.

Order updates that leave on their own. Another app in your stack starts the scenario, say a form or a shop, and Create a Utility Text sends the message to the customer. You write the flow once and stop copying phone numbers by hand.

Campaign messages from a list. When a contact enters a list in your CRM, Create a Marketing Text or Manage a Marketing Media carries the promotional side. D7 requires registered message templates on your account, so prepare them in D7 before Make sends anything.

A guard on your credit. Put Check Balance at the start of a busy flow to read where your D7 account stands before a batch goes out.

Know the edges before you start. The app has no trigger, so something else has to start the scenario: another app, or the schedule Make sets on the first module. The Make documentation also lists the modules by name only, with no description, and warns that its D7 page is AI-generated and may contain mistakes. Open each module and read its fields before you rely on it. If you are weighing tools, the same app often has an n8n node too; the n8n vs Make comparison lays out how the two differ, and the Make pricing page explains what your plan counts.

Connect

How do you connect D7 WhatsApp to Make?

  1. 01

    Get your API token from D7

    In your D7 dashboard, open the API tokens section, create a new application, give it a name and generate a token. Copy it right away. Your D7 account needs a verified WhatsApp number and registered message templates first.

  2. 02

    Add a D7 WhatsApp module in Make

    In your scenario, add any D7 WhatsApp module and click Create a connection. A connection is your D7 account linked to Make once, then reused by every D7 module. The Connection name field is optional.

  3. 03

    Paste the token and save

    Enter the credentials you copied from D7, or follow the instructions Make shows on screen, then save. The module can now use your account, and the next D7 module you add picks the same connection from the list.

First scenario

Your first scenario with D7 WhatsApp

GoalWhen a new record lands in another app, Make sends a WhatsApp text to that contact through D7.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since D7 WhatsApp has no trigger, pick the app that holds your contacts, such as a form tool or your shop.

  2. 02

    Set up the starting module

    Connect that first app and fill its fields. Once the connection exists, Make lists what it can read, so you choose the form or the list from a menu instead of typing an ID.

  3. 03

    Add Create a Utility Text

    Click the + on the right of the first module, search for D7 WhatsApp and pick Create a Utility Text. Choose your connection, then map the phone number and the values from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, a bundle being one item passed along, here one contact. Send the test to your own number first.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default on a new scenario, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

The 6 D7 WhatsApp modules, one by one

D7 WhatsApp gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

D7 WhatsApp1

Check Balance

ActionIn the docs only

Check Balance lets a scenario look at your D7 account before it spends anything, which is what its name points to. The Make documentation gives it no description, so run it once and read the bundle it returns.

When to use it
as the first D7 step of a flow that may send a large batch, followed by a filter on what it returned.
Watch out
it sends nothing by itself; it only informs the modules that come after it.
D7 WhatsApp2

Create a Marketing Text

ActionIn the docs only

With Create a Marketing Text, a promotional WhatsApp message goes out from D7 without anyone typing it. Your D7 account needs registered message templates before it can send, so set those up first.

When to use it
a lead joins a campaign list in your CRM and should get the offer tied to that list.
Watch out
the Make documentation lists no fields for it, so open the module and check what it asks before you map anything.
D7 WhatsApp3

Create a Utility Text

ActionIn the docs only

Create a Utility Text is the module to reach for when the message serves the customer rather than sells to them, as its name suggests: a confirmation, a reminder, a status. Registered templates in your D7 account are a prerequisite here too.

When to use it
an order, a booking or a ticket changes in another app and the customer should hear about it on WhatsApp.
Watch out
test with Run once on your own number, because a real run sends a real message.
D7 WhatsApp4

Make an API Call

ActionIn the docs only

Make an API Call opens the rest of the D7 API to your scenario: any endpoint the five other modules do not cover, called with the same connection. You keep one D7 account link and add no extra login.

When to use it
you need a D7 feature that no listed module offers and the D7 API documentation describes it.
Watch out
this module asks you to write the request yourself, so keep the D7 API reference open while you fill it.
D7 WhatsApp5

Manage a Marketing Media

ActionIn the docs only

Manage a Marketing Media covers the media side of your promotional messages, an image or a file that goes with the offer, going by its name. Make documents it by name only, so the exact actions it offers show up once you open it.

When to use it
a campaign needs a visual next to the text sent by Create a Marketing Text.
Watch out
on the Make Free plan, files are limited to 5 MB, which matters as soon as media travels through the scenario.
D7 WhatsApp6

Upload a Utility Media

ActionIn the docs only

Upload a Utility Media puts a file in D7 for your service messages, judging by its name, such as a receipt or a document the customer expects. Read it as the media partner of Create a Utility Text, and open it to see the options it really offers.

When to use it
a PDF is produced in another app and should reach the customer alongside a WhatsApp update.
Watch out
the file counts toward the 512 MB of data transfer on the Make Free plan.
Need help

Need help automating D7 WhatsApp with Make?

A person reads every message.

FAQ

Questions people ask about D7 WhatsApp and Make

01Is the D7 WhatsApp Make integration free?
Yes, on the Make side. D7 WhatsApp is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits per month. Your D7 account is separate: D7 bills its own subscription, and its pricing page gives the details.
02What do you need to connect D7 WhatsApp to Make?
An active D7 account with a verified WhatsApp number and registered message templates. In the D7 dashboard, open the API tokens section, create an application, name it and generate a token, then copy it. In Make, add a D7 WhatsApp module, click Create a connection, optionally name it, and paste the token. That connection then serves every D7 WhatsApp module in your scenarios, so you set it up once and never paste the token again.
03Does the D7 WhatsApp Make integration react in real time?
No, because the app has no trigger module. A scenario that sends D7 messages has to be started by something else: a trigger from another app, such as a form or a shop, or the schedule you set on the first module, every 15 minutes by default. If that first app offers an instant trigger, it calls Make through a webhook as soon as its event happens, and the D7 message follows.
04What if a D7 WhatsApp module is missing in Make?
Use Make an API Call. It calls any endpoint of the D7 API from your scenario with the same connection, so a feature the five other modules do not list stays within reach. Keep in mind that the Make documentation for D7 WhatsApp describes the modules by name only and flags its content as AI-generated, so check the D7 documentation or contact D7 when a detail matters. Each call through it counts as one operation, like any other module.
05Should you use Make or n8n for D7 WhatsApp?
It depends on where your team already builds. The same app often has an n8n node too, so check whether one exists before you pick a side. On Make, D7 WhatsApp gives you 6 action modules and no trigger, including Make an API Call for anything else. The simplest choice is usually the tool that already runs your other automations, so the WhatsApp step joins flows you maintain. Whichever you choose, test the flow on your own number before customers receive anything.