Integration · Team chat
AI agents for Rocket.Chat
Post messages and thread replies to Rocket.Chat channels and direct messages, read a room's history or a thread, search a room, and look up rooms and people, on your own Rocket.Chat server or Rocket.Chat Cloud workspace.
- Actions
- 8
- Read
- 7
- Write
- 1
Actions
What your agents can do in Rocket.Chat
8 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 7
Look things up. Nothing changes.
Who am I
Reads the account the token belongs to: _id, username, name, emails, status, roles and utcOffset.
List my rooms
Lists every room the account is in — public channels, private groups and direct messages — at update[].
Read a room's messages
Reads a room's messages, newest first, at messages[]: each with _id, msg (the text), u (username, name), ts, tmid (thread parent) and tcount (thread replies).
Read a thread
Reads the replies in a thread, by the thread's first message ID (tmid), at messages[]: each with _id, msg, u and ts.
Search a room
Searches one room's messages for text, at messages[] (each with _id, msg, u, ts).
Get a room
Reads a room by ID or by name (without #) at room: _id, name, fname, t (c, p or d), topic, description, usersCount, msgs (message count) and lm (last message time).
Find a person
Reads a person by username (without @) or email at user: _id, username, name, status (online, away, busy, offline), active, roles and utcOffset, as far as the account may see them.
Write 1
Create, change or send.
Post a message
Posts a message (Markdown allowed) as the token's user: to a channel by name (#general), to a person as a direct message (@jane), or to a room by its ID.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Rocket.Chat account.
What you enter
- Personal access token
Settings
- Server address
- User ID
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Rocket.Chat data
Ask a question in plain words. The agent can list my rooms, read a room's messages or read a thread in Rocket.Chat, then answers with what it found.
- 02
Let an agent update Rocket.Chat
Have the agent post a message in Rocket.Chat as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Work from your CRM
Give one agent HubSpot and Rocket.Chat: it can search contacts in HubSpot and post a message in Rocket.Chat in the same run.
FAQ
Rocket.Chat and MyDeepAgents
Can MyDeepAgents connect to Rocket.Chat?
Yes. The Rocket.Chat connector has 8 actions: 7 read and 1 makes changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Rocket.Chat?
Paste an API key from your Rocket.Chat account. You'll need: Personal access token. The connection also asks for: Server address and User ID. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Rocket.Chat without asking?
Only if you let it. Its one action that changes data can be set to wait for a person's approval before it runs.
Can I use Rocket.Chat in workflows as well as agents?
Yes. Every Rocket.Chat action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Rocket.Chat to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.