--- title: "Infobip Integration" description: "Reach customers worldwide over Infobip's omnichannel CPaaS. Agents send SMS, free-form and template WhatsApp messages, and transactional email, then track delivery reports and read inbound messages for two-way conversations." url: https://flowrunner.ai/integrations/infobip date_modified: 2026-08-01T02:40:32-07:00 --- # Infobip [Messaging](https://flowrunner.ai/integrations/category/communication-messaging) Reach customers worldwide over Infobip's omnichannel CPaaS. Agents send SMS, free-form and template WhatsApp messages, and transactional email, then track delivery reports and read inbound messages for two-way conversations. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 6 actions · API key · available [Infobip website](https://infobip.com/) · [Platform Documentation](https://www.infobip.com/docs/api) · Capability data verified 2026-07-28 1. An order ships and the fulfillment system emits the tracking number 2. The agent picks the channel per customer: WhatsApp where a sender is registered for the market, SMS as the fallback 3. Send WhatsApp Template delivers the pre-approved shipping notification with the tracking placeholders filled 4. Send SMS covers the customers outside WhatsApp coverage through the global gateway 5. Get SMS Delivery Reports polls the final delivery outcome for each message ID 6. Failed deliveries land in the ops channel with the destination and error details 7. An operator decides how to reach customers whose messages hard-failed, and approves any re-send batch ## What This Integration Enables Infobip's reach is the point: one API that terminates SMS worldwide, delivers WhatsApp through registered senders, and sends transactional email. What that reach demands is discipline, because the platform's rules are real. WhatsApp free-form messages only work inside the 24-hour service window; initiating a conversation requires an exact registered template. Delivery reports and inbound messages are consumed on read, so whatever polls them must actually store what it sees. These are precisely the rules an orchestration layer should enforce so humans never have to remember them. FlowRunner agents pick the compliant path automatically, poll and persist what the API only shows once, and turn a fire-and-forget gateway into an accountable messaging operation. - Send transactional SMS, order updates, alerts, OTP codes, to recipients worldwide - Deliver WhatsApp free-form messages in-window and pre-approved templates outside it - Send transactional email from verified senders alongside messaging flows - Track final SMS delivery outcomes and surface failures with error detail - Capture inbound replies and log them where the rest of the company can see them Every send lands on a person's phone, so FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) gate stands in front of anything broader than a single transactional message. Channel choice itself becomes workflow logic: the agent knows which markets have a registered WhatsApp sender, which recipients have an open service window, and which fall back to SMS or email, so the compliant path is the default path rather than something an operator has to remember under deadline. ### Without FlowRunner **One channel fits nobody**: Every customer gets email because that is the only channel the tooling can reach **Sends disappear into the gateway**: Whether a notification arrived is unknowable, so support hears "you never told me" with no defense **Replies go nowhere**: Customers answer the notification number and the answer evaporates ### With FlowRunner **Channel matches the customer**: WhatsApp where it is the norm, SMS where it is not, email alongside, all from one workflow **Delivery is a tracked outcome**: Every message ID gets a final report, and failures surface with error details the same hour **Two-way is real**: Inbound messages get read, logged against the CRM record, and routed to a person ## Use Case Scenarios ### Order confirmations on the customer's channel A [Shopify](https://flowrunner.ai/integrations/shopify) order completes. For markets where the WhatsApp sender is registered, the agent fires Send WhatsApp Template with the order-confirmation template, its language code, and the placeholders in registered order. Everywhere else, Send SMS carries the same confirmation through the gateway. One workflow, two channels, and the customer gets the message where they actually read messages, with the channel decision made by logic instead of by which tool the team happened to wire up first. ### The reply that reaches a human The agent polls Get Inbound Messages on a schedule. Each captured reply, sender, text, keyword, timestamp, is immediately persisted and matched against the CRM via [HubSpot](https://flowrunner.ai/integrations/hubspot). A customer texting STOP gets suppressed from future sends the same minute; a customer asking a question gets their message posted to the support channel in [Slack](https://flowrunner.ai/integrations/slack) with their CRM context attached, so the person answering knows who is asking. Because Infobip returns each inbound message exactly once, the agent's store-then-route discipline is what makes two-way messaging dependable at all. ### Delivery accountability for the compliance file After each notification batch, the agent polls Get SMS Delivery Reports with the bulk ID and writes every final status, delivered, failed, error code, destination, timestamp, to [Google Sheets](https://flowrunner.ai/integrations/google-sheets). Because Infobip serves each report exactly once, the agent's persistence step is the difference between an audit trail and a black hole. When a customer disputes ever being notified, the ops team answers with a delivery report row instead of a shrug. Hard failures roll up into a re-contact list that a person reviews before any second attempt goes out on any channel. ## Human-in-Loop Highlight Send WhatsApp Template is the operation that opens conversations, and it is the one to respect most. Templates exist because WhatsApp lets businesses initiate contact only on pre-approved terms; a template blast to a purchased or stale list is spam by the strictest definition, it costs per message, and repeated recipient blocks put the registered sender itself at risk. Losing a WhatsApp sender is not a bounced email; it is losing the channel. So FlowRunner agents send single transactional templates autonomously, order confirmations to the person who just ordered, and stage everything else. Any list-shaped send gets assembled into a proposal: template name, recipient count, market, estimated cost, opt-in provenance. A person approves it or kills it. The gateway makes sending easy. The gate makes sure easy never becomes careless. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 6 actions ### SMS 3 - **Send SMS** Sends SMS to one or more recipients through the global gateway, from an alphanumeric sender ID or registered number. Returns a message ID and status per recipient for delivery tracking. - **Get SMS Delivery Reports** Retrieves final delivery reports with status, error details, destination, and timestamps. Reports are consumed on read, so the agent persists them the moment they arrive. - **Get Inbound Messages** Retrieves SMS replies sent to your Infobip numbers with sender, text, keyword, and receive time. Also consumed on read; the foundation of two-way workflows. ### WhatsApp 2 - **Send WhatsApp Message** Sends a free-form WhatsApp text from a registered sender, valid only inside the open 24-hour customer service window, with optional link previews. - **Send WhatsApp Template** Sends a pre-approved template with exact registered name, language code, and ordered placeholder values. Required to initiate conversations, and the send this page's human gate exists for. ### Email 1 - **Send Email** Sends transactional email from a verified sender to one or more recipients, with plain-text or HTML content and per-recipient message IDs and statuses returned. ## Frequently Asked Questions ### What can FlowRunner do with Infobip? FlowRunner agents can run Send SMS, Get SMS Delivery Reports, and Get Inbound Messages in Infobip, plus 3 more actions. ### Does connecting Infobip to FlowRunner require OAuth? No. Infobip connects to FlowRunner with an API key, no OAuth flow required. ### Can Infobip trigger a FlowRunner workflow automatically? Infobip doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Infobip?** This integration exposes Infobip to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/infobip. Site index: https://flowrunner.ai/llms.txt