NeoGate (SMSbrána)
MessagingSend SMS through the Czech SMSbrana gateway using its SMS Connect API. Agents deliver transactional and alert messages to Czech recipients and read delivery status back.
What This Integration Enables
NeoGate is the SMS Connect API of SMSbrána, the Czech gateway operated by SMSbrána s.r.o., formerly Neogate s.r.o. If your recipients are in the Czech Republic or Slovakia, this is a local gateway with local numbers and local pricing, which is a different proposition from routing Czech traffic through an international aggregator and hoping the sender ID survives.
Four actions is the whole surface, and that is the right size for what this does. Agents send one message or a batch, read the account credit, and read the inbox. Two polling triggers do the rest of the work: On Incoming SMS fires when a customer replies, and On Delivery Report fires when the gateway confirms what happened to a message you sent, with the status in plain terms, sent, delivered, stored at the operator, not delivered, expired or rejected. Bulk sends are submitted as one XML batch and the gateway processes each message independently, so one bad recipient number does not take down the other four hundred. What deserves attention before you build is the encoding. A standard 7-bit message holds 160 characters and cannot contain diacritics. Write the same sentence properly in Czech and it becomes Unicode, which holds 70 characters per segment. The message did not get longer. The bill did.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Appointment reminders that respect the local clock
Tomorrow's bookings are read from the scheduling system. The agent renders a Czech reminder per patient and schedules each one through Send SMS with a delivery time expressed in the gateway's format, which the gateway interprets in Czech time. That detail is the whole scenario: a reminder scheduled naively against a server clock in another timezone arrives at four in the morning, and a four in the morning reminder is worse than no reminder. The agent resolves local send times before submitting and reports any that would land outside the permitted window rather than sending them.
Replies routed back to the work that caused them
A customer answers a delivery notification with a question about the address. On Incoming SMS fires, de-duplicated by sender number, receive time and message text. The agent matches the sender to the open order, creates a ticket in Freshdesk with the SMS body attached, and replies with Send SMS only when the answer is a fact it can look up. Anything ambiguous goes to a person with the order and the message side by side. The inbox is read non-destructively, so another consumer reading the same inbox does not silently rob the flow of events.
Chasing the messages that did not arrive
On Delivery Report fires with the gateway message ID, the recipient, the delivery time and the status. The agent writes each result to the order record in Google Sheets. For anything that comes back as not delivered, expired or rejected, it separates the two causes it can tell apart: a rejected number is a data quality problem for the CRM, an expired message is a handset that was off. The first becomes a correction task, the second becomes a retry. Neither becomes a shrug.
Human-in-Loop Highlight
Send Bulk SMS charges by segment, not by message, and the segment count is decided by characters the person writing the copy never thinks about. Háček on a single letter and a 150 character reminder stops being one 7-bit SMS and becomes three UCS-2 segments, because Unicode messages hold 70 characters each. Multiply that across a batch and the run costs three times the estimate, or worse, drains the prepaid credit partway through and leaves half the recipients untold. So before submitting an XML batch, the agent renders the actual text, determines the encoding, computes the segment count per message, calls Get Credit Balance, and stops: "This 620 recipient reminder run renders as Unicode at 3 segments each. That is 1,860 segments against a remaining credit of 1,400. Approve the overspend, send the diacritic free version at 1 segment each, or split the batch?" The operations lead decides, because the trade being made is between how the message reads and what it costs, and that is a business judgment rather than a technical one. Whichever way it goes, the agent knew before it spent anything, which is the difference between a digital andon cord and an incident report.
Agent Capabilities
4 actionsMessages
2- Send SMS Sends a single SMS through the SMSbrána gateway. Accepts Czech national or international recipient formats, supports scheduled sending in Czech time, delivery reports, a custom sender ID or authorized sender number, a duplicate protection user ID, and email forwarding of replies. Returns the price, the number of segments charged, the remaining credit and the gateway message ID.
- Send Bulk SMS Sends multiple messages in a single XML batch. The gateway processes each message independently and reports a per message result, so one invalid recipient does not block the rest. Returns total price, messages sent, remaining credit and a per message list of gateway IDs or error descriptions.
Account
1- Get Credit Balance Retrieves the current remaining credit of the SMSbrána account in the account currency. Used as the guard before any batch, so a run that cannot be paid for becomes a decision rather than a partial send.
Inbox
1- Get Inbox Retrieves the SMS Connect inbox: incoming messages received on the account's numbers, and delivery reports for messages previously sent, each carrying the gateway message ID, recipient, delivery time and status. Can optionally delete the returned items after reading, which is worth leaving off when more than one consumer reads the same inbox.
Triggers
2 triggersEvent Triggers
2- On Incoming SMS Fires when a new incoming message appears in the SMS Connect inbox. The first run records a baseline and emits nothing, and afterwards each newly seen message fires once, de-duplicated by sender number, receive time and message text. Used to route a customer reply into the flow that owns the order, booking or ticket it relates to.
- On Delivery Report Fires when a new delivery report appears for a previously sent message, de-duplicated by gateway message ID. Each event carries the recipient, delivery time, the numeric status and its text form, plus the custom user ID set at send time. Used to reconcile sends, retry the recoverable failures and flag bad numbers back to the system of record.
Frequently Asked Questions
What can FlowRunner do with NeoGate (SMSbrána)?
FlowRunner agents can run Send SMS, Send Bulk SMS, and Get Credit Balance in NeoGate (SMSbrána), plus 1 more action.
Does connecting NeoGate (SMSbrána) to FlowRunner require OAuth?
No. NeoGate (SMSbrána) connects to FlowRunner with an API key, no OAuth flow required.
Can NeoGate (SMSbrána) trigger a FlowRunner workflow automatically?
Yes. NeoGate (SMSbrána) supports 2 triggers that can start a FlowRunner workflow automatically.
Start building with NeoGate (SMSbrána)
$100 in credits. No card required. Connect in minutes.