- Home
- Resources
- Integrations
- Burst SMS
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 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.
How do you connect Burst SMS to Make?
- 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.
- 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.
- 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.
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.
- 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.
- 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.
- 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.
- 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.
- 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.
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.
Watch Delivery Receipt
Instant triggerIn 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.
Watch Link Hits
Instant triggerIn 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.
Watch New Contact Added To List
Instant triggerIn 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.
Watch SMS Received to Virtual Number
Instant triggerIn 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.
Watch SMS Receive to Inbox
Scheduled triggerIn 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.
Watch SMS Reply
Instant triggerIn 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.
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.
Modules index
Add Contact to List
ActionIn 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.
Format Number
ActionIn 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.
Make an API Call
ActionIn 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.
Remove Contact
ActionIn 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.
Send SMS
ActionIn 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.
Send SMS to List
ActionIn 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.
Update Contact
ActionIn 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.
Get SMS Record
ActionIn the docs onlyGoing 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.
Need help automating Burst SMS with Make?
A person reads every message.