The Bot Platform
HRMessage employees, manage user attributes, and pull bot analytics with The Bot Platform, which builds chatbots for Microsoft Teams and Workplace. Agents reach staff in the tool they already have open.
What This Integration Enables
The Bot Platform is not a chat tool and it is not a notification service. It is a bot with a curated library behind it. Somebody in internal communications or HR sat down and built messages in the Message Builder, with the buttons, the tone and the approvals that go with speaking to twenty thousand employees in the company's voice. That library is the asset. This connector exists so an agent can reach it, address it to the right person, and populate the user attributes the messages read from, without a human relaying a spreadsheet into the bot dashboard.
Agents send a pre-built message by its UUID, send plain text without a pre-built message, or send a raw payload in the channel's own format, which is the Workplace Send API message format or the Microsoft Graph chatMessage format depending on where the bot is connected. Recipients are identified by email address or user ID, which means the addressing key is whatever your HR system already holds. Agents also read and write user attributes, each of which carries a flag marking whether it holds personally identifiable information, and pull the bot's daily top-line metrics: active people, new and unique visitors, subscribers, unsubscribes, messages sent and engagement per user. The Bot Platform's webhooks are configured inside the bot builder rather than through the API, so this connector is a send and sync surface rather than a listening one, and flows start from the system that has news to deliver.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Ticket updates that reach the requester where they are
An employee raises a request in ServiceNow. When the ticket moves to awaiting information, the agent resolves the requester by email, finds the approved status-update message with List Messages, and sends it through their bot conversation in Microsoft Teams. The employee answers in the same thread they were already in, and the agent writes the reference onto their attribute record so the next update can find it. Nobody has to remember to check a portal.
Onboarding sequences that start from the HR record
A new starter is created in BambooHR. The agent calls Create User Attribute once to establish the fields the onboarding messages read from, then sets the person's department, manager and start date with Set Multiple User Attributes in a single call, and sends the first approved onboarding message. The sequence the comms team designed runs on data the HR system already owned, on the day it should, without an export.
Engagement reporting that survives the month
A scheduled flow calls Get Analytics each morning for the previous day and appends the row to a Google Sheets dashboard: active people, unique visitors, subscribers, unsubscribes, messages sent, engagement per user. Over a quarter this turns a set of point-in-time screenshots into a trend, and the unsubscribe line becomes an early signal that a campaign is asking too much of people rather than a number discovered at review time.
Human-in-Loop Highlight
This connector has three ways to speak and they do not carry equal weight. Send Message delivers something already built in the Message Builder, which means the wording passed through whoever owns employee communications. Send Text Message and Send Raw Payload Message bypass that library entirely and put whatever the flow composed in front of an employee, in the company's voice, in the chat client they trust for real internal news. There is no draft state and no recall. The moment a raw send goes out it is a message from the employer.
So the gate here is not on the send, it is on leaving the library. When an agent can match the situation to an approved message it sends it and moves on, because that wording is already governed. When it cannot, the agent stops rather than composing something. It routes to the internal communications owner through Slack or email with the exact copy it would have sent and the size of the audience: "No approved message covers a payroll cutoff change. Proposed text to 412 people in Operations: 'Your July timesheet must be submitted by 17:00 on Thursday 24th, a day earlier than usual, because of the bank holiday.' Send this once, add it to the Message Builder as a reusable message, or hold?" That is the digital andon cord applied to internal communications. The line stops when the agent would have to invent language, and the human decides whether the words are the company's.
Agent Capabilities
9 actionsMessaging
4- Send Message Sends a pre-defined message from the bot's Message Builder to a single user, identified by email address or user ID, referenced by its UUID and delivered on the channel the bot is connected to. Returns the created activity with its ID. Used for anything covered by approved wording, which should be the default path.
- Send Text Message Sends one or more plain text messages to a single user without requiring a pre-built message, each text becoming a separate message in the conversation. Returns the created external activity with its ID. Used for wording that is not in the library, which is the case that belongs behind an approval.
- Send Raw Payload Message Sends one or more raw channel payloads to a single user in the native format of the bot's channel, either the Workplace Send API message format or the Microsoft Graph chatMessage format for Teams. Accepts a single JSON object or an array of payloads. Used when a message needs channel-specific structure the Message Builder does not express.
- List Messages Retrieves every pre-defined message built in the bot's Message Builder, each with its UUID, name and content parts such as text and buttons. Used to resolve a situation to approved wording, and to detect when no approved wording exists.
User Attributes
4- Set User Attribute Sets the value of a single user attribute on a bot user, identified by email address or user ID, with the attribute referenced by its UUID. Used to write a case reference, a status or a milestone that a later message will read back.
- Set Multiple User Attributes Sets several user attributes on a bot user in one call. Used when a record changes upstream and department, manager and start date all need to move together.
- List User Attributes Retrieves every user attribute defined on the bot, each with its UUID, name and whether it is marked as personally identifiable information. Used to discover attribute UUIDs, and to see which fields carry personal data before a flow writes to them.
- Create User Attribute Creates a new user attribute on the bot, optionally marked as personally identifiable information. Returns the created attribute with its UUID. Used once when a new automated sequence needs a field the bot does not yet have.
Analytics
1- Get Analytics Returns the bot's top-line metrics for a given date: active people, new visitors, unique visitors, subscribers, unsubscribes, total messages sent and engagement per user. Used to build a daily trend in a reporting tool rather than reading a dashboard by hand.
Frequently Asked Questions
What can FlowRunner do with The Bot Platform?
FlowRunner agents can run Send Message, Send Text Message, and Send Raw Payload Message in The Bot Platform, plus 6 more actions.
Does connecting The Bot Platform to FlowRunner require OAuth?
No. The Bot Platform connects to FlowRunner with an API key, no OAuth flow required.
Can The Bot Platform trigger a FlowRunner workflow automatically?
The Bot Platform doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with The Bot Platform
$100 in credits. No card required. Connect in minutes.