Sempico Solutions
MessagingConnect AI agents to Sempico Solutions, an A2P SMS gateway also sold under the Gatum brand. Agents send single, batch, and group campaigns, run HLR and MNP lookups, search sent traffic, and manage contact groups and blacklists so high-volume messaging stays deliverable and accountable.
What This Integration Enables
Sempico Solutions is an A2P SMS gateway and messaging hub operated by Sempico Solutions Group, a UK registered company with engineering and operations in Kyiv, whose platform is also sold under the Gatum brand. The posture of the API tells you what kind of customer it is built for. There are three separate pricing actions returning product prices, account prices, and country prices, plus a country and continent reference list. There is a route that registers sub accounts for resellers. Search Sent Messages returns a per part breakdown carrying the state, the price, and the error code for every part of every message. This is a platform that expects you to reason about per country routing economics, which is a wholesale posture rather than a self serve one, and it is the reason a high volume sender picks it.
The thing that makes this connector genuinely different from every other gateway in the catalog is Preview Message Routing. The account has server side replacement rules, and those rules can rewrite both the sender ID and the message text between submission and transmission. Preview Message Routing is a dry run against them: it returns, per number, the sender ID and text that would actually be transmitted, the part count, and the destination country and network codes. Nothing is sent and nothing is billed. Read that carefully, because the implication is larger than a preview feature usually carries. On this platform, the message your flow composed and the message the recipient receives are not necessarily the same string, and there is exactly one way to find out in advance.
Authentication is a two step exchange rather than a static key: a login and password produce an authorization code, which produces a short lived access token that the connector obtains on the first call of a run and reuses for the rest of it. Revoke Access Token destroys the current token early when you want it gone, and the next action simply obtains a new one. Sending comes in three shapes:
- A single send to up to one hundred recipients, with traffic types across SMS, flash SMS, WAP push, and HLR lookup.
- A batch of differently addressed messages in one package.
- A group addressed campaign with excluded groups, extra individual numbers, personalization placeholders, and a date with start and stop times of day.
Group and campaign identifiers are validated rather than coerced, so a value like a group number with a label attached is rejected outright rather than read as the number, because reading it loosely would silently cancel a campaign exclusion.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A campaign priced and inspected before it exists
A high volume sender runs a promotion across several countries. Before anything is dispatched, the agent calls Preview Message Routing with a representative sample from each destination. What comes back is three useful things per number: the sender ID that will actually be transmitted after the account's rules run, the text as it will actually appear, and the part count. Get Country Prices and Get Account Prices turn that part count into a real number, per destination, at the rates this account is charged rather than at list rates. The campaign that then runs through Send Campaign To Groups is one whose cost and content were both known beforehand. The estimate is written to PostgreSQL next to the actual billed amount from Get Delivery Statistics, so the gap between estimate and invoice is a measured thing rather than a recurring surprise.
Suppression that is checked rather than assumed
The account carries a personal blacklist, and Search Blacklist Numbers returns which of a supplied set of numbers are on it, with the stored comment and the time each was added. A campaign flow reads it against the audience before dispatch rather than trusting that suppression happens invisibly. Numbers that appear are removed from the send and reported, and the stored comment is the useful part, because it usually says why. In the other direction, when a customer replies with a stop request that reaches the business through Zendesk rather than through the gateway, the agent adds the number with Add Numbers To Blacklist immediately and unattended, since moving toward more suppression is never the mistake worth guarding against.
Delivery reconciled per part, not per message
Sempico Solutions ships no trigger, because delivery receipts and inbound messages are forwarded to a URL set in the client cabinet, with no subscription API and no documented payload schema for either. So the connector reads instead of listening, and the read is unusually detailed. Search Sent Messages returns each hit with the destination network, the text, the encoding, the part count, and a per part breakdown carrying state, price, error code, and the time the state last changed. That per part view is what makes a real diagnosis possible: a message where part one delivered and part three failed is a different problem from a message that was rejected outright, and only one of them is worth retrying. Get Delivery Statistics aggregates the same traffic grouped by day, country, operator, or campaign, with delivered percentages and billed amounts. Anything failing at a country or operator level becomes an automation exception in Slack, because a route problem is somebody's job rather than a retry.
Human-in-Loop Highlight
The gate on Sempico Solutions is the difference between the message that was composed and the message that will be transmitted. The account holds server side replacement rules, and they can rewrite the sender ID and the body text. Those rules exist for good reasons, usually to satisfy a destination country's sender registration requirements or to substitute an alphanumeric sender that a particular operator will not carry. But they run after your flow has finished composing and before the handset receives anything, and their effect is invisible to any send call. Preview Message Routing is the one action that reveals it, and its output is a diff waiting to be read: the sender ID that will actually appear, the text that will actually go out, the part count that will actually be billed, per number and per destination network.
So the agent runs the preview and compares. When the transmitted form matches what was composed, it proceeds without asking, because there is nothing for a person to add. When it does not, it stops and shows the difference. Into Slack: "Campaign to 3 groups, 8,400 recipients across 4 countries. Routing preview returns changes on 2 destinations. Germany, 2,140 recipients: sender ID rewritten from ACMESHOP to 447xxxxxxxxx, text unchanged. Poland, 900 recipients: text rewritten, the shortened link was replaced with the full URL, which pushes the message from 1 part to 2 and doubles the billed parts for that destination. Send as transmitted, or hold Poland and Germany while the replacement rules are reviewed?" A rewritten sender ID changes whether a customer recognizes the message as coming from you, and a rewritten body can change what it means. Both are judgments about brand and about spend, and both live with a person.
That is the digital andon cord under Orchestration as a Service, placed on a mismatch rather than on a category of action, which is why it stays quiet on the vast majority of runs and speaks up on exactly the ones that matter. Two other operations deserve naming. Delete Numbers From Blacklist restores messaging to a number somebody suppressed, and it belongs with a person for the same reason the routing diff does. Register Customer Account creates a real sub account with real credentials and is reseller functionality, so it should never be something a flow reaches for on its own. Everything else, sending, previewing, searching, reading prices, and managing group membership, runs unattended, because those are either free, reversible, or the work itself.
Agent Capabilities
22 actionsAccount
3- Get Account Profile Returns the login, contact name, company, phone, email, remaining balance units, and currency for the authenticated account. The balance read that belongs before any large campaign.
- Revoke Access Token Destroys the access token the connector is currently holding. The next action simply obtains a new one, so this is a hygiene operation rather than a disconnect.
- Register Customer Account Creates a sub account with a login, password, responsible person, phone, and email. This is reseller functionality and is rejected on accounts that may not create sub accounts, and it issues real credentials, so it is not something a flow should reach for on its own.
Messaging
4- Send SMS Sends one message to up to one hundred recipients, supporting SMS, flash SMS, WAP push, and HLR lookup traffic types, scheduling by date and time, a validity period, a per message delivery receipt callback URL, and a delivery report flag. Returns each recipient mapped onto the state values of its message parts.
- Send Message Batch Sends several differently addressed messages in one package, each with its own recipients, sender ID, text, type, and schedule. The right shape when one run has to carry genuinely different messages rather than one message to many people.
- Send Campaign To Groups Creates a campaign addressed to whole contact groups, with optional excluded groups and extra individual numbers, and a date plus start and stop times of day. The body supports personalization placeholders, and it returns the campaign identifier.
- Preview Message Routing Runs a dry run against the account's replacement rules and returns, per number, the sender ID and text that would actually be transmitted, the part count, and the destination network codes. Nothing is sent and nothing is billed. The only way to see, in advance, that the transmitted message differs from the composed one.
Reporting
2- Search Sent Messages Searches recently sent traffic by destination network, sender ID, recipient numbers, contact group, time period, traffic type, and delivery state. Each hit carries the destination network, text, encoding, part count, and a per part breakdown with state, price, error code, and the time the state last changed. The per part view is what separates a partial failure from a rejection.
- Get Delivery Statistics Returns aggregated traffic grouped by year, month, week, day, country, operator, or campaign, with delivered percentage, per state counts, part totals, and billed amount. The read behind a monthly reconciliation of messaging spend against messaging outcomes.
Contact Groups
6- List Contact Groups Returns the groups on the account with identifier, name, stored number count, and birthday greeting settings.
- Create Contact Group Creates a group, optionally with an automatic birthday greeting carrying its own time of day, sender ID, and text. That greeting is a recurring send, so switching it on is a standing commitment rather than a one time action.
- Delete Contact Groups Deletes groups by identifier. Any campaign that names a deleted group by identifier stops resolving.
- Add Numbers To Group Adds contacts with phone number, names, date of birth, gender, and up to ten free form additional fields. Those fields are what the personalization placeholders on a campaign draw from.
- Search Numbers In Group Looks numbers up in a group and returns the personal data held against them. The read that shows what a campaign will actually personalize with before it runs.
- Delete Numbers From Group Removes numbers from a group. Identifiers are validated rather than coerced, so an unparseable entry is rejected instead of being quietly dropped and leaving a record in place that the caller asked to remove.
Blacklist
3- Add Numbers To Blacklist Adds numbers to the account's personal blacklist. Worth running eagerly and unattended whenever a stop request reaches the business by any route, since more suppression is not the error worth guarding against.
- Search Blacklist Numbers Returns which of the supplied numbers are blacklisted, with the stored comment and the time each was added. The comment usually records why, which is exactly what a person needs before considering a removal.
- Delete Numbers From Blacklist Removes numbers from the blacklist, restoring messaging to somebody who was suppressed. A consent decision rather than a data cleanup, and one that belongs with a person.
Pricing
4- Get Product Prices Returns per destination prices for every messaging product available to the account, grouped by product and then by country.
- Get Account Prices Returns the prices actually applied to this account, grouped by route and then by country. The rates a real cost estimate has to use, as distinct from list rates.
- Get Country Prices Returns a flat price list by country without product grouping. The simplest input to a per destination cost calculation.
- List Countries By Continent Returns every destination country with its ISO code, name, and country code, grouped by continent. The reference list that turns a raw network code in a delivery report into a place name.
Frequently Asked Questions
What can FlowRunner do with Sempico Solutions?
FlowRunner agents can run Get Account Profile, Revoke Access Token, and Register Customer Account in Sempico Solutions, plus 19 more actions.
Does connecting Sempico Solutions to FlowRunner require OAuth?
No. Sempico Solutions connects to FlowRunner with session-based authentication, no OAuth flow required.
Can Sempico Solutions trigger a FlowRunner workflow automatically?
Sempico Solutions doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Sempico Solutions
$100 in credits. No card required. Connect in minutes.