Skip to content

Turbo Notify in Make

Turbo Notify has an app on Make with eight modules. Send a text message, Send a media message and Reply to a message send a message, Get a message status reads the delivery status of one, List groups lists the groups your number is in, Watch new messages and Watch events start a scenario when a message or an event arrives, and Make an API call calls any other endpoint of the Turbo Notify API with your key. You send from your own WhatsApp number and need a Turbo Notify account. The app connects with your own API key.

  • A Turbo Notify account with a connected number (quickstart).
  • A Make account in the US region (the address in your browser starts with us2.make.com). Make has not approved the app yet, so it is not in Make’s app search. It installs from an invite link, in step 1 of Connect, and the link works only in that region.
  • An API key created in API Keys (opens in a new tab) with the AI agent (MCP) template. The template selects the five scopes below and one more that the app does not use. To keep the key tighter, select only the scopes of the modules you use.
ModulesUseScope the key needs
Send a text message, Send a media message, Reply to a messageSend a text, a file or a replymessages:send
Get a message statusRead the status of a message you sentmessages:read
List groupsList the groups of a numbergroups:read
Watch new messages, Watch eventsStart a scenario on a message or an eventevents:read
The Number list of the seven modules that have it (all but Make an API call)Pick your number from a listnumbers:read
Make an API callCall any other endpoint of the APIThe scope of that endpoint

A module whose scope is missing fails with a sentence that names the scope.

  1. Open the invite link of the app (opens in a new tab) while signed in to your Make account, choose your organization and confirm. Make answers “Turbo Notify installed successfully”.
  2. Create a scenario, click the plus sign and search for Turbo Notify. Pick a module.
  3. Create the connection with your key (next section).
  4. Fill in the module. In Number, pick your number from the list (it shows the alias and the name), or turn on Map to use main, an alias or a num_ ID from an earlier step. In Send to, choose Phone number (with the country code) or Group and pick the group from the list, which comes from your number; with Map you can use a Group ID from List groups. The optional Idempotency key makes a send that runs twice create one message, when both runs carry the same value.

The connection needs only your API key. In the module, click Add next to Connection, give the connection a name and paste the key in the API key field. It is the only field.

Make checks the key when you save. A wrong key is refused with “The API key was not accepted. Check it under API keys in your Turbo Notify dashboard.” A valid one shows your plan beside the connection name (Free, Lone Wolf, Business or Custom).

Treat the key like a password. If it leaks, the most it can do is what its scopes allow, and you revoke it in API Keys (opens in a new tab) without touching anything else.

Start with Send a text message. In a scenario with that one module, choose Phone number, type your own number in international format (+ and the country code, no spaces) and a one-line text, then click Run once. The message arrives on your phone and the module returns its Message ID. The module answers as soon as Turbo Notify accepts the message; whether it was delivered comes later, and Get a message status reads it from that ID.

Then a trigger. Add Watch new messages or Watch events, right-click the module and under Choose where to start keep From now on on the first run. Make refuses Run once until a start is chosen, and the other options return what Turbo Notify already holds, which can be a long history. With From now on, the first run answers that the module did not return any new data. That is the expected result. Send a message to your number from another phone, then run again or wait for the schedule: each new message arrives as one bundle (the item Make passes to the next module).

On the Free plan of Make, a scheduled scenario checks every 15 minutes at best.

List groups returns one bundle per group. Add the name in Name contains to narrow it.

When a module fails, Make shows the code and one sentence that says what to do, for example when the key lacks a scope or the Number is not found.

To change the key, create a new one in API Keys (opens in a new tab), open the connection in Make, paste the new key and revoke the old one.

  • Not in Make’s search yet. Make has not approved the app (the review was requested on 11 November 2026). Until it does, the app installs only from the invite link, in a Make account in the US region.
  • A number connected like WhatsApp Web. Turbo Notify links your own number as a linked device, the same way WhatsApp Web does. It is an independent service, not affiliated with Meta, and it does not use the WhatsApp Business Platform API. WhatsApp decides on restrictions, and a number can be restricted whatever the pace. The practices that keep it healthy are in Protect your number.
  • One message at a time. Your number sends one message at a time, a few seconds apart. A message that waits more than 5 minutes is marked failed with message_timeout (it may still arrive), so a run that sends dozens of messages in a row can fail on the last ones. Split a long list over several runs. On a Free-plan number, a second send that comes closer than the plan allows is refused with send_rate_spacing, and Make shows “Messages are going out faster than this number allows. Wait a few seconds and run it again.” (see Rate limits).
  • Your plan’s quota and pace apply to every message a scenario sends, as to any other send. See Rate limits.
  • The Watch modules poll. They read GET /v1/events each time the scenario runs, so a message starts the scenario at the next run, not the moment it arrives.
  • A message that quotes another one arrives as the “Message replied” event and does not start Watch new messages. Use Watch events with the “Message replied” type for those.
  • Groups. Sending to a group needs the Business plan. When nothing matches, List groups still passes one empty bundle to the next module, so add a filter on Group ID (Exists) before a step that uses it.
  • Not tested. An event that becomes visible late, after the scenario already moved past it, can be missed; how often that happens was not tested, because a burst of events could not be produced. A burst of events within seconds was not tested either.