Mobivate SMS
MessagingConnect AI agents to Mobivate SMS, a UK bulk messaging gateway with campaigns, contacts, and wallet management. Agents send single and batch SMS, run template campaigns, manage contacts, groups, and opt-outs, and check wallet balances so outbound messaging stays organized and compliant.
What This Integration Enables
Mobivate is a UK bulk messaging gateway trading since 2012, and one bearer token covers everything: single sends, personalized campaigns, an address book of contacts and groups, a global opt-out list, delivery reporting, wallet and auto topup, HLR lookup, and SMPP bind configuration. Its center of gravity is not the message. It is consent and money, and the API is unusually explicit about both. There is an account wide opt-out list with its own create, list, and delete actions. There is a wallet with a balance, a transaction history, and switches that authorize or cancel recurring charges. And every API key carries its own permission set, its own optional address allowlist, and its own daily message limit, so a key that sends may be refused a wallet read and that is a configuration outcome rather than a fault.
Two things about this vendor are worth knowing before you build, and this connector is designed around both. Mobivate does not publish its API domain: every example in its documentation uses a placeholder and the documentation says the production domain is provided by their team on request. So the base URL is a config item with an empirically determined default rather than a constant, and Test API Key exists as the one route that distinguishes a wrong key from a wrong host. Run it first. It turns the vendor's most confusing failure mode into a one line answer.
The second is the opt-out flag, and it matters more. Mobivate's own documentation spells the exclude flag two different ways across its parameter tables and its examples, and on two routes the route's table and the route's example disagree with each other. Sending the spelling the API does not read means the campaign is delivered to people who withdrew consent, with no error anywhere. Because both spellings are Mobivate's own field names, this connector sends both on exactly those two routes and lets the API read whichever it recognizes, rather than picking one and hoping. That is the kind of decision a connector should be making on your behalf, and the reason it can be made at all is that the connector is built and verified against the vendor's own published API rather than assembled from a single example.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A campaign that reads consent from the system that sends it
A retail team runs a promotion to a segment in HubSpot. The agent builds the audience, then does something the CRM cannot do for it: reads List Opt-Outs from Mobivate and removes every match, because a person who replied STOP to a previous message is recorded at the gateway, not necessarily in the CRM. Recipients whose data supports it get a template campaign with placeholders filled from their own field values, so the message says a name and an order rather than "valued customer". Recipients addressed as a whole contact group are mixed into the same campaign, since a recipient entry can name a group by identifier rather than a phone number. Get Wallet Balance runs before dispatch, because a campaign is billed per accepted recipient and finding that out at recipient nine hundred is worse than finding it out at recipient zero.
Keeping the address book and the CRM in agreement
Mobivate's address book is a real store: contacts, groups, and the opt-out list all live there and all persist between campaigns. A nightly agent reconciles it against the CRM. New customers become contacts with Create Contact, changed phone numbers flow through Update Contact, and people who left become Delete Contact. Group membership is rebuilt from CRM segments so a marketer selecting a group by name in the Mobivate portal sees the same audience the flow would build. The one direction that never runs unattended is consent: opt-outs found in the CRM are pushed into Mobivate with Create Opt-Out immediately, and opt-outs found in Mobivate but absent from the CRM are written back to Mailchimp and the CRM as authoritative. Consent moves toward more restriction automatically and toward less restriction only through a person.
Reconciling what was actually delivered
Mobivate ships no trigger a flow can own, and the reason is worth understanding rather than working around. Delivery receipts go to one of two places. The first is a Receipt URL saved against the API key, a single global slot with no route to read or change it, so registering ours would overwrite the customer's production endpoint. The second is a per request callback that only ever reports on the message that created it. Neither is a subscription. So the agent polls: Search Messages returns per message delivery status over a date range, and Get Message Summary gives the aggregate counts. The interesting output is the difference between the two. When the summary says the campaign completed and the per message search shows a cluster of failures on one network, that cluster becomes an automation exception in Slack rather than a rounding error inside a delivery percentage.
Human-in-Loop Highlight
The gate on Mobivate is Delete Opt-Out, and there is no serious competition for the title. The vendor's own documentation says as much, calling it the most consequential call in the service, because what it does is restore messaging to somebody who withdrew consent. The reason it needs a gate rather than a policy is that a perfectly ordinary automation will instruct it. A CRM resync that treats the marketing platform as the source of truth and the gateway as a derived copy will look at a contact whose CRM record shows subscribed, notice the number sitting on Mobivate's opt-out list, conclude that the gateway has drifted, and helpfully correct it. The correction is silent, it succeeds, and the next campaign reaches a person who explicitly asked not to be reached.
So the agent never runs that call on its own. It gathers what it can and hands over the decision. Into Slack: "CRM sync wants to remove 4 numbers from the Mobivate opt-out list. All 4 are marked subscribed in HubSpot as of today. List Opt-Outs shows they were added on 2026-05-03, 2026-06-11, 2026-06-11 and 2026-07-29. Mobivate does not record why a number was opted out, so the reason for each is not available here. Removing an entry restores messaging to that number on every future campaign. Approve individually, or reject and correct the CRM instead?" Framing it as a choice between correcting the gateway and correcting the CRM is the whole point, because the second option is usually the right one and an unattended sync never considers it.
That is the digital andon cord under Orchestration as a Service: stopping at the point where the automation is confidently resolving a disagreement in the wrong direction. Two neighbors deserve mention for balance. Create Opt-Out runs unattended and eagerly, because moving toward more restriction is never the error worth guarding against. Enable Auto-Topup belongs on the same side of the line as Delete Opt-Out for a different reason: it authorizes a real recurring charge against a real card, and an agent that reacts to a low balance by switching it on has made a purchasing decision nobody delegated to it.
Agent Capabilities
26 actionsMessaging
5- Send Single SMS Sends one message to one recipient, with an optional callback URL for that message's delivery receipt. The transactional send, and the simplest way to confirm the account works end to end.
- Send Batch SMS Sends to an array of recipient objects, each carrying its own reference, language, field values, and optionally its own message text or originator. The most flexible campaign form, since one call can carry genuinely different messages.
- Send Campaign With Daily Limit Dispatches a campaign metered to a maximum number of messages per day. The right shape for a large audience that should be worked through gradually rather than delivered in one burst.
- Send Template Campaign Sends a stored message template across a recipient list, with placeholders filled from each recipient's own field values. Keeps campaign copy in one reviewable place instead of inside a flow.
- Send SMS By Alias Sends using a configured alias rather than a raw originator string. Useful where the sending identity is managed centrally rather than chosen per campaign.
Account
1- Test API Key Verifies the key against the configured host. The only route that separates a wrong key from a wrong base URL, which on this vendor is a first class failure mode rather than a typo, so run it first on any new connection.
Contacts
4- Create Contact Adds a contact to the Mobivate address book. The write behind keeping the gateway's own contact store aligned with a CRM.
- List Contacts Returns the stored contacts. The read that establishes what the gateway currently believes about your audience.
- Update Contact Changes an existing contact's details, most often a phone number that changed upstream.
- Delete Contact Removes a contact from the address book. Irreversible through this API, and worth confirming against the CRM before running in bulk.
Groups
3- Create Group Creates a contact group. The unit a marketer selects by name in the portal, which is why keeping groups aligned with CRM segments matters.
- List Groups Returns the account's groups with their identifiers, which campaign recipient entries use when addressing a whole group rather than a number.
- Delete Group Removes a group. The contacts survive, but any campaign definition or flow that names the group by identifier stops resolving.
Opt-Outs
3- Create Opt-Out Adds a number to the account wide opt-out list. The action to run eagerly and unattended, because moving toward more restriction is not the mistake worth guarding against.
- List Opt-Outs Returns the current opt-out list. The read that belongs in every campaign flow, since consent recorded at the gateway will not always be reflected in the CRM that built the audience.
- Delete Opt-Out Removes a number from the opt-out list, restoring messaging to somebody who withdrew consent. The most consequential call in this connector, and the one that should never run without a person deciding.
Reporting
4- Search Messages Returns per message delivery status over a date range. The supported substitute for a delivery receipt trigger, and the place individual failures inside a completed campaign become visible.
- Get Message Summary Returns aggregate delivery counts. Useful for the headline, and best read next to Search Messages so the aggregate cannot hide a cluster.
- List Campaigns Returns the campaigns on the account. The inventory a reconciliation or reporting flow starts from.
- List Message Templates Returns the stored message templates. Lets a flow select copy that a person wrote and reviewed rather than assembling a message inline.
Wallet
4- Get Wallet Balance Returns the current balance. A campaign is billed per accepted recipient, so this read belongs before dispatch rather than after a failure.
- Get Wallet Transactions Returns the transaction history. The reconciliation read behind any question about where the month's messaging spend went.
- Enable Auto-Topup Authorizes automatic account top ups. This commits real recurring charges, so it sits on the same side of the line as removing an opt-out: a person decides, not an agent reacting to a low balance.
- Disable Auto-Topup Cancels the automatic top up authorization.
Number Verification
1- Look Up Numbers Runs an HLR lookup across a list of numbers. It is a billed operation despite reading like a free check, so treat it as a spend and run it once against a cleaned list rather than repeatedly against a raw one.
Integrations
1- Configure SMPP Connection Configures the account's SMPP bind. This rotates live credentials when a system identifier or password is actually supplied, and the connector omits the secret object entirely when only a setting is being changed, so a call that flips a toggle cannot be misread as a credential change.
Frequently Asked Questions
What can FlowRunner do with Mobivate SMS?
FlowRunner agents can run Send Single SMS, Send Batch SMS, and Send Campaign With Daily Limit in Mobivate SMS, plus 23 more actions.
Does connecting Mobivate SMS to FlowRunner require OAuth?
No. Mobivate SMS connects to FlowRunner with an API key, no OAuth flow required.
Can Mobivate SMS trigger a FlowRunner workflow automatically?
Mobivate SMS doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Mobivate SMS
$100 in credits. No card required. Connect in minutes.