MessengerOS
Email MarketingSend email and SMS campaigns through a MessengerOS account, using template-based or custom content. Agents deliver campaign messages and handle the subscribe and unsubscribe lifecycle.
What This Integration Enables
MessengerOS is a send pipe, and the connector treats it as one. There is no audience builder here and no segment engine: an agent supplies the recipient, the content and the delivery channel, and MessengerOS delivers it as email or SMS, storing the recipient as an audience contact on the way through. What makes it worth writing a careful workflow against is how the API answers. Sends and subscribes are processed in the background, so a successful call means the request was accepted, not that anything was delivered. More importantly, the send and subscribe endpoints report rejections on HTTP 200 with an error code in the status field, which means a naive integration reads a rejected send as a completed one. FlowRunner's connector surfaces those coded rejections as errors rather than passing the 200 through, so a workflow branches on the truth instead of on the status line.
The other operation worth building around is Count SMS Characters. It reports the character count, whether the text contains Unicode characters that reduce per-segment capacity, and the resulting number of message segments, all before anything is sent. That turns the cost of a broadcast into a number an agent can put in front of a person, which is the difference between an approval that means something and an approval that is a rubber stamp.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Welcome message the moment a customer signs up
A signup lands in the product or in a form built on Typeform. The agent picks the channel from what the record actually holds, calling Send Email Using Template when there is an address and Send SMS Using Template when there is only a number, passing the personalisation values the template expects. The recipient is stored as an audience contact in the same call, with distribution lists and custom info attached, so the person exists in MessengerOS without a separate import step. Because the response only confirms acceptance, the workflow treats the send as pending rather than done and moves on.
Transactional mail with your own HTML and a real attachment
A finance workflow generates a statement and needs to mail it with the sender, subject, preview line and body under its own control rather than a template's. Send Email With Custom Content takes all four, and an attachment can be supplied either as a public file URL that the connector downloads and encodes, or as Base64 content directly. The document produced upstream, in Google Sheets or a document generator, reaches the customer without a person assembling the mail.
Pausing a live sequence for a maintenance window
Before a planned migration, the agent calls Get Automations to list the email and SMS automations in the project and Set Automation Status to pause the ones that would mail customers about a system that is about to be offline. When the window closes, the same workflow resumes them. Separately, when a customer converts, Unsubscribe Email From Automation removes them from the nurture sequence they no longer belong in, so the conversion event and the sequence exit are one step rather than two teams' problem.
Human-in-Loop Highlight
An SMS cannot be recalled, and its cost is not a property of the message, it is a property of the encoding. Count SMS Characters is the only operation in this connector that tells the truth before the send: a body that reads as a single short message will report three segments if someone pasted a curly apostrophe or an emoji into it, because Unicode cuts the per-segment capacity. So the broadcast agent runs Count SMS Characters against the exact final text, multiplies by the recipient count, and when the result crosses the threshold the team set, it stops. The digital andon cord pulls, and the agent posts to the operations channel: "Incident notice to 6,200 numbers. Count SMS Characters reports 3 segments per message because the body contains Unicode, so this send is 18,600 segments, not 6,200. Send as written, send a rewritten ASCII version, or hold?" A person decides whether the wording is worth the multiplier, and the human-in-the-loop step returns that decision to the flow. The agent does not get to make the call itself, because the money is spent the moment the request is accepted and the acceptance response will not tell it anything is wrong.
Agent Capabilities
10 actions- Send Email Using Template Sends an email to a recipient using a template built in MessengerOS. The request is accepted for background processing, and the recipient is stored as an audience contact with any distribution lists and custom info supplied alongside it.
- Send Email With Custom Content Sends an email with the sender, subject, preview line and HTML body supplied in the request instead of drawn from a template. Used when the content is generated upstream by another step in the workflow.
SMS
3- Send SMS Using Template Sends an SMS using a MessengerOS template, storing the recipient as an audience contact with any name fields, distribution lists and custom info. The template's personalisation values are passed in the same call.
- Send SMS With Custom Text Sends an SMS with the message text supplied in the request. Placeholders in the text are replaced from the template parameters, so a single custom body can still be personalised per recipient.
- Count SMS Characters Calculates how many message segments a given text needs, reporting the character count and whether the text contains Unicode characters that reduce per-segment capacity. This is the guard step that makes broadcast cost visible before anything is sent.
Audience
1- Add Subscriber Adds a subscriber to audience lists or updates an existing subscriber's details, requiring an email address or a phone number. The same operation unsubscribes or re-subscribes a contact through its unsubscribed flag, so consent changes are a single call.
Automations
3- Get Automations Retrieves the email and SMS automations in a project, returning each automation's API key and name. Agents call it to resolve a human readable automation name into the key the status operations need.
- Set Automation Status Pauses or resumes an automation. Used to take a sequence offline for a maintenance window and bring it back afterwards as part of the same workflow rather than as a reminder.
- Unsubscribe Email From Automation Removes an email recipient from an automation so they stop receiving its messages. The usual trigger is a conversion, where continuing to nurture someone who already bought is the failure.
Projects
1- Create Project Creates a new project in the MessengerOS account and returns its API key, defaulting to the account's company when none is named. Used when provisioning a sending context for a new brand, client or region.
Frequently Asked Questions
What can FlowRunner do with MessengerOS?
FlowRunner agents can run Send Email Using Template, Send Email With Custom Content, and Send SMS Using Template in MessengerOS, plus 7 more actions.
Does connecting MessengerOS to FlowRunner require OAuth?
No. MessengerOS connects to FlowRunner with an API key, no OAuth flow required.
Can MessengerOS trigger a FlowRunner workflow automatically?
MessengerOS doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with MessengerOS
$100 in credits. No card required. Connect in minutes.