SMS Everyone
MessagingConnect AI agents to SMS Everyone, an Australian SMS gateway for campaign-based messaging. Agents send and schedule campaigns, pause, resume, or cancel them, retrieve delivery receipts and replies, and manage recipient lists and opt-outs so Australian SMS programs stay controlled end to end.
What This Integration Enables
SMS Everyone is an Australian gateway operated by SMS Everyone Pty Ltd in Victoria, trading since 2014, and it is the connector on this list built around the idea that a campaign is a thing with a life rather than an event that happens once. Nineteen actions cover a single REST API, and six of them exist purely to reach a campaign after you have already submitted it: modify it, pause it, resume it, cancel it, ask what state it is in, and read what the carriers said about it. Most SMS gateways offer a cancel for scheduled messages and nothing else. This one gives you a lifecycle, and if you run Australian consumer campaigns where a wrong price or a wrong date is a real commercial exposure, that lifecycle is the reason to be here.
The connector is a complete map of the vendor's REST generation, all seven routes and all nineteen of their documented actions, and the older compatibility API that carries the username and password as URL query parameters is deliberately not built. Its operation set is a strict subset with no stored lists and no delivery reports, and mixing the two would mean two credential transports for one account. Authentication is HTTP Basic with a username and password the vendor issues by email at setup. There is no API key and no token anywhere on this vendor, which is unusual in this category and worth knowing before somebody goes looking for one in the panel.
A few operational facts shape how flows should be written. Sending is capped at 1000 destination numbers per call, and larger sends are assembled by calling repeatedly with the same Reference, which merges the parts into one campaign. That merging behavior is what makes a partial pause possible at all. The originator is chosen per message rather than configured once, and the API exposes no endpoint that enumerates the originators registered to an account, so the value comes from the email the vendor sent at signup and is case sensitive. Alphanumeric originators must be ACMA-registered in Australia and are not available in New Zealand. There are no triggers on this connector: SMS Everyone can forward inbound replies to a URL of yours, but the vendor's own instruction for setting it up is to contact them, and the URL is a single per-account setting with no route to create, read, update, or delete it. Get Replies is the pull mechanism the vendor recommends instead, and it has a consuming behavior described below that a flow must be built around.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Catching a wrong price before the second half of the list
A retailer sends a Saturday promotion to 40,000 Australian customers, assembled as forty calls sharing one Reference. Twenty minutes in, a customer service reply flags that the advertised price is wrong. The agent calls Get Campaign Status, sees the campaign is still Running, and calls Pause Campaign. Whether that catches anything depends on how much is left, because this vendor dispatches at well over 1000 messages per second and a pause realistically only holds a campaign that has not started or one that is very large. The agent then calls Get Delivery Status to establish exactly how many recipients already have the wrong price, posts that number to Slack with the corrected body ready, and waits. The count is the deliverable. Nobody can decide what to do about a mistake without knowing its size.
Replies that reach the CRM instead of a mailbox
Customers answer the promotion. Some ask a question, some opt out in words rather than by keyword, and a few say something that needs a human. The agent polls Get Replies on a schedule, which returns inbound messages with the originating number and the campaign reference. Anything containing an unsubscribe intent goes to Add Opt-Outs immediately, because suppression is the reversible-in-practice direction and does not need a person. Questions are matched back to the customer record in HubSpot and opened as tasks. The important build detail is that Get Replies called with no filters returns everything received since the last call and permanently marks it retrieved, so it never comes back. A flow that reads it must persist what it read in the same step, or supply Days or a date range to read without consuming.
Lists maintained by the systems that own the truth
A membership platform is the source of who should receive what. The agent reconciles it against SMS Everyone nightly: Get Lists for the current stored lists, Get List Details for the numbers in each, then Add Numbers To List and Remove Numbers From List for the differences. The gateway de-duplicates additions and washes them against the opt-out database, so a member who unsubscribed by SMS is not silently re-added by a source system that never heard about it. Delete List is not part of the reconciliation. Removing a whole list is a decision with no undo, and the agent raises it as an automation exception rather than acting on a diff that says a list is now empty.
Human-in-Loop Highlight
The gate on SMS Everyone is Resume Campaign, which sounds like the least consequential action in the set and is actually the sharpest. Resume does not continue a campaign at the pace it was going. The vendor's own documentation is explicit: if the campaign's scheduled time has already passed, every unsent message goes immediately. So a campaign paused at 09:20 because somebody spotted a wrong expiry date is not sitting there waiting to be nudged forward. It is a loaded batch, and resuming fires all of it at once. Compounding this, the pause was the only brake the account has, and it worked in the first place only because enough of the campaign had not started. Pause it again after a resume and you are unlikely to catch anything, because this vendor dispatches at well over 1000 messages per second.
So the agent restores everything a person needs and refuses to touch the switch. It has already paused, already read Get Delivery Status to count who received the original, already prepared the corrected body and confirmed with Modify Scheduled Campaign that the destination list is not something this route can change. What it posts is the state of play with the consequence spelled out: "Campaign SPRING-4, paused at 09:22. 11,480 of 40,000 delivered with the wrong expiry. 28,520 unsent. Corrected body is staged. Resuming releases all 28,520 immediately because the scheduled time has passed, and a second pause is unlikely to catch anything. Resume with the correction, or cancel and rebuild?" A person answers that in the Flow conversation, and the answer is what runs Resume Campaign or Cancel Campaign.
That is the shape human-in-the-loop takes under Orchestration as a Service. The agent held the line, gathered the count, and staged the fix, which is all the work. The remaining decision is a commercial one about 28,520 people who are about to hear from you in the next few seconds, and it is not improved by being made faster. Two neighboring actions deserve the same care. Remove Opt-Outs resubscribes numbers into every future campaign, which reverses a decision the recipient made and the agent did not witness. Add Credits is a reseller facility that moves real money into a sub-account balance, and the vendor gates it further: the credentials must belong to the sub-account being topped up, and the account must be pre-approved.
Agent Capabilities
19 actionsMessaging
1- Send SMS Campaign Sends or schedules a message to up to 1000 destination numbers, to stored lists, or to both at once. Recipients are de-duplicated and washed against the opt-out database at send time. Returns the campaign identifier, recipient count, segment count, and credit cost. Larger sends are assembled by calling repeatedly with the same Reference, which merges the parts into one campaign.
Campaigns
5- Modify Scheduled Campaign Changes the message text, originator, or send time of a campaign that has not started. The destination list cannot be changed this way, which is the constraint that decides whether a correction is possible or a rebuild is required.
- Cancel Campaign Cancels a scheduled campaign so its remaining messages are never sent. The clean exit when a correction is not worth attempting.
- Pause Campaign Pauses a campaign before or during its send. Realistically this catches a campaign that has not started or one that is very large, because the vendor dispatches at well over 1000 messages per second.
- Resume Campaign Resumes a paused campaign. If its scheduled time has already passed, every unsent message goes immediately rather than resuming at the original pace.
- Get Campaign Status Returns the campaign's lifecycle state as Scheduled, Running, Paused, or Deleted. The first read in any intervention, because it determines which of the other campaign actions will do anything at all.
Delivery Reports
1- Get Delivery Status Returns carrier delivery receipts for a campaign, for every recipient or for one specific number. Each entry carries a status identifier covering delivered, failed, rejected, expired, aborted, queued, dispatched, and no receipt received, plus the carrier's own error code where the message failed. The vendor documents polling this no more often than once a minute, and recommends five.
Replies
1- Get Replies Retrieves inbound SMS replies, optionally filtered by number of days, a date range, or a single originating number. Called with no filters it returns everything received since the last call and permanently marks those replies as retrieved, so they never come back. Supply Days or a date range, or enable Test Mode, to read without consuming.
Account
2- Get Account Settings Returns the remaining credit balance, the account identifier, and whether the account may send Unicode and may send outside Australia. New accounts commonly have international sending off, which is worth checking before a campaign assumes otherwise.
- Add Credits Tops up a sub-account's credit balance and returns the new balance. This is a reseller facility: the configured credentials must belong to the sub-account being topped up, and the account must be pre-approved by the vendor.
Opt-Outs
3- Add Opt-Outs Adds mobile numbers to the account's opt-out database, unsubscribing them from all future campaigns. The direction an agent can take without asking, because it only ever reduces contact.
- Remove Opt-Outs Removes numbers from the opt-out database, resubscribing them. This reverses a decision the recipient made, which makes it a consent judgment rather than a data fix.
- List Opt-Outs Returns every opted-out number with the date it was added, the reason, and the text of the reply that opted it out where that is how it happened. The reply text is the evidence, which is what makes an opt-out here auditable rather than just a flag.
Lists
6- Get Lists Returns every stored list with its identifier, name, recipient count, parent-account flag, and whether a campaign is scheduled against it. Deleted lists are shown only on request.
- Get List Details Returns one list with every mobile number it contains. The read that makes a reconciliation against a source system possible.
- Create List Creates a stored list, optionally populated at creation time, and returns its identifier.
- Add Numbers To List Adds numbers to an existing list. The gateway de-duplicates them and washes them against the opt-out database, so opted-out numbers are not added back by an upstream system that never heard about the opt-out.
- Remove Numbers From List Removes numbers from a list without deleting the list. The right action for a membership change, as opposed to a teardown.
- Delete List Deletes a list and everything in it. There is no undelete, and a campaign scheduled against it loses its audience.
Frequently Asked Questions
What can FlowRunner do with SMS Everyone?
FlowRunner agents can run Send SMS Campaign, Modify Scheduled Campaign, and Cancel Campaign in SMS Everyone, plus 16 more actions.
Does connecting SMS Everyone to FlowRunner require OAuth?
No. SMS Everyone connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can SMS Everyone trigger a FlowRunner workflow automatically?
SMS Everyone doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SMS Everyone
$100 in credits. No card required. Connect in minutes.