AllMySMS
MessagingConnect AI agents to AllMySMS, a French SMS gateway for single and bulk campaign messaging. Agents send SMS and voice campaigns, manage contact lists and the opt-out blacklist, and pull delivery reports and replies so outreach to French customers stays tracked and compliant.
What This Integration Enables
AllMySMS is a French gateway run by MS Innovations, and the parts of its API that look like quirks are mostly the French market showing through. Sender names are constrained to three to eleven alphanumeric characters starting with a letter. A custom sender is only applied to French destinations when the message carries an opt-out mention such as STOP au 36180. The voice product does not place calls at all, it deposits a pre-recorded WAV or MP3 straight onto a French voicemail, from a landline-style number, for French numbers only. If you are messaging French consumers, that specificity is the reason to pick this connector over a generic international gateway. If you are not, most of what makes it good does not apply to you.
The operational shape is a campaign with a full reporting tail behind it. Send SMS and Send SMS Campaign both take a Simulate flag that validates the recipients, the message part count and the cost without creating or sending anything. That turns the price of a run into something an agent can put in front of a person before it is spent rather than after. Personalized recipients merge per-contact values into the body through numbered parameters. Behind the send, List Campaigns and Get Campaign carry status and counters, Get Campaign Delivery Reports resolves per-recipient outcomes into five documented statuses, and three separate reply actions read inbound answers at different scopes. The account also holds contact lists with declared custom field structures, a blacklist fed by STOP replies, a URL shortener on AllMySMS domains that exists because operators frequently block third-party shorteners, and full subaccount administration for an agency running client accounts under one master. Delivery report and inbound reply callbacks are configured through actions rather than a FlowRunner-managed subscription, because AllMySMS stores exactly one URL per event type for the whole account and validates at configuration time that it answers within five seconds, so this connector ships no triggers.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The price of the run, before the run
A promotion is ready for a segment of 14,000 French subscribers pulled from HubSpot. Message length matters here in money terms, because a single SMS holds 160 GSM-7 characters and anything longer is concatenated into parts that are each billed. The agent calls Send SMS Campaign with Simulate enabled, which returns the validated audience, the SMS count and the cost without dispatching anything. It compares that figure against the balance from Get Account Information and posts both into the marketing channel in Slack. If a stray accented character has pushed the message into an extra part across 14,000 recipients, that shows up as a number in a message rather than as a line on an invoice three weeks later.
Delivery outcomes reconciled per recipient
The campaign is out and the identifier is held. Later that day the agent calls Get Campaign with detailed statistics enabled for the aggregate view, then Get Campaign Delivery Reports for the per-recipient rows. Each report carries the number, the reception date and one of five documented statuses: programmed, delivered, undelivered, sent, refused. Undelivered and refused are not the same problem and the agent routes them differently, marking refused numbers for review against the blacklist and queueing undelivered ones for a retry window. Reports only exist once the operators have returned them, so the sweep runs on a schedule rather than immediately after the send.
A voicemail that never rings the phone
A French clinic needs to remind patients of an appointment without interrupting their day. The agent calls Create Voice Code, and the practice manager dials the AllMySMS interactive voice response line, enters the code and records the message in their own voice. Get Voice Code confirms the recording date and duration are populated, and Download Voice Message pulls the audio into FlowRunner file storage so the recording is archived where the practice can find it. Then Send Voice Campaign deposits it on each patient's voicemail from the clinic's own landline-style number. Nobody's phone rings. The message is waiting when they next check, which for a reminder is exactly the right amount of intrusion.
Human-in-Loop Highlight
The sender name on this connector looks like branding and is actually a switch that turns the reply channel off. Send a French campaign from the shared short code and everything works: recipients can answer, Get Pending Replies and Get Campaign Replies return what they said, and a STOP reply lands the number on the blacklist automatically where Get Blacklist will find it before the next send. Set a custom sender and the short code that recipients would have answered to is gone. The vendor is explicit that replies can only be collected when the default short code sender was used, and the connector says so on all three reply actions. Nothing errors. The campaign delivers, the delivery reports look healthy, and the reply queue is simply empty, which is indistinguishable from an audience that had nothing to say. Meanwhile the custom sender is only applied to French destinations at all when the body ends with an opt-out mention such as STOP au 36180, so the message either carries that text or the branding silently does not take effect. An agent can weigh none of this, because both outcomes are successful sends. So it stops. It presents the composed message, the sender it was handed and the audience size, and asks the campaign owner: "This campaign is set to send as CLINIQUE to 14,000 French numbers. A custom sender removes the short code recipients reply to, so replies and STOP opt-outs will not reach the account, and the body must carry an opt-out mention for the sender to apply at all. Send as CLINIQUE with STOP au 36180 appended, or send from the shared short code and keep replies?" The owner answers once per campaign shape, not once per message. Get Pending Replies deserves the same care for a related reason: it consumes what it returns, so replies fetched by a step that then fails are gone from the API for good, and any flow using it should persist first and process second.
Agent Capabilities
34 actionsSMS
3- Send SMS Sends a single SMS to one mobile number in international format without a leading plus sign. Messages longer than 160 GSM-7 characters are concatenated and billed as several parts. The sender name is optional and falls back to a shared five digit short code. Set Simulate to validate the recipient, the part count and the cost without creating or sending anything.
- Send SMS Campaign Sends a campaign to many recipients in one request, either as plain numbers or as personalized recipient objects that merge per-contact values into the body through numbered parameters referenced as `#param1#` and onward. Personalized recipients take precedence when both are supplied. A campaign message can span at most eight concatenated parts. Simulate validates the audience and the cost without sending.
- Delete Scheduled Campaign Deletes a scheduled campaign that has not started sending. Deletion is permanent and cannot be undone, and a campaign already in flight cannot be deleted at all, which makes the window between scheduling and dispatch the only place a mistake can still be caught.
Campaigns
2- List Campaigns Lists SMS or voice campaigns sent or scheduled within a date range, ordered by sending date, with each campaign's identifier, status, message, sender, contact and SMS counts and dates. Returns up to 100 per call with an offset for paging. Used to reconcile what a flow believes it sent against what the account actually holds.
- Get Campaign Retrieves a single campaign by identifier with its status, message, sender, counts, scheduling dates and tracked link. Delivery statistics add delivered, undelivered, refused and click counters, and detailed statistics add a per number breakdown of delivery status and click activity. This is the aggregate view an agent posts into a channel after a run.
Delivery Reports
2- Get Campaign Delivery Reports Retrieves the delivery reports recorded for every recipient of a campaign, each carrying the number, the reception date and a numeric status with its description: programmed, delivered, undelivered, sent or refused. Reports appear only once operators have returned them, so schedule the sweep rather than reading immediately after the send.
- Get SMS Delivery Report Retrieves the delivery report of a single SMS by its identifier, with the recipient number, the reception date and the same five status values. Used where one message matters on its own, such as a transactional confirmation attached to an order.
Replies
3- Get Pending Replies Retrieves inbound replies not yet fetched, up to 1000 per call. Replies returned here are marked consumed and will not appear again, so a flow should persist them in the same step that reads them. Replies are only collectable when the campaign used the default short code sender.
- Get Campaign Replies Retrieves the replies received for a specific campaign, with the responding number, the reply text and the reception date. Unlike the pending queue this does not consume them, which makes it the safe route for reprocessing or for a second flow that needs the same answers.
- Get SMS Reply Retrieves the reply received for a single SMS, with the responding number, the text and the reception date. Used to close the loop on one transactional message rather than sweeping a campaign.
Blacklist
2- Get Blacklist Retrieves the account's blacklisted numbers with the reason each was added and the date it was recorded. Numbers arrive here through STOP opt-out replies or manual unsubscription. Supply a campaign identifier to see only the numbers blacklisted from that campaign, which is a direct read on how a message landed.
- Delete Blacklisted Number Removes a number from the blacklist so it can receive messages again. Deletion is permanent. Numbers blacklisted through a STOP reply cannot be removed with this operation at all, which is the vendor drawing a line an integration cannot cross.
Account
2- Get Account Information Retrieves the authenticated account with its remaining balance in euros, the number of messages that balance buys in the reference country, the account status, contact and company details, and the alerting level that governs access to the priority sending channel. Used as the balance guard before a large run.
- Ping API Checks that the API is reachable and reports its response time in seconds. Requires no authentication, which makes it a connectivity check that stays meaningful even when a credential is the thing that broke.
Contact Lists
5- Create Contact List Creates an empty list and declares its custom field structure. This creates the structure only. Every custom field declared here must then be supplied for each contact added later or the request is rejected, so the schema decision made once here constrains every import afterward.
- List Contact Lists Retrieves every contact list on the account with its name, contact count, lock state and creation date, plus the total number of lists. Used to resolve a list before reading or writing to it.
- Get Contact List Contacts Retrieves every contact stored in a list, each carrying its mobile number plus the custom fields declared when the list was created. Used to audit an audience before a campaign points at it.
- Update Contact List Contacts Adds contacts to a list or updates existing ones, matching on the mobile number, with one entry per declared custom field. Omitting a declared field fails the request. This operation cannot delete contacts. The response reports how many were added, ignored and detected as duplicates, so a flow should read those counts rather than assume the whole batch landed.
- Delete Contact List Deletes a list together with the contacts it holds. Deletion is permanent and cannot be undone.
Short URLs
2- Shorten URL Shortens a URL on an AllMySMS short domain so it fits in a message and can be click tracked. Supply a domain from the domain list or let one be picked. The vendor recommends its own short links because operators frequently block messages containing third-party shorteners, which makes this a deliverability decision rather than a cosmetic one.
- List Short URL Domains Retrieves the short domains available to the account for the shortener. Used to pick a domain deliberately rather than accepting a random one, which matters when recipients recognize the domain.
Webhooks
3- Configure Webhook Sets the callback URL AllMySMS pushes events to for a given type, with delivery report and inbound reply payloads delivered as query parameters. The URL must answer within five seconds with the literal string `OK` or the configuration is rejected. One URL is stored per type for the whole account, so this replaces whatever was configured before, including an endpoint someone else depends on.
- Get Webhooks Retrieves the callback URLs currently configured on the account for delivery reports and inbound replies. Read this before configuring anything, since the slot is global and overwriting it is silent.
- Delete Webhook Removes the callback URL configured for a webhook type. The URL stops receiving pushes immediately, so anything downstream that was consuming those events goes quiet without an error.
Subaccounts
5- List Subaccounts Retrieves every subaccount of the master account with login, contact, company and billing details, plus the total count. The backbone of an agency setup where each client sends under their own account.
- Get Subaccount Retrieves one subaccount by login, including its status, remaining balance in euros, available message count, reference country and contact details. Used to check a client's balance before running their campaign.
- Create Subaccount Creates a subaccount under the master account and returns its own API key. Login and password constraints are enforced by the vendor, a subaccount cannot be given an alerting level higher than its parent, and post-payment is only available when the master account is itself in post-payment.
- Update Subaccount Updates an existing subaccount, modifying only the fields supplied. Not available while impersonating a subaccount through the subaccount configuration item, which prevents a delegated session from editing the account it is operating as.
- Delete Subaccount Deletes a subaccount of the master account. Deletion is permanent and cannot be undone, and it takes the subaccount's own API key with it.
Voice Messages
5- Send Voice Message Deposits a pre-recorded voice message on a single recipient's voicemail, for French numbers only, from a French landline-style sender. The audio is fetched from a URL and must be a WAV or MP3 between five and thirty seconds. Simulate validates the recipient and cost without depositing anything. No phone rings.
- Send Voice Campaign Deposits a pre-recorded message on many voicemails as a campaign, for French numbers only, using either an audio URL or a voice code recorded through the vendor's interactive voice response line. Simulate validates the audience and cost first, which matters more here than on SMS because the recording cannot be edited after it is out.
- Create Voice Code Creates an eight digit code used to record a message through the AllMySMS interactive voice response line. Call the line, enter the code when prompted, and record. The code is then what Send Voice Campaign plays, which is how a human voice gets into an automated flow without a studio.
- Get Voice Code Retrieves a voice code with its label, creation date, recording date and the duration of the recording. Recording date and duration stay null until something has actually been recorded, which makes this the check that confirms a person completed their half of the task.
- Download Voice Message Downloads the audio recorded on the interactive voice response line for a voice code and stores it in FlowRunner file storage, returning a downloadable URL. Saved with a `.wav` extension by default, overridable through file settings if the account records another format. Used to archive what was actually said before it goes out to an audience.
Frequently Asked Questions
What can FlowRunner do with AllMySMS?
FlowRunner agents can run Send SMS, Send SMS Campaign, and Delete Scheduled Campaign in AllMySMS, plus 31 more actions.
Does connecting AllMySMS to FlowRunner require OAuth?
No. AllMySMS connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can AllMySMS trigger a FlowRunner workflow automatically?
AllMySMS doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with AllMySMS
$100 in credits. No card required. Connect in minutes.