Resources · n8n integration

RocketChat n8n integrationAutomate RocketChat with n8n.

Every alert your team needs should land in the right channel, without anyone copying it there. The RocketChat n8n integration exposes one node operation, Post a message, with 19 attachment options behind it. Made for teams running their own chat server next to the rest of their tools.

Try the RocketChat integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the RocketChat n8n integration actually cover?

The RocketChat node takes a workflow result and posts it as a message in a RocketChat channel, or as a direct message to one person. It carries a single operation, and that operation is the delivery end of an automation: something happens elsewhere, n8n formats it, RocketChat displays it to the people who need to act on it.

One operation sounds thin until you look at what rides on it. A message can be plain text, or it can carry an attachment with a color bar, an author name, a clickable title, a thumbnail and up to 19 configurable options. That is the difference between a wall of pasted logs and a card someone can act on at a glance.

First pattern, the internal alert. A workflow reads a sheet with Google Sheets, spots the rows that need a human decision, and posts one message per row with the record link as the attachment title. The ops channel becomes the queue.

Second pattern, the mirror. Teams that keep RocketChat for internal talk but still receive customer traffic elsewhere push a copy into a private room, whether that traffic arrives through Gmail or already lands in Slack for another department. Same workflow, two destinations, no manual forwarding.

Third pattern, the direct ping. The Channel field accepts a person as well as a room, so an approval request reaches the one person who can answer it instead of a channel where it will scroll away.

Where the node stops: it posts, and that is all it does. Creating a channel, inviting a user, uploading a file, reading message history or listing rooms are not part of it. Those calls go through the HTTP Request node, which reaches any endpoint of the RocketChat REST API while reusing the same credential. There is also no RocketChat trigger in n8n, so a workflow that watches for something starts with a Schedule Trigger or a Webhook and uses RocketChat only at the end. If you want the wider view before committing, the n8n review and the n8n training cover the parts around the node.

Connect

How do you connect RocketChat to n8n?

  1. 01

    Check the permission on your account

    The credential runs on a personal access token, and RocketChat only lets an account generate one when it holds the create-personal-access-tokens permission. On a self-hosted server an admin grants it per role, so ask before you start clicking. Using a dedicated automation account rather than a human one keeps the message author readable later, when someone wonders who posted that alert at night.

  2. 02

    Generate the access token

    In RocketChat, open your avatar, then Account, then Personal Access Tokens, and create one. The screen shows two values and only shows them once: the token itself, and the user identifier attached to it. Copy both somewhere safe before closing the panel. RocketChat will not display the token again, and a lost token means generating a new one and updating the credential.

  3. 03

    Fill the credential in n8n

    In n8n, go to Credentials and create a Rocket.Chat credential. It asks for three things: User ID, the identifier shown when the token was generated, Auth Key, the personal access token itself, and Domain, your workspace URL, the same address you type to open RocketChat. A credential is created once and then appears in the dropdown of every RocketChat node you add later.

Actions

What can the RocketChat node do?

The RocketChat node exposes 1 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourcePost Message
Chat✓

Chat

1 operation
01

Post a message

chat.postMessage

What you see in n8n

Notes & use cases

The single operation posts a message to a RocketChat channel or a direct message.

Key parameters

  • Channel: name with its prefix, #ops-alerts or @alex, often {{ $json.channel }}.
  • Text: the message body, optional if an attachment carries it.
  • Color, Author Name, Title, Title Link: four Options fields building the card's bar, byline and headline.
  • Image URL, Audio URL, Video URL: attach media by URL, the node never uploads a file.
  • Text under Options: a second field, the attachment's own text, not the message Text above.
Use cases
a titled card instead of a bare link.
Need help

Need help automating RocketChat with n8n?

A person reads every message.

FAQ

RocketChat and n8n, the usual questions

01Is the RocketChat n8n integration free?
Yes on the n8n side. The RocketChat node ships with n8n, so there is nothing to install and nothing extra to pay, whether you work on n8n Cloud or on a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both cases: same node, same credential, same result. What your RocketChat server costs is a separate question and depends on how you run it, which this page does not cover. The only real requirement is an account allowed to generate a personal access token.
02What credentials does the RocketChat node need?
One credential, based on an API access token. You create it once in n8n and every RocketChat node in every workflow can pick it from a dropdown. It holds three values: User ID, displayed at the moment you generate the token, Auth Key, which is the personal access token itself, and Domain, your workspace URL. The account generating the token needs the create-personal-access-tokens permission, otherwise the option never appears in the RocketChat interface. There is no authentication selector on the node, so this is the only path available.
03What are the limits of the RocketChat node in n8n?
The node covers one operation, posting a message to a channel or as a direct message. Everything else in the RocketChat API sits outside it: creating rooms, managing users, uploading files, reading history. For those, the HTTP Request node calls any endpoint directly and can reuse the same credential through predefined authentication, so you are not blocked, only one node further. The depth of the node is on the message itself, with attachment options for color, author, title link, image, audio, video and timestamp, 19 in the Options collection.
04Can n8n react to a new RocketChat message in real time?
No, not with a dedicated node. RocketChat has no trigger node in n8n, so nothing watches the server on its own. A workflow involving RocketChat starts with something else: a Schedule Trigger that runs at a fixed interval, an n8n Webhook, which is a URL n8n exposes so another service can call it and start the run, or the trigger of another tool in your setup. RocketChat then sits at the end of the workflow, as the destination. If you need incoming events, a RocketChat outgoing integration pointed at an n8n Webhook URL is the direction to explore.
05n8n or Make for RocketChat?
It depends on where you want the automation to run. Make is hosted, with no self-hosting option, and bills by operation, so its cost grows with message volume. n8n runs on your own server or on n8n Cloud, with the same workflow either way, which matters when your RocketChat server is already self-hosted for data control reasons, since both then stay inside your perimeter. Make has a visual editor many people find quicker at first. n8n gives more room on expressions and on falling back to raw API calls when a node stops short, which is exactly the situation here.
Same platform

Other docs you might need on this stack.

Browse all integrations