SMS Partner
MessagingConnect AI agents to SMS Partner, a French SMS and RCS gateway. Agents send single and bulk SMS, deliver RCS rich cards and carousels, track delivery statuses, and manage contacts and stop lists so French and international campaigns stay deliverable and compliant.
What This Integration Enables
SMS Partner is the French gateway operated by SAS NDA Media in Paris, and it covers a wider span than most connectors in this category. The obvious half is messaging: single and personalized bulk SMS, two-way sending from a rented long number, dashboard-built surveys, and a full RCS surface with text, files, rich cards, and carousels. The less obvious half is that SMS Partner also sells access to its own opted-in contact base, targeted by gender, age range, interest category, socio-professional segment, and French departments or postcodes. That makes this the one connector here where a flow can acquire an audience as well as message one, which is a genuinely different kind of capability and deserves to be treated as such.
The French market rules are enforced by the platform, which is a large part of why you would choose a French gateway rather than a global one for French traffic. Marketing SMS is blocked between 20:00 and 08:00 on weekdays and all day on Sundays and public holidays, and messages submitted in those windows are held until 08:00 on the next working day rather than dropped. Sending actions carry an option to append the STOP notice the regulation requires. Scheduling works in five-minute steps up to three months ahead, and a scheduled message can no longer be canceled within five minutes of its send time, which is a real deadline a flow should treat as one. Leave the sender name empty and the message is delivered from an operator short code, or supply three to eleven alphanumeric characters. Long-number sending uses a virtual number rented on the account instead, which is what gives the recipient somewhere to reply.
Three build details are worth knowing before wiring flows. The RCS surface must be activated on the account by SMS Partner support, and every RCS action accepts an optional SMS failover block that delivers a fallback text to handsets which do not accept RCS, so a rich campaign does not silently miss the people who cannot receive it. Number checking splits into a free format lookup that validates against the international numbering plan and a billed HLR verification that queries the operator network asynchronously and posts results to your notify URL. And there are no triggers on this connector: SMS Partner documents the payload shapes for inbound replies, STOP requests, and delivery receipts, but the account-wide callback URL is a single dashboard slot with no route to read or write it, so registering one programmatically would destroy the customer's own. The per-message reply and delivery callback fields are exposed as ordinary parameters on the sending actions instead, covering only messages this connector itself sends.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A launch that uses the rich channel and still reaches everyone
A retailer is launching a product and wants more than 160 characters of it. The agent builds an RCS carousel of up to eight cards, each with its own media and suggestions, and attaches an SMS failover block carrying the plain-text version with a short link. Handsets that accept RCS get the carousel. Handsets that do not get a message rather than nothing, which is the difference between a rich channel and a partial one. Recipients are capped at 500 per request, so the agent batches accordingly and tags every send with a campaign tag. Afterwards Get Status By Tag returns per-recipient status across every send that carried the tag, which is how a campaign assembled from batches gets reported as one thing.
Suppression that runs itself and un-suppression that does not
Opt-outs arrive through several routes. SMS Partner adds recipients who reply STOP to the stop list automatically, and the agent handles the rest: an unsubscribe collected on the website goes to Add Number To Stop List immediately, without asking anyone, because it only ever reduces contact. The mirror image is not symmetrical. Remove Number From Stop List takes the entry identifier rather than the phone number, so the agent must first find the entry in List Stop List, and even holding the identifier it does not act. Restoring contactability reverses a decision the customer made, so the agent raises it as an automation exception with the opt-out date attached and lets a person weigh it against whatever newer consent record exists in HubSpot.
A regional team with its own budget and its own ceiling
A franchise network wants each region to run local campaigns without access to the group balance. The agent provisions with Create Sub-Account, which returns the sub-account's token and its own API key, and the type it is created as, simple or advanced, is permanent. Credit moves in euros with Add Sub-Account Credits and comes back with Remove Sub-Account Credits, so a monthly allowance is something a flow can administer on a schedule. Get Sending Statistics reports cost and volume per period, which the agent summarizes into a monthly report alongside the email side of the program from Brevo. Delete Sub-Account is permanent and is never part of an automated cleanup.
Human-in-Loop Highlight
The gate on SMS Partner is Rent Contacts, and it is different in kind from every other gate on a messaging connector. Every other one asks a person to approve reaching your own customers. This one asks whether to buy an audience of people who have never heard of you. SMS Partner sells access to its own opted-in contact base, targeted by gender, age range, interest category and sub-category, socio-professional segment, and French departments or postcodes, and the purchase is committed by a single call that returns a rental token. There is no unrent. What makes this a clean gate rather than a nervous one is that the agent can genuinely do all the analysis first. Calculate Contact Rental Reach returns how many contacts match a brief and what they would cost, and Price Contact Rental returns the cost for a chosen volume per locality. Both rent nothing and bill nothing. The arithmetic is complete before anybody decides.
So the agent presents a finished case and stops at the commitment. What it posts is the whole picture with the irreversibility named: "Rental brief for the Occitanie launch. Targeting: 25 to 44, interest category Maison et jardin, departments 31, 34, 66. Calculate Contact Rental Reach returns 84,200 matching contacts. Price Contact Rental quotes 12,600 EUR for 60,000. Our own stop list holds 3,140 numbers, which this rented file will not have been washed against. Rent Contacts commits the purchase and returns a rental token; there is no reversal action on this API. Commit at 60,000, narrow the brief, or hold?" A person answers that in the Flow conversation, and the answer is what runs Rent Contacts.
That is the shape human-in-the-loop takes under Orchestration as a Service. The judgment is not arithmetic, which the agent already did. It is whether renting a third-party audience is something this brand does at all, whether the targeting brief is one you would be comfortable explaining, and whether messaging 60,000 strangers is worth what it does to a sender name you spent years making familiar. Nothing in an API models that. Two neighboring actions belong behind the same treatment for narrower reasons. Cancel Scheduled SMS stops working within five minutes of the send time, so a flow that discovers a problem late has a hard deadline rather than a retry. Request HLR Verification is billable and asynchronous across up to 500 numbers, so sweeping an uncleaned list is spending real money to learn that the list is bad.
Agent Capabilities
39 actionsMessaging
5- Send SMS Sends one message body to up to 500 recipients, with an alphanumeric sender, a campaign tag, scheduling in five-minute steps up to three months ahead, per-message reply and delivery callback URLs, the appended STOP notice, Unicode mode, and a no-cost sandbox mode.
- Send Bulk SMS Sends a distinct message body to each of up to 500 recipients in one request, which is the route for personalized campaigns. Returns the batch cost plus a per-recipient breakdown.
- Send SMS From Virtual Number Sends from a long virtual number rented on the account so the recipient can reply directly to it. Takes no scheduling parameter, so it is an immediate send by design.
- Send Survey Sends a survey built in the SMS Partner dashboard, identified by its survey identifier, to up to 500 recipients.
- Cancel Scheduled SMS Cancels a scheduled send that has not yet been dispatched. It stops working within five minutes of the send time, which is a real deadline rather than a soft one.
RCS
4- Send RCS Text Sends a plain text conversation message with up to four suggestions. RCS must be activated on the account by SMS Partner support first.
- Send RCS File Sends an image, video, or document referenced by a public URL, with an optional SMS failover for handsets that do not accept RCS.
- Send RCS Rich Card Sends one card with a title, description, and media, laid out vertically or horizontally, with up to four card suggestions and eight conversation suggestions.
- Send RCS Carousel Sends up to eight scrollable cards, each with its own media and suggestions. Built for product sets and multi-option offers rather than single announcements.
Delivery Status
4- Get Message Status Returns status, cost, country, and timestamp for one message to one recipient. Status is Delivered, Not delivered, or Waiting, and receipts can take up to 48 hours depending on the operator, so Waiting is not a failure.
- Get Bulk Status Returns the per-recipient status of every message under one message identifier.
- Get Status By Tag Returns the per-recipient status of every message carrying a campaign tag, across all the sends that used it. The action that makes a campaign assembled from batches reportable as one thing.
- Get Multiple Statuses Returns status for up to 500 arbitrary number and message-identifier pairs in one call.
Account
2- Get Account Credits Returns SMS, ECO, and HLR credits, queued messages, and the monetary balance. Doubles as an inexpensive credential check.
- Get Sending Statistics Returns cost and volume per period for the previous month, the last twelve months, or a custom date range. Rate limited to five calls per minute, more tightly than the rest of the API.
Contact Management
9- Create Contact Group Creates a group. A contact on this platform always lives inside a group, so the group comes first.
- List Contact Groups Returns the account's contact groups.
- Delete Contact Group Deletes a group. The contacts inside it go with it, and there is no undelete.
- Add Contact Adds one contact to a group.
- Add Contacts In Bulk Imports up to 500 contacts in one request with a per-reason error report covering opted-out, invalid, duplicate, and already-present numbers. That report is the useful part: it tells you exactly why a number did not land.
- Update Contact Updates a contact by its identifier. Updating does not move a contact between groups.
- List Contacts Returns the contacts of one group. A group identifier is mandatory, because the API offers no way to list every contact on the account at once.
- Get Contact Details Reads one contact by its identifier.
- Delete Contact Removes one contact from its group.
Opt-Out Management
3- Add Number To Stop List Adds a number to the account's stop list so it is excluded from every future send. SMS Partner adds STOP repliers automatically, so this route is for opt-outs collected through your own channels.
- List Stop List Returns every opted-out number with its entry identifier and opt-out date. The entry identifier is what the removal route needs, so this read always comes first.
- Remove Number From Stop List Removes an entry by its entry identifier, not by the phone number. This restores contactability, which makes it a consent decision rather than a data correction.
Sub-Accounts
5- Create Sub-Account Creates a simple or advanced sub-account and returns its token and its own API key. The type is permanent. Sub-accounts must be enabled on the account by SMS Partner support first.
- List Sub-Accounts Returns one page of twenty sub-accounts with tokens, API keys, and credit balances.
- Add Sub-Account Credits Moves credit in euros from the main account to a sub-account. Real money moves between balances, so it belongs in a flow with a spend policy behind it.
- Remove Sub-Account Credits Moves credit in euros back from a sub-account to the main account.
- Delete Sub-Account Permanently deletes a sub-account by its token. Its API key stops working immediately, wherever it is held.
Number Verification
2- Look Up Number Format Validates up to 500 numbers against the international numbering plan and returns country, prefix, line type, and the E.164, international, national, and RFC 3966 forms. Documented by the vendor as free, and it does not query the operator network.
- Request HLR Verification Runs an asynchronous Home Location Register query for up to 500 numbers, returning a campaign identifier and cost while the per-number results are posted to your notify URL. Billable, and it delivers no message to the handset.
Contact Rental
5- Calculate Contact Rental Reach Returns how many contacts match a targeting brief and what they would cost. Nothing is rented and nothing is billed, so this is safe to run across as many briefs as a plan needs.
- Price Contact Rental Returns the cost of a brief for a chosen volume per locality. The second free read, and the one that turns a reach figure into a budget decision.
- Rent Contacts Commits the purchase and returns a rental token. This is billable and there is no reversal action anywhere on this API.
- Get Contact Rental Status Polls a rental until its file is ready.
- Download Contact Rental File Returns the rented numbers as JSON rather than as a binary file. Note that a rented file has not been washed against your own stop list, so that comparison is work the flow still has to do.
Frequently Asked Questions
What can FlowRunner do with SMS Partner?
FlowRunner agents can run Send SMS, Send Bulk SMS, and Send SMS From Virtual Number in SMS Partner, plus 36 more actions.
Does connecting SMS Partner to FlowRunner require OAuth?
No. SMS Partner connects to FlowRunner with an API key, no OAuth flow required.
Can SMS Partner trigger a FlowRunner workflow automatically?
SMS Partner doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SMS Partner
$100 in credits. No card required. Connect in minutes.