Brosix
CommunicationSend notifications into Brosix team chat through the Notifications API. Agents deliver alerts and workflow updates to the channel a team already watches.
What This Integration Enables
Brosix is bought by teams that want internal chat they control rather than a public workspace, and its Notifications API reflects that. The API delivers messages into Brosix. It does not read them back out. There is no list of rooms, no message history, no contact directory, and no event stream, so this connector has exactly one action and no triggers. FlowRunner agents use it as an outbound alerting surface: a place to put a fact in front of a named user or chat room the moment a flow produces it.
That constraint matters when you design the flow, so it is worth stating plainly rather than discovering later. A Brosix step can announce, but it cannot wait for an answer, because the agent has no way to read the reply. Any decision the flow needs has to come back through a channel FlowRunner can actually hear, which is what the human-in-the-loop step is for. Brosix carries the outbound half. The judgment arrives somewhere the agent is listening.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Failed job alerts routed to the team that owns the job
A nightly reconciliation flow finishes and finds two integrations that errored. Rather than emitting one generic alert, the agent maps each failing job to the team that owns it and looks up that team's Brosix channel key. Each room gets only the failure it is responsible for, with the job name, the error code, and a link to the run record. The teams stop filtering a shared alert stream for the lines that concern them.
New support ticket announced to the room on duty
A ticket arrives in the helpdesk and the agent classifies it by product area and severity. High-severity tickets are pushed into the on-duty support room in Brosix with the customer, the symptom, and the first diagnostic the agent already ran. Because the agent has done the triage before the message lands, the person who picks it up starts from a summary rather than from a raw ticket body. Companion systems like Zendesk or Freshdesk supply the ticket; Brosix supplies the room.
Scheduled report delivered where the managers already are
A flow assembles a daily operating summary from Google Sheets and Stripe, formats it as a short digest, and delivers it into a management chat room every morning. The report arrives in chat instead of an attachment, so nobody has to open anything to read the top line. When a figure crosses a threshold the flow was told to watch, the agent stops and asks a person whether to escalate before it sends anything to a wider room.
Human-in-Loop Highlight
A Brosix channel is bound to exactly one recipient, a single user or a single chat room, and the binding lives in the channel key rather than in the message. That means the agent chooses who reads the message by choosing a key, and this connector has no delete action, so a message delivered to the wrong room stays there. The gate sits before the send. When a flow selects the destination key dynamically, routing by owning team or by customer, and the alert body carries account names or figures, the agent stops: "This alert names Northwind and their outstanding balance. I resolved the destination to the Collections room key. Send there, send to the Finance leads room instead, or send a version with the account detail stripped?" The ops owner answers through the channel FlowRunner is listening on, and the agent sends once, to the room a person picked.
Agent Capabilities
1 actionsNotifications
1- Send Channel Message Delivers a text message into a Brosix Notifications API channel, which forwards it to the user or chat room that channel was created for in the Brosix Web Control Panel. The channel is selected by API key: the service key is used by default, and passing a different Channel API Key sends to a different recipient without reconfiguring the connection. Used for alerts, escalations, and scheduled digests, and used with a dynamic key when one flow serves several teams.
Frequently Asked Questions
What can FlowRunner do with Brosix?
FlowRunner agents can run Send Channel Message in Brosix.
Does connecting Brosix to FlowRunner require OAuth?
No. Brosix connects to FlowRunner with an API key, no OAuth flow required.
Can Brosix trigger a FlowRunner workflow automatically?
Brosix doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Brosix
$100 in credits. No card required. Connect in minutes.