SMSAdvert
MessagingConnect AI agents to SMSAdvert, a Romanian SMS platform from Synaptech Services. Agents send text messages immediately or schedule them into a future delivery window so customer notifications go out over the SMSAdvert network or your connected Android devices.
What This Integration Enables
SMSAdvert publishes exactly one API endpoint with seven parameters, and this connector covers all seven. Two actions is the complete documented surface, not a partial build. There is no balance endpoint, no sender ID endpoint, no contacts or groups endpoint, and no delivery report lookup anywhere on the vendor's site. Read that as a description of the product rather than as a shortcoming. SMSAdvert is a Romanian sender operated by Synaptech Services, trading since 2014, and what it sells is getting a message to Romanian handsets. Everything a larger platform would layer on top of that, the audience management and the reporting, is expected to live in the system you already run.
Two of those seven parameters are worth understanding before you build on it. Sending Channel selects between two genuinely different delivery paths: the SMSAdvert network, billed in message credits, or the Android phones you have connected to your account, sending over their own SIMs. A failover toggle can fall back to the billed network when no device is available. That toggle is more delicate than it looks, because a Boolean bound to a flow expression arrives as a string, and in JavaScript every non-empty string is truthy. Read naively, declining failover would switch the billed fallback on. The connector normalizes the value before reading it, and rejects anything that is neither the documented labels nor the two wire values rather than coercing a typo into the billed network. The same instinct applies to the schedule: the vendor's timestamps are Unix milliseconds, and a value small enough to be a seconds timestamp is rejected instead of being silently read as a moment in 1970. Those are the kinds of details that decide whether an automated sender is trustworthy, and they are handled in the connectors layer rather than left for a flow author to discover in production.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Order Notifications From the Store You Already Run
A Romanian merchant runs PrestaShop and wants customers told when an order ships. The agent reads the order, extracts the customer number, and calls Send SMS with the courier reference. Recipients are supplied in international format and duplicates are removed locally before the request goes out, so the recipient count the merchant sees matches what the gateway accepts. Because there is no sender ID parameter on this API, the originator is whatever the account is configured with platform side, which means the message arrives under a consistent identity the merchant does not have to manage per send.
Reminders Sent Over Your Own SIM
A clinic already has a company Android phone and an existing mobile subscription. Rather than buying message credits, the flow sets the sending channel to the connected devices path, so reminders leave over the clinic's own SIM. The agent still resolves the recipient list, applies the per-request ceiling, and validates the body length before issuing anything. Failover to the billed SMSAdvert network stays off unless the clinic has explicitly decided it wants that fallback, because with it on, a phone that happens to be offline quietly converts a free send into a billed one.
A Callback That Closes the Loop the API Cannot
There is no delivery report lookup on this API, so the outcome has to come to you. The agent supplies its own delivery report URL on the send, and a second flow receives the callback, matches it to the stored message ID, and writes the result onto the record in Google Sheets that operations actually reads. Anything that arrives as an error map, a field name paired with a message, is raised as a real failure rather than passing as a success, because this gateway can report failures on an otherwise healthy response. The reporting layer the vendor does not ship gets assembled from the callback and the systems the business already has.
Human-in-Loop Highlight
Schedule SMS does not set a send time. It sets a window. Start Date is the moment SMSAdvert begins attempting delivery and End Date is the moment it stops attempting, and both are submitted as Unix milliseconds. Now list what this API does not have: no cancel endpoint, no delivery report lookup, no balance endpoint, no way to enumerate what is queued. Once a window is open against a recipient list of up to a thousand numbers, there is nothing in the API to close it early, nothing to ask how far it has got, and nothing to check whether the credits are draining. The only signal is the callback you configured, arriving message by message.
That combination is why this connector's gate sits on the schedule rather than on the send. The agent resolves both timestamps into absolute local times, checks that the end genuinely follows the start, counts the deduplicated recipients, and stops: "Ready to schedule 640 reminders. Delivery window opens Thu 14 Aug 07:00 and closes Thu 14 Aug 11:00, Bucharest time. Sending channel: Connected Devices, failover to the SMSAdvert network is off. There is no cancel operation on this API, so once the window opens it stays open until the end time regardless of what happens downstream. Confirm the window and the channel, or reply with a different close time." An immediate send is a mistake you make once. An open delivery window with no cancel is a mistake that keeps happening for four hours, which is exactly the shape of risk a human-in-the-loop step is supposed to catch before it starts.
Agent Capabilities
2 actionsSMS
2- Send SMS Sends a text message immediately to one or more recipients in international format, up to the documented per-request ceiling, with duplicates removed before sending. The body length is validated up front, the sending channel is chosen explicitly between the SMSAdvert network and your own connected Android devices, and a delivery report URL can be supplied so the outcome reaches a system you control.
- Schedule SMS The same send, plus a Start Date from which SMSAdvert begins attempting delivery and an optional End Date after which it stops. The two form a sending window rather than a single fire time, and both accept an ISO 8601 date-time or a Unix timestamp. With no cancel operation published on this API, the window is the commitment, which makes this the operation to put an approval in front of.
Frequently Asked Questions
What can FlowRunner do with SMSAdvert?
FlowRunner agents can run Send SMS and Schedule SMS in SMSAdvert.
Does connecting SMSAdvert to FlowRunner require OAuth?
No. SMSAdvert connects to FlowRunner with an API key, no OAuth flow required.
Can SMSAdvert trigger a FlowRunner workflow automatically?
SMSAdvert doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SMSAdvert
$100 in credits. No card required. Connect in minutes.