Resources · Make integration

Matrix Make integrationAutomate Matrix with Make.

Matrix can keep its rooms up to date without anyone typing in them. The Matrix Make integration gives you 9 modules, the bricks you drop into a scenario, the automation Make runs for you. Six of them act on a room, three read it. This page takes you from a blank scenario to a working one.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Matrix Make integration actually do?

It lets Make write into your Matrix rooms and read what is in them, on your behalf. You connect your Matrix account once, then any scenario can post a message, pull one back, list who is in a room or update the room itself. Matrix stays the place your team talks. Make becomes the hand that types when nobody is around to do it.

Three shapes come back over and over. An alert relay: something breaks in your monitoring tool, and Send a Message drops the line in the room your on-call people watch. A broadcast: List Public Rooms collects the public rooms of your server, and the same announcement lands in each of them. A cleanup: Update a Room corrects a room that drifted, and Leave a Room pulls the account out of the ones nobody opens.

One thing to know before you start. Matrix has no trigger module in Make, so nothing here watches a room and wakes a scenario up when a message arrives. The scenario starts somewhere else, on Make's own clock or on another app, and Matrix does its part once the run begins. If you were counting on a reaction within the second, that is the gap to plan around.

The same app lives on the other side too. The Matrix n8n integration goes through the nodes one by one, and the n8n vs Make comparison helps you settle the question before you build. If the scenario editor still looks like a maze, the Make training starts from the very beginning.

Connect

How do you connect your Matrix account to Make?

  1. 01

    Get your credentials out of Matrix

    Matrix is a network of servers, not one website, so start there. From your Matrix client, click Create Account if you do not have one yet, then click Edit next to the default homeserver to pick your Home Server. Your fully qualified user ID goes in the User field, your password in Password.

  2. 02

    Add a Matrix module and open the connection window

    Back in Make, drop any Matrix module into a scenario and hit Create a connection. A connection is your Matrix account tied to Make once, and every other Matrix module reuses it, in this scenario and in the ones you build later.

  3. 03

    Name it and hand over your credentials

    Give the connection a label in the Connection name field if you want to tell it apart later, that part is optional. Then paste the credentials you took from your Matrix account, or let Make guide you with the instructions it shows on screen. Once it is saved, the module can read what your account can see.

First scenario

Your first scenario: announce something in every public room

GoalEach time the scenario runs, Make collects the public rooms on your Matrix server and posts the same announcement in each of them.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario, and click the + to add your first module. A blank page with one empty circle on it is exactly what you should be looking at.

  2. 02

    Pick List Public Rooms

    Search Matrix by name, choose List Public Rooms, and click Create a connection if you have not linked your account yet. This module asks your server which of its rooms are open.

  3. 03

    Add Send a Message after it

    Click the + on the right of the first circle and pick Send a Message. Point it at the room that comes out of the search rather than typing one in, then write the text you want posted.

  4. 04

    Run it once and read what came through

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, a bundle being one item passed from a module to the next, here one public room.

  5. 05

    Set the schedule and switch it on

    Click the clock on the first module. A new scenario is set to run every 15 minutes, so pick the interval that matches how often your announcements change, then flip the scenario on.

Modules

What each Matrix module does

Matrix gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Matrix1

Edit a Message

Action

In MakeEdits an existing message.

Edit a Message rewrites a message that is already posted, in place, so nobody has to read a correction sitting three lines below the mistake.

When to use it
a status line in an ops room that should say resolved once your monitoring tool goes quiet.
Watch out
the module needs to know which message it is editing, so something upstream has to hand it that message.
Matrix2

Get a Message

Action

In MakeRetrieves an existing message from a specific room.

Point Get a Message at a room and it brings back the one message you name, ready to be reused by whatever comes next in the scenario.

When to use it
pulling the pinned brief of a project room into a report you build elsewhere.
Watch out
it fetches a message you already identify, so pair it with List Messages when all you know is the room.
Matrix3

Leave a Room

Action

In MakeLeaves an existing room.

Leave a Room takes the account behind your connection out of a room. The room keeps living without it, and your scenario stops seeing anything posted there.

When to use it
closing a client project where the shared room outlives the work.
Watch out
the other Matrix modules lose their way into that room afterwards, so keep this one last in the chain.
Matrix4

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call is the escape hatch. It reaches any endpoint of the Matrix API with the connection you already set up, which covers everything the eight other modules leave out.

When to use it
a room setting nobody turned into a module, with the API reference open beside you.
Watch out
it counts as one operation, meaning one module run charged to your plan, and you write the request yourself.
Matrix5

Send a Message

Action

In MakeSends a new message in a specific room.

Send a Message posts new text in the room you target. It is where most scenarios end, the moment something that happened elsewhere becomes a line your team can read.

When to use it
a deal signed in your CRM that the sales room should hear about without anyone relaying it by hand.
Watch out
placed after a search, it fires once per item returned, which is handy for a broadcast and noisy for anything else.
Matrix6

Update a Room

Action

In MakeUpdates an existing room.

A room that already exists can be changed with Update a Room, from whatever you fill in its fields. Nothing is created here, the room has to be there first.

When to use it
a project room that needs to reflect a rename decided in your project tool.
Watch out
no module in this list creates a room, so that part has to come from Matrix itself or from Make an API Call.
Matrix7

List Members

Search

In MakeLists all members in a specific room.

Every person in a room comes back as its own bundle when you run List Members. The scenario gets a roster it can count, compare or write down somewhere else.

When to use it
checking that everyone on a project actually made it into the shared room.
Watch out
anything you place after it runs once per member, so a message module here would write the same line over and over.
Matrix8

List Messages

Search

In MakeLists of all messages in a specific room.

List Messages pulls the messages of one room back into the scenario, to be read, stored or forwarded.

When to use it
archiving a support room into a spreadsheet before the thread gets too long to follow.
Watch out
you do not know in advance how many come back, and each one costs a run in the modules that follow.
Matrix9

List Public Rooms

Search

In MakeLists the public rooms on the server.

Ask List Public Rooms what the server hosts and it hands back the open rooms, one by one. That is how a broadcast finds its targets without a list you maintain by hand.

When to use it
an announcement that has to reach every open room of a community server.
Watch out
public means public, and rooms kept private stay invisible to this module whatever your account can otherwise see.
Need help

Need help automating Matrix with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the Matrix Make integration free?
Yes, on the Free plan. Matrix is a standard app in Make, so it comes with the free tier at no extra cost for the app. What the Free plan limits is the running: 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. Paid plans bring the interval down to 1 minute, lift the cap on active scenarios and give 40 minutes of execution. Any subscription on the Matrix side is separate and handled there.
02What do you need to connect Matrix to Make?
An active Matrix account, and that is the whole list. Make asks Matrix for the access tokens it will use, and a normal account is what produces them, so open one before you start if your team does not run a homeserver yet. Then it is four moves inside Make: add a Matrix module, click Create a connection, hand over the credentials or follow the on-screen instructions, save. Naming the connection is optional, though it helps once you have a few. From then on every Matrix module reuses it, in this scenario and the next ones.
03Does Matrix react in real time in Make?
No, because Matrix has no trigger module in Make. Nothing in this app sits and watches a room, so a scenario cannot start from a message landing in Matrix. You start it somewhere else instead. The plain route is the clock on the first module, set to every 15 minutes on a new scenario, which makes the Matrix modules run on each pass. The other route is to let a different app open the chain, a form, a CRM, a monitoring tool, or a Make webhook, the address Make gives you for an outside service to call, with Send a Message closing the job.
04What if a Matrix module is missing in Make?
Make an API Call takes over. It is one of the 9 modules, and it reaches any endpoint of the Matrix API using the connection you already made, so anything the eight named modules do not cover is still within reach of the scenario. You write the request yourself, which means keeping the Matrix API reference open. It counts as one run like any other module. One caveat worth knowing: the Matrix pages inside Make's app documentation are generated automatically and carry a warning that they may contain mistakes, so check anything critical against Matrix directly.
05Make or n8n for Matrix?
It depends on two things: how linear your flow is, and how much of the machinery you want to see. Make lays the scenario out as a chain of circles and keeps the plumbing out of sight, which is comfortable when the job is short, and this app has no trigger to wire up anyway. n8n puts more of the mechanics in front of you and accepts code when a case refuses to fit the boxes. Both cover Matrix, so the app itself rarely breaks the tie. Pick on the flow you are about to draw, not on the logo.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.