--- title: "Rocket.Chat Integration" description: "Post and manage messages, work with channels, private groups, and direct messages, administer users, and upload files against your self-hosted or cloud Rocket.Chat server over its REST API." url: https://flowrunner.ai/integrations/rocketchat date_modified: 2026-08-01T02:40:32-07:00 --- # Rocket.Chat [Communication](https://flowrunner.ai/integrations/category/communication-messaging) Post and manage messages, work with channels, private groups, and direct messages, administer users, and upload files against your self-hosted or cloud Rocket.Chat server over its REST API. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 28 actions · API key · available [Rocket.Chat website](https://rocket.chat/) · [Platform Documentation](https://developer.rocket.chat/reference/api) · Capability data verified 2026-07-14 1. A new-hire record appears in the HR system with a start date 2. Agent reads the hire's name, role, and team assignment 3. Agent confirms the record is complete and the start date is confirmed 4. Agent drafts the account details and the group memberships the hire needs 5. Agent posts the proposed account and access to the IT admin channel 6. An IT admin approves; only then does the agent call Create User and seed the onboarding group ## What This Integration Enables FlowRunner agents use Rocket.Chat to run notifications, onboarding, and triage on a server you control. An agent can broadcast alerts and build notifications into a channel or DM, create channels and private groups and seed them with members, pin, star, and react to messages to highlight what matters, provision and update user accounts, and share files into a room by URL. It resolves a channel name into its room ID when an action needs one. The administrative actions, creating users and managing access, are where the agent stops and asks, because on your own server those changes are yours to answer for. ### Without FlowRunner **Manual account setup**: IT creates each Rocket.Chat account and group by hand from an HR ticket **Access drift**: New hires wait for access, or get more than their role needs **No provisioning record**: Accounts get created with no clear note of who approved them ### With FlowRunner **Agent prepares onboarding**: The agent assembles the account and the right group memberships from the HR record **Human approves access**: An admin signs off before any account is created on the server **Logged provisioning**: Each account creation is captured with the admin who approved it ## Use Case Scenarios ### Onboarding with a provisioning gate When a new hire appears in the HR system, the agent assembles the account details and the group memberships the role requires, then posts the proposed account and access to the IT admin channel. An IT admin approves. Only then does the agent call Create User and Create Group to provision the account and a private onboarding group. Access is granted on purpose, by a person, with a record of who approved it. ### Build and deploy alerts When a build or deploy event arrives, the agent calls Post Message to alert the engineering channel with the status and a link. Failures can be pinned with Pin Message so the channel keeps the current problem visible until it clears. ### Summarized delivery to a requester The agent summarizes a long document with an AI connector, then calls Send Direct Message to deliver the summary to the requesting user by username. The person who asked gets the answer in a DM without digging through the source. ## Human-in-Loop Highlight The human-in-loop moment on Rocket.Chat is the provisioning gate. Posting, reacting, and pinning run on their own. Creating a user account on your server does not, because it grants standing access. When an onboarding workflow reaches the account step, the agent assembles the details and posts a request to the IT admin channel: "New hire in the support role needs an account and membership in the support-onboarding group. Approve to provision?" An admin approves or holds. Only an approval leads the agent to call Create User, and the approval is recorded. The agent prepares the onboarding. A person owns the decision to grant access. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 28 actions ### Messages 8 - **Post Message** Post a message to a channel by name or reference. Used for build alerts, reports, and notifications. - **Send Message** Send a message using the room ID form. Used when an action supplies a stable room ID. - **Update Message** Edit a message. Used to update a status in place. - **Delete Message** Delete a message. Used to clean up a resolved alert. - **Get Channel Messages** Read a channel's message history. Used to gather context before acting. - **Pin Message** Pin a message to keep an important update visible. - **Star Message** Star a message to triage or bookmark it. - **React to Message** Add an emoji reaction as a lightweight acknowledgement. ### Channels 9 - **Create Channel** Create a public channel. Used to provision a project space. - **Get Channel Info** Resolve a channel by name into its room ID and details. - **List Channels** List channels on the server. - **Archive Channel** Archive a channel to retire it without deleting history. - **Delete Channel** Delete a channel. - **Invite User to Channel** Add a user to a channel during onboarding. - **Kick User from Channel** Remove a user from a channel during offboarding. - **Set Channel Topic** Set a channel's topic. - **Set Channel Announcement** Set a channel's announcement banner. ### Groups 3 - **Create Group** Create a private group. Used for a sensitive or invite-only workflow. - **Get Group Info** Retrieve a private group's details. - **List Groups** List the private groups the account can see. ### Direct Messages 2 - **Create Direct Message** Open a direct message room with a user. - **Send Direct Message** Send a direct message to a user by username. ### Users 5 - **Get User Info** Look up a user account. - **Create User** Provision a user account. Used for onboarding automation, behind a human approval. - **Get Me** Return the token's account. Used as a connection check. - **Set User Status** Set a user's presence status. - **Update User** Update a user account. ### Files 1 - **Upload File to Room** Share a file into a room by URL. ## Frequently Asked Questions ### What can FlowRunner do with Rocket.Chat? FlowRunner agents can run Post Message, Send Message, and Update Message in Rocket.Chat, plus 25 more actions. ### Does connecting Rocket.Chat to FlowRunner require OAuth? No. Rocket.Chat connects to FlowRunner with an API key, no OAuth flow required. ### Can Rocket.Chat trigger a FlowRunner workflow automatically? Rocket.Chat doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Rocket.Chat?** This integration exposes Rocket.Chat to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/rocketchat. Site index: https://flowrunner.ai/llms.txt