Resources · Make integration

Burst SMS Make integrationAutomate Burst SMS with Make.

Can Make send your texts and react to replies without you watching the Burst SMS inbox? The Burst SMS Make integration offers 14 modules: 6 triggers and 8 actions. This page shows how to link your account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Burst SMS Make integration automate?

The Burst SMS Make integration links your Burst SMS account to Make so texts go out, lists stay tidy and replies land somewhere useful without copy and paste. You build a scenario, the automation itself, from modules: each module is one brick, such as a trigger that starts the flow or an action that does one job.

Replies that reach the right person. Watch SMS Reply fires when a customer answers one of your texts, and the next module can hand the message to your CRM or your support tool. For a clinic, that means a patient who answers a reminder is no longer lost in a shared inbox.

A welcome text for every new subscriber. Watch New Contact Added To List starts the scenario as soon as a contact joins a list, and Send SMS writes to that person straight away. An online shop can greet each sign-up this way, which is the scenario built step by step below.

Campaign follow-up based on real behavior. Watch Link Hits tells Make who clicked a shortened link in your SMS, and Add Contact to List or Remove Contact can then move that person to the list that fits. Watch Delivery Receipt closes the loop by reporting what was delivered.

Make does not replace your Burst SMS account: you still need an active Kudosity account and an API key. When a module is missing, Make an API Call reaches the rest of the Burst SMS API with the same connection. The same app often exists in n8n too; the n8n vs Make comparison lays out the differences, and our Make review covers the editor itself. If you would rather learn with guidance, see the Make training.

Connect

How do you connect Burst SMS to Make?

  1. 01

    Copy your API key and client secret

    In your Burst SMS account, open Settings and scroll down to the API settings section. Copy the API key and the client secret shown there. You will paste both into Make in a moment, so keep them at hand.

  2. 02

    Add a Burst SMS module and create the connection

    In your scenario, add any Burst SMS module and click Create a connection. A connection is your Burst SMS account linked to Make once, then reused by every Burst SMS module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the credentials and save

    Enter the API key and client secret you copied, or follow the instructions Make shows on screen, then confirm. Once the connection exists, Make can show in the module fields what it reads from your account, so you pick instead of typing.

First scenario

Your first scenario: text every new contact on a list

GoalWhen a contact is added to a list in Burst SMS, Make sends them a welcome SMS.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for Burst SMS and choose Watch New Contact Added To List.

  2. 02

    Set up the webhook and connection

    Because this trigger is instant, click Create a webhook, then Create a connection and paste your API key and client secret. Burst SMS will now call Make each time a contact joins a list.

  3. 03

    Add Send SMS after the trigger

    Click the + on the right of the trigger and add Send SMS. Map the phone number from the trigger's bundle, the item that flows from one module to the next, and write your welcome text around the contact's name.

  4. 04

    Test with Run once

    Click Run once, then add a test contact with your own number to the list in Burst SMS. Open the bubbles above each module to read the bundles they received and check that the text reached your phone.

  5. 05

    Switch the scenario on

    Save and turn the scenario on. The trigger is instant, so there is no interval to tune: Burst SMS wakes the scenario each time the event happens, and each module run counts as one operation on your plan.

Triggers

Which Burst SMS triggers start a scenario?

6 modules start a scenario when something happens in Burst SMS. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Burst SMS as soon as it happens.

Burst SMS1Watch Delivery Receipt

Watch Delivery Receipt

Instant trigger

In Make“Watches for the delivery receipt to arrive after sending SMS.”

You learn whether each text you sent actually reached the handset, because this trigger passes the delivery receipt to Make once it comes back from the network. That turns a blind send into something you can log and act on.

How it fires
instant, Burst SMS calls Make through a webhook as soon as the receipt arrives.
When to use it
after an appointment reminder or a password code, when you want a record of what was delivered in a sheet or your CRM, or a follow-up by email when a text did not make it.
Watch out
it only reports on SMS that were already sent, so pair it with a sending scenario rather than expecting it to start anything on its own.
Burst SMS2Watch Link Hits

Watch Link Hits

Instant trigger

In Make“Watches for link hits from shorted URL links in SMS being clicked.”

Each click on a shortened link inside one of your SMS becomes a bundle in Make, so you know who showed interest in an offer the moment they tap it. It is the most direct way to measure a text campaign from inside a scenario.

How it fires
instant, Burst SMS calls Make through a webhook as soon as the link is clicked.
When to use it
a promo text for an event, where anyone who clicks should move to a warm list with Add Contact to List or get a call from sales.
Watch out
the documentation only mentions shortened links, so assume a plain URL pasted into the message will not report any click.
Burst SMS3Watch New Contact Added To List

Watch New Contact Added To List

Instant trigger

In Make“Watches for new a contact being added to a list.”

A scenario starts the instant someone joins one of your Burst SMS lists, which makes it the natural entry point for onboarding by text. Every new member flows into Make as a bundle.

How it fires
instant, Burst SMS calls Make through a webhook as soon as the contact is added.
When to use it
a new subscriber to your VIP list should get a welcome message through Send SMS and land in your CRM at the same time.
Watch out
if the same scenario also adds contacts to that list with Add Contact to List, it will wake itself up again, so write to a different list.
Burst SMS4Watch SMS Received to Virtual Number

Watch SMS Received to Virtual Number

Instant trigger

In Make“Watches for SMS replies to a specific virtual number.”

Messages sent to one specific virtual number reach Make on their own, so a number printed on a flyer or a shop window can feed a scenario directly. You choose which number to watch when you set the trigger up.

How it fires
instant, Burst SMS calls Make through a webhook as soon as the text arrives.
When to use it
a dedicated number for bookings or quote requests, where each incoming text should open a ticket or a deal for the right team.
Watch out
it only covers the number you selected; with several virtual numbers, build one trigger per number or use Watch SMS Receive to Inbox instead.
Burst SMS5Watch SMS Receive to Inbox

Watch SMS Receive to Inbox

Scheduled trigger

In Make“Watches for SMS to be received in the inbox.”

Everything that lands in your Burst SMS inbox can be picked up by Make and sent on to the tool your team actually reads, such as a shared channel or a helpdesk. It is the broad net, as opposed to the number-specific trigger.

How it fires
scheduled, Make checks Burst SMS on the scenario's schedule, every 15 minutes by default.
When to use it
when replies do not need an answer within seconds and you want one scenario that gathers every inbound text in one place.
Watch out
on the Free plan the shortest interval is 15 minutes, so a message can wait until the next check; switch to an instant trigger when speed matters.
Burst SMS6Watch SMS Reply

Watch SMS Reply

Instant trigger

In Make“Watches for replies to SMS.”

When a contact answers one of your outgoing texts, Make gets that reply right away, which lets a two-way conversation continue in another tool. Confirmations like YES or STOP can be routed before anyone reads them by hand.

How it fires
instant, Burst SMS calls Make through a webhook as soon as the reply comes in.
When to use it
a reminder that asks the customer to confirm, where the answer should update the booking or alert the person in charge.
Watch out
it listens to replies to messages you sent; a brand new inbound text on a virtual number belongs to Watch SMS Received to Virtual Number.
Modules

What can Make do in Burst SMS?

Burst SMS gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Burst SMS1

Add Contact to List

Action

In Make“Adds or updates a contact on a list found in CONTACTS.”

Your contact ends up on the right Burst SMS list without manual import, and if they already exist their details are refreshed instead of duplicated. It keeps your audiences in sync with the tools where people actually sign up.

When to use it
a form submission or a new customer in your shop should join the list your next campaign will target.
Watch out
adding to a list watched by Watch New Contact Added To List restarts that other scenario.
Burst SMS2

Format Number

Action

In Make“Formats and validates a given number.”

A phone number typed any old way comes out formatted and checked, so the next module sends to something valid. It saves failed texts caused by a missing country code or stray spaces in a form field.

When to use it
right before Send SMS or Add Contact to List, whenever numbers come from a web form, a spreadsheet or a CRM you do not fully control.
Watch out
add a filter after it so a number that fails validation stops there instead of reaching the send step.
Burst SMS3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the Burst SMS API offers that no listed module covers can still be reached, using the connection you already set up. It is the escape hatch of this integration when you outgrow the ready-made modules.

When to use it
you need an endpoint of the Burst SMS API that none of the 14 modules exposes and you are comfortable reading its API documentation.
Watch out
you write the request yourself, so test it with Run once on a harmless call before plugging it into a live flow.
Burst SMS4

Remove Contact

Action

In Make“Removes a contact from one list or all lists.”

People who unsubscribe or churn stop receiving texts, because this module takes them off one list or off every list at once. It is how your opt-outs in other tools become real in Burst SMS.

When to use it
a customer cancels, answers STOP through Watch SMS Reply, or unsubscribes from your emails, and must leave your SMS audiences too.
Watch out
choose between one list and all lists carefully; removing from all lists is the safer choice for an opt-out.
Burst SMS5

Send SMS

Action

In Make“Sends one SMS text message.”

One text goes to one person, built from whatever the earlier modules gathered: a name, an order number, a time slot. This is the module most scenarios end with.

When to use it
a personal message triggered by an event, like an order confirmation, a visit reminder or the welcome text of the scenario above.
Watch out
placed after a module that returns many bundles, it sends one text per bundle, and each send counts as an operation on your plan.
Burst SMS6

Send SMS to List

Action

In Make“Sends an SMS text message to everyone on a specific contact list.”

A whole contact list receives the same message from a single module run, so a broadcast takes one step instead of one per recipient. Your list in Burst SMS does the targeting.

When to use it
a store closure, a flash sale or an event update that every member of a list should read, launched when a row or a status changes elsewhere.
Watch out
there is no per-person wording here; when each text must carry a name or a date, loop through contacts with Send SMS instead.
Burst SMS7

Update Contact

Action

In Make“Updates a contact.”

Details you change in your CRM or shop show up on the matching Burst SMS contact, so your texts never greet someone by an old name or reach a number they no longer use.

When to use it
a customer edits their profile or a sales rep corrects a phone number, and the SMS side should follow without a second edit.
Watch out
run the number through Format Number first when it comes from a free-text field, otherwise a badly typed value overwrites a good one.
Burst SMS8

Get SMS Record

ActionIn the docs only

Going by its name, this module fetches the record of one SMS so later modules can use it; the Burst SMS documentation gives it no description, so treat that as the likely role rather than a promise.

When to use it
when a trigger hands you a message reference and you want the full record before logging it or making a decision.
Watch out
run it once with Run once and read the returned bundle to see exactly which details you get before you map anything.
Need help

Need help automating Burst SMS with Make?

A person reads every message.

FAQ

Burst SMS and Make: frequently asked questions

01Is the Burst SMS Make integration free?
Yes, on the Make side. Burst SMS is a standard app, available from the Free plan, like the 3,000+ standard apps. The Free plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the limit on active scenarios. Usage is counted in operations, one per module run on one bundle. The texts themselves are billed by your Burst SMS subscription, not by Make.
02What does it take to connect Burst SMS to Make?
It takes an active Kudosity account and an API key, as the Make documentation states. In Burst SMS, open Settings, scroll to API settings and copy the API key and the client secret. In Make, add a Burst SMS module, click Create a connection, give it a name if you like and paste both values. For an instant trigger, Make asks you to click Create a webhook before creating the connection. The connection is then shared by every Burst SMS module in your scenarios.
03Do the Burst SMS triggers in Make react in real time?
Five of the six do. Watch Delivery Receipt, Watch Link Hits, Watch New Contact Added To List, Watch SMS Received to Virtual Number and Watch SMS Reply are instant: Burst SMS calls Make through a webhook as soon as the event happens. Watch SMS Receive to Inbox is scheduled instead, meaning Make checks the inbox on the scenario's schedule, every 15 minutes by default and never more often than every 15 minutes on the Free plan. Paid plans allow checks every minute.
04What if a Burst SMS module is missing in Make?
Use Make an API Call. It calls any endpoint of the Burst SMS API with the connection you already created, so you are not limited to the 14 listed modules. You do need to read the Burst SMS API documentation to shape the request. The Make documentation for this app also warns that its content is AI-generated from the vendor documentation and may contain mistakes, so check important details with Burst SMS directly before you rely on them.
05Make or n8n for Burst SMS: which one fits?
It depends on the tools you already use. On Make, Burst SMS comes with 14 ready modules, 6 of them triggers, plus Make an API Call for the rest of the API, and it works from the Free plan. The same app often has an n8n node as well, so compare the exact triggers and actions each tool offers for the job you have in mind, then choose the editor your team is most comfortable maintaining. The comparison page linked above goes through the criteria.