InforUMobile
MessagingConnect AI agents to InforUMobile, an Israeli multichannel messaging platform. Agents send SMS, WhatsApp, email, voice, and push messages, manage contacts, groups, and unsubscribes, and pull delivery receipts and incoming messages so multichannel campaigns run under one roof.
What This Integration Enables
InforUMobile is an Israeli multichannel messaging platform, and the breadth behind one credential is the first thing to notice: SMS, WhatsApp, email campaigns, text-to-speech voice calls, and Firebase push notifications, plus contacts, groups, unsubscribe management, file storage, and automation triggers. The WhatsApp side is Meta's official Business Platform rather than a session gateway, which shows in the shape of the API. Templates are submitted for provider approval, they carry Meta's MARKETING and UTILITY categories, and Get WhatsApp Sender Info reports the account's messaging tier and quality rating straight out of Facebook Business Manager. That means an agent working here is subject to the same rules a WhatsApp Business account is subject to everywhere, and it can read its own standing rather than guessing at it.
The structure the platform is organized around is quota. Get Quota returns the remaining message balance per product and per account level, and Create Or Add Quota allocates quota to a customer, a project, or a user. That is a reseller shape: a parent account holds the balance and pushes spending authority downward. It is genuinely useful for an agency or a multi-brand operation running several tenants through one connector, and it carries one asymmetry worth knowing before you build on it, which the human-in-loop section below is entirely about.
Three operational facts belong in any design. First, the Pull operations are destructive reads. Pull SMS Delivery Notifications, Pull Incoming SMS Messages, Pull WhatsApp Delivery Notifications, Pull Incoming WhatsApp Messages, Pull Email Notifications, and Pull Voice Notifications each drain a server-side queue, and entries are removed once pulled. Whatever pulls them owns them, so a flow should write what it drained somewhere durable before doing anything else with it, and two flows should never poll the same queue. Second, group numbers and group ids are different identifiers on this platform: SMS, WhatsApp, voice, and push target groups by group number, while email and voice campaigns can also target them by group id. Third, every endpoint answers with a status envelope, and a status other than success is a failure even when the HTTP response is 200, which this connector raises as an error rather than passing through. Several endpoints are additionally gated per account and must be enabled by InforUMobile before use, including the sent-message report, the sender whitelist operations, the standalone one-time password interface, and the notification queues. There are no triggers, because InforUMobile's callbacks are configured on the account by their support team and there is nothing a flow could subscribe against.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A tenant's campaign run against the balance that belongs to them
An agency runs messaging for several client brands out of one InforUMobile parent account, each client holding its own quota. When a campaign is approved, the agent resolves the audience by group number, calls Check Sender ID Is Allowed for the sender the brand uses, and reads Get Quota for that account level. If the run fits, it sends with Send SMS, which handles per-recipient placeholder substitution, scheduling, segment capping, and a delivery notification URL in one call. If it does not fit, the agent does not top up. It reports the shortfall with the numbers attached, because releasing more quota is an act of moving spending authority and this API has no way to reverse it. Afterward, Pull SMS Delivery Notifications drains the receipts into Google Sheets so the run reconciles against something that persists.
A WhatsApp template that took Meta a week to approve
Reaching a customer on WhatsApp outside an open conversation requires an approved template, and approval is Meta's to grant. The agent handles the lifecycle: Upload File puts the header media into place and returns the UID the template needs, Create WhatsApp Template submits it, and List WhatsApp Templates and Get WhatsApp Template report the approval state until it clears. Once approved, Send WhatsApp Template Message reaches recipients and groups with per-placeholder bindings and per-recipient media and button values, while Send WhatsApp Chat Message handles free-form replies inside conversations that are already open. Get WhatsApp Chats gives the conversation history, Pull Incoming WhatsApp Messages drains what customers sent, and Download Media File pulls an inbound photo into FlowRunner file storage where a claims or support step can attach it. Delete WhatsApp Template is the one action here that no automated cleanup rule should ever hold, because it destroys an asset that only Meta can grant back, on Meta's timetable.
Reactivating an unsubscribe, with the evidence in hand
InforUMobile keeps a real opt-out history, which changes what an agent can responsibly do with it. When a customer writes in asking to start receiving messages again, the agent runs Check If Unsubscribed to confirm the current state and Get Unsubscribe History For Contact to retrieve when and how they opted out in the first place. It assembles both alongside the customer's written request and posts the whole thing to a person, because Reactivate Unsubscribed Contacts reverses a decision the customer made and the platform recorded, and consent that was withdrawn on one channel is not automatically restored on all of them. The agent's contribution is the evidence and the timeline. The decision to put someone back on a list they chose to leave belongs to a human, and the history makes that decision an informed one rather than a guess.
Human-in-Loop Highlight
The gate on InforUMobile is Create Or Add Quota, and what makes it a gate is what is missing rather than what is present. This connector can read a quota with Get Quota and it can allocate quota to a customer, a project, or a user with Create Or Add Quota. There is no operation anywhere in the action list that reduces an allocation, reclaims it, or hands it back to the parent. Quota moves in one direction through this API. So when an agent releases balance to a tenant, it is not performing a step that can be corrected on the next run, it is transferring spending authority permanently as far as any flow is concerned, and the only route back is a person in the InforUMobile interface or a support conversation.
That is why the agent brings the arithmetic and stops. Into Slack: "Northshore Retail's spring campaign needs 41,800 SMS. Their quota shows 28,400 remaining, so the run is short by 13,400. Their last three months averaged 22,000 a month. Release 13,400 to Northshore, release a larger buffer, or trim the run to the 28,400 already allocated? Note that this connector cannot take an allocation back once it is granted." A person who knows the commercial relationship answers that in the Flow conversation and the flow proceeds either way, with the release recorded against their name.
That is human-in-the-loop as Orchestration as a Service means it. The agent handled the audience resolution, the sender validation, the placeholder substitution, and the reconciliation, which is all of the work. It held back the one act whose consequences it cannot undo. Two other operations belong behind the same treatment for reasons of their own. Delete WhatsApp Template destroys a Meta-approved asset, and the account's messaging tier and quality rating mean the cost of losing one is measured in review time you do not control. The Pull operations are destructive reads that drain a queue permanently, so the decision about which flow owns each queue is an architectural one that should be made once by a person and then never contended, rather than discovered when two schedules overlap and half a day of delivery receipts is gone.
Agent Capabilities
55 actionsSMS
9- Send SMS Sends a message to recipients, contact groups, or both, with per-recipient placeholder substitution, scheduling, segment capping, and a delivery notification URL. The main outbound path, and the one that draws directly on the account's quota.
- Delete Future SMS Messages Cancels scheduled messages by phone number, customer message id, and customer parameter. The recall path on a queued send, and the reason a large run is safer scheduled than dispatched.
- Get Sent SMS Messages Returns a sent-message report for one phone number over a date range. Enabled per account, and the read behind answering whether a specific customer was actually contacted.
- Check Sender ID Is Allowed Checks whether a sender identity may send on the account. Worth running before the message is composed, since a sender is a per-message parameter with no endpoint that lists the permitted values.
- Send Sender Whitelist OTP Sends a verification code to the number being registered as a sender. The first half of claiming a phone number as a sending identity.
- Authenticate Sender Whitelist OTP Submits that code to complete the whitelisting. Together with the previous action, this is how a new sender identity becomes usable without leaving the flow.
- Get Unsubscribe Link Returns the account's unsubscribe link and sentence. The text a compliant marketing message needs to carry, retrieved rather than hand-copied into a template.
- Pull SMS Delivery Notifications Retrieves and drains queued delivery receipts. A destructive read: entries are removed once pulled, so whatever calls this owns the only copy and should persist it before anything else.
- Pull Incoming SMS Messages Retrieves and drains queued inbound messages. Same destructive semantics, and the entry point for handling replies and opt-out language.
One-Time Passwords
2- Send One-Time Password Sends a generated code by SMS or email. Enabled per account, and the managed alternative to generating and storing codes in your own flow.
- Verify One-Time Password Verifies a code the end user entered. The agent branches on the verdict rather than holding the secret itself.
- Send WhatsApp Template Message Sends an approved template with per-placeholder bindings and per-recipient media and button values, to recipients, groups, or both. The only way to reach a customer outside an open conversation window.
- Send WhatsApp Chat Message Sends a free-form message inside an open conversation. Used for the actual back and forth once a customer has messaged first.
- List WhatsApp Templates Returns the account's templates with their approval state. The read that tells a flow which templates are actually usable right now.
- Get WhatsApp Template Returns one template with its approval state and content. Used to confirm the exact placeholder shape before binding values to it.
- Create WhatsApp Template Submits a new template for provider approval. Approval is Meta's decision on Meta's timetable, so a flow should treat submission and availability as separate events.
- Delete WhatsApp Template Deletes a template. This destroys an asset that only Meta can grant back, which makes it a poor fit for any automated cleanup rule and a good fit for a person's judgment.
- Get WhatsApp Chats Returns conversation history aggregated by chat. The context a support agent, human or otherwise, needs before replying to a returning customer.
- Get WhatsApp Sender Info Returns the account's messaging tier and quality rating. Reading your own standing before a large template send is the difference between a campaign and a rate limit.
- Delete Future WhatsApp Messages Cancels scheduled WhatsApp messages. The recall path on queued template sends.
- Pull WhatsApp Delivery Notifications Retrieves and drains queued WhatsApp delivery receipts. Destructive read, same ownership rule as the SMS queues.
- Pull Incoming WhatsApp Messages Retrieves and drains queued inbound WhatsApp messages. The trigger substitute for conversational flows, and the read that opens the reply window.
- Send Existing Email Campaign Sends a campaign built in the InforUMobile interface, with optional duplication and string replacements. Lets the design live where designers work while the dispatch decision lives in the flow.
- Send Email Message Composes and sends a campaign entirely through the API. The path for email that is generated rather than designed.
- List Email Campaigns Returns campaigns with their performance counters. The inventory read behind reporting and behind picking a campaign to duplicate.
- Get Email Campaign Returns one campaign with its counters. Used to confirm what a flow is about to send or duplicate.
- Duplicate Email Campaign Creates a new draft from an existing campaign. The safe way to reuse a design without editing the original that other flows may still reference.
- Get Email Campaign Job Status Returns processing status for a send, by job token. Email dispatch is asynchronous, so this is how a flow knows a send finished rather than started.
- Pull Email Notifications Retrieves and drains queued delivery, open, click, return, and unsubscribe events. Destructive read, and the source of the engagement data that would otherwise need a separate analytics integration.
- Stop Future Email Campaign Cancels a scheduled campaign. The recall path on email, and worth wiring into any flow that schedules more than a day ahead.
Voice
3- Send Text To Speech Call Places calls that read a text message aloud, up to a hundred per request. Used for urgent notifications where a message on a screen is not enough.
- Send Existing Voice Campaign Plays an interactive voice campaign to recipients and groups. The path for anything with menus and routing built in the platform.
- Pull Voice Notifications Retrieves and drains queued end-of-call notifications. Destructive read, and the only record of what happened on each call.
Contacts
6- Create Or Update Contacts Bulk upsert of up to five thousand records, matched on email, phone, or both. The synchronization path between a CRM and the messaging platform.
- Check Contact Job Status Returns the final result of a bulk upload by token. Bulk contact writes are asynchronous, so this is how a flow learns which records actually landed.
- Delete Contacts Deletes contacts. Removing a contact is not the same as suppressing them, and only the unsubscribe operations stop future contact.
- Get Contact Returns a single contact. The lookup behind personalization and behind answering what the platform holds about a specific person.
- List Contacts Returns contacts with paging. The read behind audience sizing and export.
- List Contact Fields Returns the field ids, API names, captions, and types defined on the account. Worth reading once at the start of a flow rather than hard-coding field names that differ per tenant.
Contact Groups
4- Create Or Update Contact Group Creates or updates a group, including the group number that sends target. Group number and group id are different identifiers, and using the wrong one is the most common way a send misses its audience.
- Delete Contact Group Deletes a group. Any flow still targeting that group number will stop reaching anyone, silently, so this is worth coordinating rather than automating.
- Get Contact Group Returns one group with its identifiers. The read that resolves a group name to the number a send actually needs.
- List Contact Groups Returns the account's groups. The inventory an audience-building step works from.
Subscriptions
6- Unsubscribe Contacts Opts contacts out. This should run automatically the moment a reply asks to stop, with no approval step in front of it.
- Reactivate Unsubscribed Contacts Puts previously unsubscribed contacts back in reach. This reverses a decision the customer made and the platform recorded, which is why it belongs with a person and the history in front of them.
- List Unsubscribed Contacts Returns the opt-out list. The suppression read that runs before any campaign is priced or sent.
- Get Unsubscribe History For Contact Returns when and how one contact opted out. The evidence that turns a reactivation request into an informed decision instead of a guess.
- List Unsubscribe History Returns opt-out history across the account. Useful for spotting a campaign that produced an unusual number of opt-outs while it is still running.
- Check If Unsubscribed Checks whether a specific contact is currently opted out. The per-recipient guard for transactional flows that must not become marketing ones.
Account
2- Get Quota Returns the remaining message balance per product and per account level. The read that decides whether a run fits before it is proposed.
- Create Or Add Quota Allocates quota to a customer, a project, or a user. Nothing in this connector reduces or reclaims an allocation, so this moves spending authority in one direction only.
Files
2- Upload File Uploads a file by URL or Base64 and returns a UID for WhatsApp template media. The step that turns an asset into something a template can reference.
- Download Media File Downloads an inbound WhatsApp media file by UID into FlowRunner file storage and returns a URL. How a customer's photo becomes something a later action can attach to a ticket or a claim.
Push and Automation
2- Send Push Notification Sends a Firebase push notification to groups or to specific devices. The in-app channel on the same account and quota as everything else.
- Trigger Automation Fires a named automation event for one or more contacts. The bridge between a FlowRunner flow and a sequence built inside InforUMobile, so the two do not have to duplicate each other's logic.
Frequently Asked Questions
What can FlowRunner do with InforUMobile?
FlowRunner agents can run Send SMS, Delete Future SMS Messages, and Get Sent SMS Messages in InforUMobile, plus 52 more actions.
Does connecting InforUMobile to FlowRunner require OAuth?
No. InforUMobile connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can InforUMobile trigger a FlowRunner workflow automatically?
InforUMobile doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with InforUMobile
$100 in credits. No card required. Connect in minutes.