SerwerSMS
MessagingConnect AI agents to SerwerSMS, a Polish messaging gateway from Vercom covering SMS, MMS, voice, and RCS. Agents send and schedule messages, pull delivery reports and inbound replies, manage contacts, templates, and blacklists, and run HLR checks so Polish-market messaging stays reliable.
What This Integration Enables
SerwerSMS is a Polish gateway operated by Vercom in Poznan, and it is the deepest surface in this category for teams whose customers are in Poland. One connector covers SMS, personalized SMS, MMS with an attachment library, synthesized voice calls, RCS through named agents, Premium SMS with quiz tallies, and shortened otworz.to links with QR encoding. Around the sending sits everything a Polish operations team actually needs to run it: registered sender names with their authorization state, message templates, a contact address book with groups, a blacklist, subaccounts with per-product limits, and three different kinds of number check.
The design decision worth understanding before you automate anything here is that SerwerSMS has no separate product parameter. On both SMS sending operations, leaving the sender name empty sends a cheaper ECO message from a shared number that recipients can reply to, and filling it in sends a FULL message showing your brand. An empty field is not an omission, it is a choice, and it changes both the price and whether replies come back to you. Agents are very good at leaving optional fields empty. That is precisely why a flow on this connector should read List Sender Names and state the resulting product type out loud before a person is asked to approve anything.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Appointment Reminders With Replies That Land Somewhere
A clinic's booking system in Google Calendar holds tomorrow's appointments. Each morning an agent expands the day's patients, checks each number with Check Blacklisted Number, and sends reminders with Send Personalized SMS so every patient gets their own time and doctor rather than a generic text. Because the clinic wants replies, the send goes out as an ECO message from the shared repliable number. Later that day the agent polls Get Received Messages for the confirmations and cancellations that came back and writes each one onto the appointment. The scheduling team never touches the gateway.
Number Hygiene Before a Polish Campaign
Before a quarterly campaign, the agent runs the recipient list through Look Up Number Network to see which numbers have been ported and which network now holds them, and Check Number Availability (HLR) to establish whether the handset is reachable at all. Both operations are billed per query including failures, so the agent writes every result back to PostgreSQL as a cached record with a timestamp and only re-queries entries older than the cache window. Numbers that fail Validate Phone Number Format never reach the paid lookups in the first place. The campaign that follows is smaller, cheaper and lands more often.
A Premium SMS Quiz Answered by an Agent
A broadcaster runs a Premium SMS vote. Inbound entries queue up, and the agent polls List Premium Messages, reads each entry's sender and body, records the vote in Airtable, and answers with Send Premium Reply over the same Premium number the message arrived on, consuming one of that message's reply allowance. At the end of the segment the agent calls Get Quiz Results for the tallied count per answer option and posts the final numbers to the production channel in Slack. Nobody sits at a console retyping replies during a live show.
Human-in-Loop Highlight
A single Send SMS on this connector accepts up to 100,000 recipients, and it accepts contact groups and stored contacts as well as raw numbers, which means the true audience of a send is not visible in the parameters an agent filled in. Cancel Scheduled Messages exists, but it only reaches messages queued for a future date. An immediate send has no recall at all. So the agent resolves the audience before it asks: it expands every named group, subtracts the blacklist, and counts what is left. Then it stops and posts to the campaign owner: "Ready to send to 3 groups, expanded to 41,880 recipients after removing 612 blacklisted numbers. Sender name: MEDICOVER, authorized, so this bills as FULL and replies will not come back to us. This is an immediate send, so Cancel Scheduled Messages will not reach it. Approve, or reply schedule and I will queue it for 09:00 tomorrow so it stays cancellable." Two facts drive that message, and both are SerwerSMS's own: the group expansion the agent had to perform to know the real number, and the sender name that silently decided the product. The human-in-the-loop gate here converts an irreversible send into a reversible one, or gets somebody to own the fact that it is not.
Agent Capabilities
56 actionsSMS
2- Send SMS Sends the same text to one or more recipients, contact groups or stored contacts in a single request. The sender name decides which product is billed, and the operation supports Unicode, flash, vCard, priority channel, WAP push, scheduling, validity period, custom message identifiers and a per-request delivery report URL.
- Send Personalized SMS Sends a batch in which every recipient receives its own message text, supplied as number and text pairs. This is the operation for reminders, statements and anything where the body varies per person. It can optionally be delivered as synthesized voice calls instead.
MMS and Voice
2- Send MMS Sends a multimedia message carrying up to ten previously uploaded attachments to recipients or contact groups. Attachments must already exist in the media library.
- Send Voice Message Places an automated call to recipients, contact groups or stored contacts, playing either an uploaded recording or text read by a speech synthesizer, with an optional caller number and replay key.
Media Library
4- Upload Media File Registers a file from a public URL into the MMS or voice library so it can be attached or played.
- List Media Files Lists stored files in one of the libraries with their identifiers, original file names, sizes and upload dates.
- Get Media File Returns the stored details of a single file in one of the libraries.
- Delete Media File Permanently removes a file from a library. Messages already queued that reference it are unaffected.
RCS
4- Send RCS Message Sends a Rich Communication Services message through one of the account's RCS agents. The body is a structure whose shape selects text, audio, file, map, rich card or carousel, with reply and action suggestion buttons.
- List RCS Agents Lists the RCS agents configured on the account with their networks, configuration and readiness state.
- Check RCS Support Checks whether given numbers can receive RCS from a specific agent, answering each number individually. Used to decide per recipient whether to send RCS or fall back to SMS.
- Register RCS Test Number Submits a number to Google as a tester for an RCS agent, which is required before that agent can reach the number while it is still in testing.
Message Reporting
5- Get Delivery Reports Returns the delivery state of previously sent messages, filtered by message identifier, custom identifier, recipient, queueing date range and state. Reports age out of the API after a matter of days, so they should be collected while they are still available.
- Get Message Returns the full record of one sent message: delivery state, queueing, sending and delivery timestamps, sender, product type and cost.
- Cancel Scheduled Messages Removes messages queued for a future send date so they are never dispatched. This reaches scheduled traffic only, which is the reason a large send is often better scheduled than sent immediately.
- Get Received Messages Retrieves inbound messages: replies to ECO messages, traffic on shared and individual access numbers, Premium SMS and inbound RCS. Enabling the mark-as-read option means those messages are never returned by the API again, so a flow that consumes them is the only reader that will ever see them.
- Get Sending Statistics Returns aggregate statistics for the account's sending batches, each with its identifier, name, body, product type and date range.
Account
2- Get Account Limits Returns how many messages of each product the account may still send, along with the maximum message length per product. Used as the preflight check before a large campaign.
- Get Account Notices Returns notices posted to the account by SerwerSMS administrators, flagged by whether they are still unread. Service announcements land here, so a flow can surface them rather than let them sit.
Sender Names
2- List Sender Names Lists registered sender names with their authorization state, which is one of pending, authorized, rejected or expired. Reading this before a send is what stops a flow from dispatching under a name that is not yet cleared.
- Add Sender Name Submits a new alphanumeric sender name of up to eleven characters for authorization. Adding a name does not make it usable, because an administrator must approve it first.
Templates
5- List Message Templates Lists the reusable templates stored on the account with their identifiers, names and body text.
- Get Message Template Returns a single template by identifier with its name and body.
- Create Message Template Stores a new reusable template and returns its identifier. Templates are visible in the customer panel, so wording stays reviewable by the people responsible for it.
- Update Message Template Replaces the name and body of an existing template. Both values are required, so read the template first when only one is changing.
- Delete Message Template Permanently removes a template. Messages already sent using its text are unaffected.
Contact Groups
6- List Contact Groups Lists the account's contact groups with their identifiers, names and current member counts. The member count is what turns a group name into a real audience size.
- Get Contact Group Returns a single group by identifier with its name and member count.
- Create Contact Group Creates an empty group and returns its identifier for assigning contacts and addressing sends.
- Update Contact Group Renames an existing group without affecting membership.
- Delete Contact Group Removes a group. By default the contacts keep existing and simply lose the group assignment, but the delete-contacts option removes them outright.
- Get Groups For Phone Number Returns every group containing a given number, with the contact identifier alongside each group. Used to answer what a customer is currently subscribed to before changing anything.
Contacts
6- List Contacts Lists address book contacts, optionally narrowed to one group or to contacts belonging to no group at all.
- Get Contact Returns a single contact with all stored fields, including whether its number is currently blacklisted.
- Create Contact Adds a contact to the address book and assigns it to one or more groups, returning the new identifier.
- Update Contact Updates an existing contact. The group assignment and phone number are required alongside the identifier, so read the contact first.
- Delete Contact Permanently removes a contact. The number is not blacklisted by this operation, so it can still be messaged directly.
- Import Contacts Imports a list of contacts into a named group in a single request, creating the group if needed. Used for bulk sync from a CRM or store.
Blacklist
4- List Blacklisted Numbers Lists blacklisted numbers with the date each was added.
- Add Number To Blacklist Adds a number so future sends skip it. This is the operation an inbound opt-out handler should call.
- Check Blacklisted Number Reports whether a single number is currently blacklisted. Useful as a guard immediately before a one-to-one send.
- Remove Number From Blacklist Removes a number so it can be messaged again. Reversing a recorded opt-out is a decision that belongs with a person, not a rule.
Subaccounts
5- List Subaccounts Lists subaccounts under the main account with their identifiers and login names.
- Get Subaccount Returns one subaccount's stored details: identifier, login name, descriptive name, phone number and email.
- Create Subaccount Creates a subaccount, nominating an existing one as the permission template so its settings are copied.
- Set Subaccount Limit Sets how many messages of one product a subaccount may send, drawn from the main account's allowance. A separate limit is held per product.
- Delete Subaccount Permanently removes a subaccount, revoking both panel access and API access.
Number Checks
4- Look Up Number Network Identifies the mobile network a number belongs to, returning its network name, whether it has been ported and which network now holds it.
- Check Number Availability (HLR) Runs an HLR query against one or many numbers for network membership, porting status and, where the operator supports it, handset reachability. Billed per query including failures, so results are worth caching.
- Check Number Availability (NAT) Submits a number for a NAT availability check, which supports Polish mobile numbers only and is always asynchronous, returning an identifier to poll.
- Validate Phone Number Format Checks whether a number is syntactically valid and returns a simple correct flag. Unlike the network and HLR checks this costs nothing, so it belongs first in any hygiene sequence.
Premium SMS
3- List Premium Messages Lists inbound Premium SMS messages awaiting a reply, each with its identifier, the Premium number it arrived on, the sender and the body.
- Send Premium Reply Replies to a specific inbound Premium SMS over the same Premium number it arrived on, consuming one of that message's reply allowance.
- Get Quiz Results Returns the tallied results of a Premium SMS quiz: the quiz name and the response count for each answer option.
Short Links
2- Create Short Link Creates a shortened otworz.to link that redirects to a target address, or encodes a string as a QR code. Used to keep a campaign inside one SMS part.
- Get Short Link Statistics Returns a shortened link and how many times it has been followed, addressed by its suffix. This is the click measurement for an SMS campaign.
Frequently Asked Questions
What can FlowRunner do with SerwerSMS?
FlowRunner agents can run Send SMS, Send Personalized SMS, and Send MMS in SerwerSMS, plus 53 more actions.
Does connecting SerwerSMS to FlowRunner require OAuth?
No. SerwerSMS connects to FlowRunner with an API key, no OAuth flow required.
Can SerwerSMS trigger a FlowRunner workflow automatically?
SerwerSMS doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SerwerSMS
$100 in credits. No card required. Connect in minutes.