SMS Masivos
MessagingConnect AI agents to SMS Masivos, a Mexican bulk messaging platform covering SMS, WhatsApp, and voice. Agents send messages and verification codes, manage contact lists, pull delivery reports, and run the vendor's wallet and loyalty tooling so Mexican customer messaging and engagement run from one API.
What This Integration Enables
SMS Masivos is a Mexican platform run by VZERT in Leon, Guanajuato, and describing it as a bulk SMS gateway undersells what its API is actually built around. Yes, it sends SMS, RCS, WhatsApp and text-to-speech voice calls. But the same API also runs a digital wallet with per-customer balances, a loyalty card program with stamps and cycles, payment request links, staff members who transactions are attributed to, and subaccounts with their own keys and credit. This is a customer engagement stack for Mexican retail and services, and messaging is the notification layer on top of it rather than the product itself.
That shapes how an agent should be pointed at it. The verification surface is a good example of the design: Send Verification Code, Verify Code, Get Verification Status and Invalidate Verification manage one lifecycle across SMS, WhatsApp and voice, and calling the send again for the same number resends the existing code on a different channel rather than starting over, which is exactly what a "did not receive the code" button needs. Get Verification Status is explicitly side effect free, so a flow can inspect state without consuming an attempt. Sandbox mode runs every validation and returns message references without delivering anything or spending credit, which means a flow can be exercised end to end before it touches a customer. And one detail that matters more in Mexico than anywhere else in this category: message bodies always go out in the GSM-7 alphabet, so accents and the letter enye are substituted automatically. A flow that personalizes with customer names should know that Muñoz will arrive as Munoz.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Loyalty That Follows the Sale
A cafe chain records sales in Square. Each completed sale pushes into a flow that resolves the cashier through List Staff Members, reads Get Loyalty Customer to see how many cycles the customer has completed, and calls Register Loyalty Stamp attributed to that cashier. When the read shows the customer is one stamp from a completed cycle, the agent sends a message with Send SMS telling them so. Nothing is retyped, the stamp lands on the right customer, and the branch manager can see which staff member processed it.
Verification Across Three Channels Without Three Integrations
A delivery app verifies phone numbers at signup. The agent calls Send Verification Code over SMS. If the user taps "resend by WhatsApp", the agent calls the same operation again with a different channel, and the same code is resent rather than a new one issued. If the number never verifies, the agent calls Invalidate Verification to clear the state cleanly instead of leaving a stale code in force. Throughout, Get Verification Status lets a support flow answer "where is this signup stuck" without sending anything or burning one of the customer's attempts. Failed signups after the retry limit open a task in Zendesk.
A Campaign Sized Against the Balance That Will Pay For It
Before a promotional send, the agent reads Get Credit Balance and compares it against the resolved recipient count, because a large campaign that runs out midway fails with an insufficient credit condition rather than degrading gracefully. It stages the audience with List Contacts In List, sends with Send SMS in batches inside the documented per-request recipient ceiling, and afterward calls Get Campaign Report Details for the aggregated breakdown: effectiveness percentage, total messages, delivered, failed, pending and not charged. That breakdown lands in Google Sheets alongside the campaign cost, so the next campaign is planned against real delivery rather than against the send count.
Human-in-Loop Highlight
Most of this connector sends messages. One operation moves money. Update Wallet Balance adds balance to, or redeems balance from, a customer's digital wallet, and a redemption is stored value leaving a customer's account. There is no reversing operation. Register Wallet Sale records the transaction against a staff member, which means the attribution is permanent too, and the record will be read later as evidence of who authorized what. An agent is well placed to gather everything needed for that decision and badly placed to make it, because the failure mode is not a wrong message, it is a customer whose balance is wrong and a staff member's name on the entry. So the agent stops and asks the branch manager: "Redemption request at Polanco, wallet MX-CAFE-01. Customer +52 55 xxx xxxx, current balance 340 MXN. Requested redemption 280 MXN against ticket 8841, entered by staff member Ana R. Get Loyalty Customer shows 2 completed cycles and 1 redemption already recorded today. Approve and I will call Update Wallet Balance and Register Wallet Sale attributed to Ana R., or reject and I will leave the balance untouched." Everything before that message is work an agent should do. The line it stops at is the one where a message becomes a transaction, which is the human-in-the-loop boundary this connector makes unusually easy to draw.
Agent Capabilities
41 actionsMessaging
3- Send SMS Sends an SMS or RCS message to a batch of Mexican or international mobile numbers in one request. Supports a sender ID, scheduled delivery, flash SMS, automatic URL shortening, read confirmation tracking and extra parameters echoed back on the delivery webhook. Accents and special characters are substituted automatically because bodies go out in GSM-7.
- Send WhatsApp Message Sends a one-to-one WhatsApp message from a line connected to your account, with text plus image, video, audio or document media supplied as a public URL.
- Send Voice Call Places a text-to-speech call that reads out a code character by character, using one of the vendor's pre-recorded scripts or a custom spoken message with your organization name filled in.
Verification
4- Send Verification Code Generates and sends a one-time code by SMS, WhatsApp or voice and manages the whole lifecycle. Calling it again for the same number resends the existing code, optionally on a different channel, which is how a "did not receive the code" button is served without issuing a second code.
- Verify Code Checks the code the user entered against the code in force for a number. Each code allows a fixed number of attempts before it stops being usable.
- Get Verification Status Returns the current verification state with no side effects: no message sent, no attempt consumed, nothing reset. This is the read a support flow should use.
- Invalidate Verification Invalidates the active code and returns the number to an unverified state. No message is sent and no credit is spent.
Contact Lists
6- Create Contact List Creates a list with a unique name, a description and up to four custom field labels, returning the list key every other contact operation needs.
- List Contact Lists Returns every list on the account with its name, description, creation date and key.
- Search Contact Lists Searches lists by name and returns each match's key and name.
- Rename Contact List Changes a list's name, which must remain unique within the account.
- Delete Contact List Deletes a list and every contact it holds. The operation cannot be undone, so it belongs behind a review step in any automated cleanup.
- List Contacts In List Returns every contact in a given list with name, phone number, email and creation date.
Contacts
4- Add Contact Adds a contact to a list, behaving as an upsert: a new number creates the contact, an existing one updates it. The response code tells the flow which happened.
- Update Contact Updates the email address of an existing contact, identified by phone number. Unlike Add Contact it does not create a missing contact, and reports that the contact does not exist instead.
- Delete Contact Removes a contact from a list, identified by phone number and optionally narrowed by email.
- Duplicate Contact To Another List Copies a contact into a second list while leaving the original in place, addressed by the numeric contact identifier.
Webhooks
4- Register Webhook Registers the account-wide webhook URL that receives delivery confirmation and customer reply events. The account holds one webhook slot, so registering replaces whatever was configured before.
- Get Webhook Configuration Returns the URL and current state of the single webhook configured on the account.
- Set Webhook State Enables or disables event delivery without removing the registered URL.
- Delete Webhook Removes the webhook URL and stops all delivery confirmation and reply events.
Reports
2- Generate Sends Report Returns every message sent within a date range with campaign name, timestamps, message reference, destination, body, delivery status, mobile operator and campaign type. Rate limited per account, so wide ranges beat frequent polling.
- Get Campaign Report Details Returns the aggregated breakdown of one campaign: delivery effectiveness as a percentage, total messages, and how many were delivered, failed, are pending or were not charged.
Account
1- Get Credit Balance Returns the credit still available on the account. Checking it before a large campaign is what stops a send from failing partway through on insufficient credit.
Digital Wallet
5- Get Wallet Configuration Lists the wallets on the account with their names, keys, app client names and plan types. The wallet key identifies the wallet in every other wallet operation.
- Add Wallet Customer Registers a customer in a digital wallet, associated with the staff member who enrolled them.
- Get Wallet Customer Reads a customer's wallet balance, optionally filtered by phone number. This is the read that should precede any balance change.
- Update Wallet Balance Adds balance to, or redeems balance from, a customer's wallet by a given amount. This moves stored value and has no reversing operation, so it is the natural approval point in any wallet flow.
- Register Wallet Sale Records a wallet sale or redemption against a customer, attributed to the staff member who processed it. The amount is required when the transaction adds balance.
Loyalty Cards
4- Get Loyalty Configuration Lists the loyalty programs on the account with their names, keys, app client names and plan types.
- Add Loyalty Customer Registers a customer in a loyalty program, associated with the staff member who enrolled them.
- Get Loyalty Customer Returns a customer's card details including name, phone number, date of birth, completed cycles and accumulated redemptions.
- Register Loyalty Stamp Records a stamp or sale for a customer on a loyalty program, attributed to the staff member who processed it.
Payments
1- Send Payment Request Sends a payment request link to a contact by SMS, within the vendor's documented body length, template name length and amount range. This puts a request for money in front of a customer, so the amount and the recipient are worth confirming before it goes.
Subaccounts
4- Create Subaccount Creates a subaccount under a manager account and returns the API key generated for it, so the subaccount can be integrated independently with its own credentials and balance.
- Get Subaccount API Key Returns an existing subaccount's API key by email address. Requires the manager key rather than a subaccount key.
- Archive Subaccount Archives and disables a subaccount by email address. Requires the manager key.
- Manage Subaccount Credits Transfers whole credits between the manager account and a subaccount, in either direction. This moves spending capacity between accounts, which is a decision rather than a routine sync.
Staff
3- List Staff Members Returns every staff member and collaborator with their identifier, name, phone number, branch, role and state. The identifier is what the wallet and loyalty operations use for attribution.
- Add Staff Member Registers a new staff member and returns the identifier created for them.
- Disable Staff Member Disables a staff member or collaborator by phone number. Useful as the offboarding step that stops new transactions being attributed to someone who has left.
Frequently Asked Questions
What can FlowRunner do with SMS Masivos?
FlowRunner agents can run Send SMS, Send WhatsApp Message, and Send Voice Call in SMS Masivos, plus 38 more actions.
Does connecting SMS Masivos to FlowRunner require OAuth?
No. SMS Masivos connects to FlowRunner with an API key, no OAuth flow required.
Can SMS Masivos trigger a FlowRunner workflow automatically?
SMS Masivos doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SMS Masivos
$100 in credits. No card required. Connect in minutes.