Kudosity (Burst SMS)
MessagingConnect AI agents to Kudosity, the Australian business messaging platform formerly known as Burst SMS. Agents send and schedule SMS, manage contact lists, lease virtual numbers, and pull delivery and reply reports so campaigns and transactional texts stay measurable.
What This Integration Enables
Kudosity is the Australian messaging platform that traded as Burst SMS and then Transmit SMS, and the API it still publishes is the Transmit SMS one. The catalog slug stays burst-sms because that is the name this integration was catalogued under. What the API is built around is the recipient list. Almost everything here orbits it. Lists carry a first name, a last name and up to ten custom fields, and contacts are added and updated against those fields. A send can be pointed at a whole list in one parameter, keywords subscribe inbound senders to a list automatically, and the reporting reads back per recipient and per list. If your messaging program is a set of curated audiences that people join and leave, this connector fits the shape you already have.
The second thing worth designing around is the inbound side, because it is where the money decision lives. A dedicated virtual number is what receives replies and gives every send a consistent sender ID, and leasing one starts a recurring charge. Keywords attach to that number: an inbound message whose first word matches a keyword is captured against it, the sender can be subscribed to a list automatically, and a welcome or members reply can go back without a flow being involved at all. Around that sit the reporting actions, which are unusually granular for a gateway of this size. Get Campaign Statistics gives the aggregate counters, Get Campaign Recipients walks the individual recipients, Get SMS Delivery Status resolves one recipient's final message text with personalization and tracked links substituted, and Get Activity Report and Get Message Report cover the account level view over a window. Kudosity delivers receipts and inbound messages to a callback URL set per message or in account settings rather than through any webhook subscription route, so this connector ships no triggers and the response actions are the polling path.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A list that stays clean without anyone maintaining it
Signups arrive from a form and from Shopify checkout, in whatever format the customer typed. The agent calls Format Number on each one with the destination country code, which strips spaces and punctuation, returns the E.164 form, the line type and a validity flag, and screens out the landlines and the typos before either becomes a failed send. Valid numbers go to Add Contact To List with their custom values written into the slots the list declares. When someone replies STOP, the agent calls Opt Out Contact rather than Remove Contact, because an opted-out contact stays on the list and is excluded from sends, while a removed contact is simply absent and the next import will add them back.
Inbound keyword capture that runs without a flow
A campaign invites customers to text JOIN to the clinic's dedicated number. The agent calls Create Keyword on that number, points it at the subscription list, and sets the welcome message for new senders and the members reply for people already on the list. From then on the capture happens at the platform: someone texts JOIN, they are subscribed, and they get an immediate answer. The flow's job shrinks to reading Get Responses By Message Or Keyword on a schedule for anything that was not a keyword, which is where the actual questions are, and routing those to a person in Slack.
A campaign reconciled against what recipients actually received
After a send, Get Campaign Information returns the recipient count, the cost, the part count and the message template as submitted, with its placeholders still unresolved. Get Campaign Statistics adds the counters: delivered, pending, hard and soft bounces, replies, opt-outs and tracked link hits. Hard and soft bounces mean different things about a number and the agent routes them apart, queueing soft bounces for a retry and marking hard bounces for removal. For any recipient whose outcome is disputed, Get SMS Delivery Status returns the sender ID used, both timestamps, the current status and the final text that specific person received, personalization resolved. That last one is the difference between a report and evidence.
Human-in-Loop Highlight
Custom fields on a Kudosity list are positional, and that is the fault line on this connector. A list declares up to ten custom field names, and those names are written into slots field_1 through field_10 in the order they are supplied. Every subsequent write follows the same rule: Add Contact To List and Update Contact place their values positionally into those same slots. Two things follow. First, if the values array a flow assembles does not line up with the order the list was created in, every contact gets a perfectly stored record with the data in the wrong fields, and nothing anywhere reports an error. Second, Add Fields To List writes names positionally too, so supplying a name for a slot already in use renames that field. The stored values do not move. Only the label does, which means a rename quietly redefines what ten thousand existing records mean.
A personalized send built on top of that is unrecallable, and the connector will not warn you, because there is nothing wrong with the request. Worse, the obvious place to look does not help: Get Campaign Information returns the template with its placeholders unresolved, so reading it back shows you the message you wrote rather than the message anyone received. The only way to see a rendered result is Get SMS Delivery Status for one specific recipient. So that is where the agent stops. It sends to a single seed recipient, pulls the resolved text, and posts it: "Here is the message as recipient +61400000000 will receive it: 'Hi Sydney, your Melbourne appointment is confirmed.' The list's custom fields are named suburb, city, appointment_type in slots 1 to 3. Send to the remaining 8,412 recipients, or stop and fix the field order?" A person reads one sentence and catches a transposition that would otherwise reach every customer on the list. Kudosity also returns logical errors inside an HTTP 200 with a code in its own error block, which the connector inspects and raises rather than passing off as success, so the exceptions this gate does not catch still surface as automation exceptions instead of silence.
Agent Capabilities
34 actionsMessaging
5- Send SMS Sends to one or more recipients, to an entire contact list, or both, with up to 500 comma separated numbers in E.164 format. The body accepts up to 612 characters, with part counts that change when Unicode characters such as emoji appear. The send can be scheduled, given a validity window, pointed at per-message delivery receipt, reply and link hit callback URLs, and can carry a tracked short link substituted wherever the placeholder appears.
- Cancel Scheduled SMS Cancels a message scheduled for a future time that has not been dispatched, identified by the message ID returned when it was created. Messages that have already left the platform cannot be recalled, which makes the scheduling window the only place a send can still be stopped.
- Format Number Normalizes a number held in local format into E.164 by combining it with a country code and stripping the spaces, hyphens and other characters that cause delivery failures. Returns the parsed country code, national number, international number, line type and a validity flag, so it doubles as a screening step before a list is built.
- Get Responses By Message Or Keyword Retrieves inbound replies filtered by the message they answer, by keyword, by keyword ID or by the virtual number they arrived on, with at least one of those required. Results can be narrowed to a date range within the last twelve months and default to the last thirty days. The original message option includes the outbound text each reply responds to, which is what makes a reply readable out of context.
- Get Responses By Contact Retrieves the reply history for a single number across every send, so a full inbound conversation with one contact can be reconstructed. Used when a complaint or a dispute needs the whole thread rather than the one message that prompted it.
Contacts and Lists
8- Create List Creates a recipient list under a unique name. First name and last name exist on every list by default, and up to ten additional custom fields can be declared at creation by supplying their names in order, which maps them to the positional slots used by every later write. That ordering decision is made once and constrains everything afterward.
- Add Fields To List Adds or renames custom fields on an existing list, writing the supplied names positionally into the same ten slots. Passing a name for a slot already in use renames that field without moving any stored value, so a rename redefines what existing records mean. Treat this as a schema change rather than a labeling tweak.
- Delete List Permanently deletes a recipient list together with every contact on it. Reporting already generated for sends that used the list is retained, but the contact records themselves cannot be recovered.
- Add Contact To List Adds a contact to a list, writing custom values positionally into the declared slots. A contact already present is ignored rather than updated, so a sync that expects upsert behavior needs the update action instead and should not read a silent ignore as a successful write.
- Update Contact Updates a contact already on a list, replacing the stored name and custom field values, again positionally. Used by an enrichment pass that carries the full value set rather than a partial one, since the write replaces what is there.
- Remove Contact Removes a contact from a single list, or from every list on the account when no list is given, and returns the IDs of the lists it was removed from. Removal is not an unsubscribe: the number carries no record of having objected, so a later import can restore it.
- Opt Out Contact Marks a contact as unsubscribed on one list or across every list on the account, returning the list IDs the opt-out was applied to. Opted-out contacts stay on the list and are excluded from subsequent sends, which is what makes this the correct response to a STOP reply and removal the wrong one.
- Get Bulk Import Progress Reports the progress of a bulk contact import, returning the status with counts of imported, duplicate, skipped and opted-out records. Large imports take time and the upload only confirms the file arrived, so this is where the actual outcome is established rather than assumed.
Reporting
12- Get Account Balance Returns the remaining credit on the account with its currency. Used as the guard before a large campaign, or as a standing low balance monitor that pages a person while there is still time to act.
- Get Lists Returns metadata for every recipient list on the account, including each list's name, creation date, custom field names and active member count, paginated. The custom field names in this response are how a flow discovers the slot order it must write into.
- Get List Returns detailed information about a single list, including its custom field names and, when members are requested, a paginated page of contacts with their names, status and stored custom data. The audit read before a campaign points at that list.
- Get Contact Returns the stored record for one contact on a list, with the name, creation date, subscription status and the values held in the custom fields. Used to check one person's state rather than pulling a page of the list.
- Get Campaign Information Returns summary information about a send: the scheduled time, recipient count, cost, part count, the message template as submitted and aggregate delivery statistics. The template comes back with placeholders unresolved, so this shows the message that was written and not the message anyone received.
- Get Campaign Statistics Returns aggregate counters for a send: total recipients, delivered, pending, hard and soft bounces, replies, opt-outs and tracked link hits. Delivery is confirmed by a handset level receipt or a carrier acknowledgement, and the detail available varies by destination carrier, so treat the counters as the platform's best view rather than a universal truth.
- Get Campaign Recipients Returns a paginated list of the individual recipients of a send with their per-recipient delivery state, optionally restricted to one list, with delivery detail and opt-out records each includable. Used to build the exception queue rather than to read the headline number.
- Get SMS Delivery Status Returns the delivery record for one recipient of one send, including the sender ID used, the scheduled and actual timestamps, the current status and the final message text with all personalization variables and tracked links resolved. This is the only route that shows what a specific person actually received.
- Get SMS Sent Count Returns the total number of message parts sent from the account within a time window, with both timestamps interpreted in UTC. Parts rather than messages, which is the unit that gets billed and therefore the unit worth watching.
- Get Activity Report Returns a paginated log of the individual messages sent from the account between two timestamps, with the text, recipient, sender ID and status for each. Supply a number to narrow the report to one recipient, which is the fastest answer to "what did we send this person".
- Get Message Report Returns a paginated report broken down by message with cost, part count, status and per-message delivery, bounce, opt-out and reply counters, filterable by message type or virtual number. Supplying a list ID also returns the custom data held for each contact on that list. The window must be within thirty days, and with no range only the last day is reported.
- Get Messages Sent To Contact Returns a paginated history of the individual messages delivered to one number, with the message ID, timestamp and delivery status for each. With no date range it covers everything from account registration onward, which makes it the record to pull when someone asks how often they have been contacted.
Numbers
4- Get Numbers Returns the dedicated virtual numbers on the account, or the numbers available to lease, with price, renewal date and status. A dedicated number is what receives inbound messages and gives every send a consistent sender ID, and availability varies by country.
- Get Number Returns the lease detail for one dedicated number held on the account, including its price, next charge date, auto-renewal setting and status. Read this before a renewal decision rather than after the charge.
- Lease Number Leases a dedicated virtual number to the account, either a specific one from the available list or an automatically allocated one, with an optional forward URL for inbound messages. This is billable and starts a recurring charge, so it belongs behind a person rather than inside a provisioning loop.
- Update Number Options Configures how inbound messages on a dedicated number are handled: which list new senders join, the automatic welcome for new senders and the reply for existing members, and where inbound messages are forwarded by email, SMS or HTTP callback. Options left empty are unchanged, so a partial update will not wipe a colleague's configuration.
Keywords
3- Create Keyword Creates a keyword on a dedicated number so inbound messages whose first word matches are captured against it, the sender is optionally subscribed to a list, and a welcome or members reply is returned automatically. Forwarding to an HTTP callback, to email addresses or to mobile numbers can be set at the same time, which moves the capture off the flow and into the platform.
- Update Keyword Updates an existing keyword, identified by its text and the number it belongs to, changing the subscription list, automatic replies, forwarding destinations, activation flag or open and closed status. Closing a keyword stops it capturing inbound messages, which is the clean way to end a campaign without deleting its history.
- Get Keywords Returns a paginated list of the keywords configured on the account with the number each is attached to, its reference, subscription list, automatic replies, forwarding destinations and open or closed status. Restrict to one number to audit what a single line is answering.
Email To SMS
2- Authorise Email Address Authorizes an email address to send through the email to SMS gateway, so mail from that address to a recipient at the gateway domain is delivered as a message. The length can be capped at one to four parts and the send can be bound to a specific dedicated number, which keeps a legacy mail-based workflow inside the same sender identity as everything else.
- Remove Email Address Removes an email address from the authorized list, after which mail from that address is no longer accepted by the gateway. The clean revocation when someone leaves the team and their mailbox still exists.
Frequently Asked Questions
What can FlowRunner do with Kudosity (Burst SMS)?
FlowRunner agents can run Send SMS, Cancel Scheduled SMS, and Format Number in Kudosity (Burst SMS), plus 31 more actions.
Does connecting Kudosity (Burst SMS) to FlowRunner require OAuth?
No. Kudosity (Burst SMS) connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Kudosity (Burst SMS) trigger a FlowRunner workflow automatically?
Kudosity (Burst SMS) doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Kudosity (Burst SMS)
$100 in credits. No card required. Connect in minutes.