Resources · Make integration

Rocket.Chat Make integrationAutomate Rocket.Chat with Make.

Can Make run the busywork inside your Rocket.Chat workspace? The Rocket.Chat Make integration gives you 12 modules: 10 actions and 2 searches for channels, private groups and messages. It suits ops and support teams who live in chat, and this page walks you from connection to a first working scenario.

Try the Rocket.Chat integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Rocket.Chat Make integration do for you?

The Rocket.Chat Make integration links your Rocket.Chat workspace to Make, a no-code tool where you build a scenario (the automation itself, a chain of small bricks called modules). Your scenario can then open channels, manage private groups and post messages for you, based on what happens in your other apps.

Escalation rooms that open themselves. When a support ticket turns critical in your helpdesk, Create a Channel opens a room for the incident and Send a Message drops the ticket summary inside, so nobody has to set it up by hand while the customer waits.

A private space per new client. A deal marked as won in your CRM can start Create a Private Group for the account team. When the project closes, Rename a Private Group tags it as finished, or Delete a Private Group removes it.

A clear view of your workspace. List Channels and List Private Groups pull every room into Make, ready to be copied into a spreadsheet or a base such as the one described on the Airtable Make integration page.

Know the limits before you start. Rocket.Chat has no trigger module in Make, so it cannot start a scenario by itself: another app or the scenario's schedule does that. Anything outside the listed modules goes through Make an API Call. Rocket.Chat also has an n8n node; if you are weighing the two tools, the n8n vs Make comparison and the Rocket.Chat n8n integration page lay out both options.

Connect

How do you connect Rocket.Chat to Make?

  1. 01

    Add a Rocket.Chat module

    Open a scenario, click the + and search for Rocket.Chat. Pick any module, for example Send a Message, then click Create a connection. A connection is your Rocket.Chat account linked to Make once and reused by every Rocket.Chat module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like; it is optional but helps when you manage more than one workspace. Then either approve Make on the Rocket.Chat page that opens, or paste the key Rocket.Chat gives you, depending on what the form asks for.

  3. 03

    Save and check the lists

    Click Save. Back in the module, Make now reads your workspace and can offer the channels and groups it sees, so you pick them from a list instead of typing names from memory.

First scenario

Your first scenario: post a message to a Rocket.Chat channel

GoalWhen the scenario runs, Make looks up a Rocket.Chat channel and posts a message in it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + in the middle. That is where your first module goes.

  2. 02

    Add Get a Channel

    Search for Rocket.Chat, pick Get a Channel and create your connection. Choose the channel that should receive the message from the list Make shows you.

  3. 03

    Add Send a Message

    Click the + on the right of the first module and pick Send a Message. Map the channel from the previous module, then write the text you want posted.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time; open the bubble above each module to read the bundles it received (a bundle is one item passed along, here one channel).

  5. 05

    Set the schedule and switch it on

    Click the clock on the first module. A new scenario runs every 15 minutes by default, so adjust it to what makes sense for your message, then switch the scenario on.

Modules

Every Rocket.Chat module in Make, explained

Rocket.Chat gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Rocket.Chat1

Create a Channel

Action

In Make“Creates a new channel.”

Opens a brand new public channel in your workspace from inside a scenario, so a room exists the moment the work behind it starts.

When to use it
a new event, product launch or incident is logged in another app and the team needs a shared place to talk about it right away.
Watch out
each run creates a channel, so on a schedule without a filter you will end up with a pile of duplicates.
Rocket.Chat2

Create a Private Group

Action

In Make“Creates a new private group.”

Sets up a closed room that only invited members can read, which is the right home for anything touching contracts, pay or a single client.

When to use it
a deal is signed or a sensitive project begins and you want a discreet space instead of a public channel.
Watch out
pick this over Create a Channel whenever the content should not be visible to the whole workspace.
Rocket.Chat3

Delete a Channel

Action

In Make“Deletes a channel.”

Removes a public channel from Rocket.Chat for good, which keeps the sidebar tidy once a topic is over.

When to use it
an incident is closed or a campaign has ended and the room no longer serves anyone.
Watch out
a deletion cannot be undone from Make. Test it with Run once on a throwaway channel, and consider Rename a Channel if you might need the history later.
Rocket.Chat4

Delete a Private Group

Action

In Make“Deletes a private group.”

Erases a private group entirely, members and conversation included, as soon as your scenario reaches this step.

When to use it
a client relationship ends and your process says the dedicated room should disappear with it.
Watch out
this is the step to guard most carefully. Put a filter before it so it only fires on the exact group you mean.
Rocket.Chat5

Get a Channel

Action

In Make“Gets a channel.”

Fetches the details of one public channel so the next modules can reuse them, rather than guessing at an identifier.

When to use it
you already know which channel matters and want to check it exists, or hand its data to Send a Message or Rename a Channel.
Watch out
it returns a single channel; to look across all of them, use List Channels.
Rocket.Chat6

Get a Private Group

Action

In Make“Gets a private group.”

Reads the information of one specific private group, which gives later steps a reliable reference to work with.

When to use it
before renaming, deleting or posting into a known private group, to confirm it is the right one.
Watch out
it returns a single group; to go through all of them, use List Private Groups.
Rocket.Chat7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the Rocket.Chat API from your scenario, reusing the same connection, for anything the ready-made modules do not cover.

When to use it
you need an operation that none of the 12 modules above handle.
Watch out
this one expects you to know the Rocket.Chat API, so keep it for the gaps and try the named modules first.
Rocket.Chat8

Rename a Channel

Action

In Make“Renames a channel.”

Changes the name of an existing public channel, a gentle alternative to deleting it because the conversation stays in place.

When to use it
a project changes status and you want the channel name to show it, for example by adding a closed or archived prefix.
Watch out
people may search for the old name, so announce the change with Send a Message.
Rocket.Chat9

Rename a Private Group

Action

In Make“Renames a private group.”

Gives a private group a new name while keeping its members and messages exactly as they were.

When to use it
a client changes its company name, or an account moves from onboarding to regular follow-up and the room label should follow.
Watch out
it only renames; it does not add or remove members, which would need Make an API Call.
Rocket.Chat10

Send a Message

Action

In Make“Post a new message to channel, direct or private group.”

Posts a new message into a channel, a direct conversation or a private group, which makes it the module you will use most often.

When to use it
a form is submitted, a payment fails or an order ships in another app and the right people should hear about it in chat.
Watch out
map real data from earlier modules into the text, or every alert will look the same and people will stop reading.
Rocket.Chat11

List Channels

Search

In Make“Gets a list of channels.”

Returns the public channels of your workspace as separate bundles, one per channel, so the rest of the scenario handles each in turn.

When to use it
you want an inventory of rooms in a spreadsheet, or to spot channels worth renaming or removing.
Watch out
as a search it can return zero, one or many results, and every following module runs once per channel, which counts operations.
Rocket.Chat12

List Private Groups

Search

In Make“Gets a list of private groups.”

Pulls the private groups into Make and passes them along one bundle at a time.

When to use it
you are reviewing client rooms and want to know which ones still exist before a cleanup pass.
Watch out
each group is one bundle, so a Delete a Private Group placed right after would act on every one of them. Put a filter in between.
Need help

Need help automating Rocket.Chat with Make?

A person reads every message.

FAQ

Rocket.Chat and Make: common questions

01Is the Rocket.Chat Make integration free?
Yes. Rocket.Chat is a standard app in Make, so you can use it on the Free plan. That plan keeps you to 2 active scenarios, runs a scheduled scenario at most every 15 minutes, caps each run at 5 minutes and files at 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Make counts usage in operations, one per module per bundle, so a List Channels feeding Send a Message uses more than a single post.
02What does it take to connect Rocket.Chat to Make?
You need a Rocket.Chat account with access to the channels and groups you want to automate, plus a Make account. Add any Rocket.Chat module, click Create a connection, optionally name it, then authorize Make on the Rocket.Chat page or paste the key Rocket.Chat provides, and click Save. The documentation lists no special prerequisite. After that, every Rocket.Chat module reuses the same connection, and Make lists the channels and groups it can read, so you pick them from a menu instead of typing names from memory.
03Can Rocket.Chat trigger a Make scenario in real time?
No. Rocket.Chat has no trigger module in Make, neither scheduled nor instant, so a Rocket.Chat event cannot start a scenario on its own. You still have two ways in. Start the scenario with a trigger from another app, such as a new ticket or a won deal, and let the Rocket.Chat modules act after it. Or run the scenario on its schedule, every 15 minutes by default, with a search like List Channels as the first step. A webhook module from Make can also start it when another tool sends a request.
04What if Make has no Rocket.Chat module for your task?
Use Make an API Call. It reaches any endpoint of the Rocket.Chat API with the connection you already set up, so you can cover actions the 12 modules skip. You will need the Rocket.Chat API reference to fill in the request. Check the named modules first, since they already cover channels, private groups and messages without any request to write. The Make documentation gives no numeric limit for this app. If the API route feels heavy, another chat app with more modules may fit better.
05Make or n8n for Rocket.Chat: which one fits?
It depends on where your other automations already live. Make offers 12 Rocket.Chat modules covering channels, private groups and messages, plus Make an API Call for the rest, and you build everything visually. Rocket.Chat also has an n8n node, so the app itself does not force the choice. Look at which tool your team already knows, and which other apps your scenario has to touch. Test the same small flow in both if you are unsure, then keep the one your team can maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations