Resources · Make integration

MatrixFlows Make integrationAutomate MatrixFlows with Make.

Can Make keep your MatrixFlows collections moving without code? The MatrixFlows Make integration gives you 12 modules: 1 scheduled trigger, 8 actions and 3 searches. This page shows how to link your account, build a first scenario and pick the right module for each job.

Try the MatrixFlows integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the MatrixFlows Make integration do for you?

The integration lets Make read and write the items stored in your MatrixFlows collections. You build a scenario, which is the automation itself: a chain of modules, each one a single brick such as a trigger, an action or a search. Make then runs that chain for you, so items, comments and files move without copy and paste.

Intake that files itself. A form or another app hands Make new data, and Create an Item in a Collection turns it into a MatrixFlows item. Upload an Attachment to an Item can then add the file that came with it.

Items that get a first reply. Watch Items in a Collection spots new items, and Comment on an Item in a Collection leaves a note on each one, so nobody opens an item that looks untouched.

Files that leave MatrixFlows. Download Attachments from an Item hands the files of an item to the next module, which can store them in the tool your team already uses.

Know the limit before you start: the official MatrixFlows documentation on Make is thin, with no field descriptions and no connection guide, and there is no Make an API Call module to fall back on. Test every module with Run once. If a run fails, the Make troubleshooting guide covers the usual errors, and the Make training helps if scenarios are new to you. Weighing another tool? Read n8n vs Make.

Connect

How do you connect MatrixFlows to Make?

  1. 01

    Add a MatrixFlows module

    In a scenario, click the +, search for MatrixFlows and pick any of its modules. Then click Create a connection. A connection is your MatrixFlows account linked to Make once and reused by every MatrixFlows module afterwards.

  2. 02

    Name it and authorize Make

    Give the connection a name if you plan to link more than one account, such as a test workspace and a live one. Then authorize Make on the MatrixFlows page that opens, or paste the key MatrixFlows gives you, depending on what the window asks for.

  3. 03

    Save and check the lists

    Click Save. Back in the module, Make now lists what it can read from your account, so you choose options from menus instead of typing them.

First scenario

Your first scenario with MatrixFlows and Make

GoalWhen a new item lands in a MatrixFlows collection, Make adds a comment to that item.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. That empty circle is where the first module goes, the one that starts everything.

  2. 02

    Place the trigger

    Search for MatrixFlows, choose Watch Items in a Collection and link your account with Create a connection. Then pick the collection to watch from the list Make shows you.

  3. 03

    Add the comment

    Click the + on the right of the trigger and pick Comment on an Item in a Collection. Map the item from the trigger so the comment lands on the item that just arrived, then write the note.

  4. 04

    Test with Run once

    Add a test item in MatrixFlows, then click Run once. Then read the bundles each module received, a bundle being one item passed from module to module.

  5. 05

    Schedule and switch on

    Click the clock on the trigger to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval allowed.

Triggers

What starts a MatrixFlows scenario

1 module starts a scenario when something happens in MatrixFlows. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by MatrixFlows as soon as it happens.

MatrixFlows1Watch Items in a Collection

Watch Items in a Collection

triggerIn the docs only

This trigger picks up items from the collection you choose and hands each one to the rest of your scenario as a separate bundle. It is the only way to start a scenario from inside MatrixFlows itself.

How it fires
scheduled. Make checks the app on the scenario's schedule, shown by the clock badge on the module, so nothing happens between two checks.
When to use it
whenever a new entry in a collection should set off work somewhere else, like a comment, a download or a record in another app.
Watch out
the documentation gives no detail on this module, so run it once on a test collection and read the bundles before you rely on what it returns.
Modules

Every MatrixFlows module, explained

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

MatrixFlows1

Comment on an Item in a Collection

ActionIn the docs only

Leaves a comment on an existing item, which gives your team a visible trace of what the automation did on that item.

When to use it
right after another module has acted on an item, to say that a file was stored or a status was checked.
Watch out
it needs the item to already exist, so map the item from an earlier module instead of typing it by hand.
MatrixFlows2

Create an Item in a Collection

ActionIn the docs only

Adds a brand new item to the collection you pick, filled with data mapped from earlier modules. It is how outside information enters MatrixFlows without anyone retyping it.

When to use it
a form, an email or another app produces something your team should track in a collection.
Watch out
pairing it with Watch Items on the same collection can make the scenario feed itself, so keep the two apart.
MatrixFlows3

Delete an Item in a Collection

ActionIn the docs only

Removes an item from a collection for good. Think of it as the cleanup step at the end of a flow, once the data lives somewhere else.

When to use it
test entries or duplicates that a filter in your scenario has already identified with certainty.
Watch out
a deleted item does not come back through Make, so run it once on a copy before pointing it at real data.
MatrixFlows4

Download Attachments from an Item

ActionIn the docs only

Pulls the files attached to an item and passes them on as bundles, ready for a storage app, an email or any module that accepts a file.

When to use it
documents gathered in MatrixFlows need to reach a shared drive or a colleague who never opens MatrixFlows.
Watch out
on the Free plan Make handles files up to 5 MB, so larger attachments call for a paid plan.
MatrixFlows5

Get an Item in Collection by ID

ActionIn the docs only

Fetches one specific item when you already hold its ID, and returns its current content to the modules that follow.

When to use it
another app stored the MatrixFlows ID earlier and you now need the latest version of that item before acting on it.
Watch out
without a valid ID the step has nothing to return, so map the ID from a previous module rather than guessing it.
MatrixFlows6

List All Items in a Collection

SearchIn the docs only

Returns the items of a collection, each one as its own bundle, so the next modules run once per item. A search like this can return zero, one or many results.

When to use it
a one-off sweep through a whole collection, such as copying its entries into a spreadsheet.
Watch out
every bundle that follows costs operations on your plan, so a large collection adds up quickly.
MatrixFlows7

List All Users in a Workspace

SearchIn the docs only

Returns the people in a MatrixFlows workspace, one bundle per user, which gives your scenario a roster to work with.

When to use it
syncing the team list into another tool, or finding the right person before you mention them in a comment.
Watch out
the documentation says nothing about which user details come back, so read the output of a Run once before mapping anything.
MatrixFlows8

List Inbox Conversations

SearchIn the docs only

Reads the conversations sitting in your MatrixFlows inbox and hands each one to the next module as a separate bundle.

When to use it
you want conversations copied into a helpdesk, a CRM or a report instead of reading them one by one.
Watch out
it is a search, not a trigger, so it only runs when something earlier in the scenario starts it.
MatrixFlows9

Update an Item in a Collection

ActionIn the docs only

Changes an item that already exists, keeping it in step with what happened in another app instead of creating a second copy.

When to use it
a deal closes in your CRM or a payment clears, and the matching MatrixFlows item should show it.
Watch out
you need the item's ID first, which usually comes from Get an Item in Collection by ID or from one of the list searches.
MatrixFlows10

Upload an Attachment to an Item

ActionIn the docs only

Attaches a file coming from an earlier module to a MatrixFlows item, so the document sits right next to the record it belongs to.

When to use it
a contract signed elsewhere or a PDF received by email should end up on the matching item.
Watch out
the file must travel through the scenario first, and the Free plan caps files at 5 MB.
MatrixFlows11

Upload an Image to an Item

ActionIn the docs only

Adds a picture to an item through its own dedicated action, so an image produced or received elsewhere ends up stored on the right MatrixFlows record.

When to use it
product photos, screenshots or generated visuals that the team should see when it opens the item.
Watch out
pick this module for pictures and Upload an Attachment for documents, since the two are listed as different actions.
Need help

Need help automating MatrixFlows with Make?

A person reads every message.

FAQ

MatrixFlows and Make: common questions

01Is the MatrixFlows Make integration free?
Yes. MatrixFlows is a standard app in Make, so its modules work on the Free plan. That plan allows 2 active scenarios, a shortest interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Every module run counts as an operation, which is what Make tallies on your plan. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Any cost on the MatrixFlows side is a separate question this page does not cover.
02What is needed to connect MatrixFlows to Make?
A MatrixFlows account and a Make account. Make's documentation lists no specific prerequisite for this app, so the standard connection flow applies. Add a MatrixFlows module, click Create a connection, give it a name if you like, then authorize Make on the MatrixFlows page or paste the key the app provides. Click Save and the connection is reused by every MatrixFlows module in your scenarios. Since the documentation is limited, test with Run once straight away to confirm the connection reaches the right workspace.
03Does the MatrixFlows trigger in Make react in real time?
No. Watch Items in a Collection is a scheduled trigger: Make checks MatrixFlows on the scenario's schedule instead of being called the moment an item appears. A new scenario runs every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Paid plans can check as often as every minute. The documentation gives no detail on this module, so look for the clock badge on it in the editor and run the scenario once to see what it returns.
04What if a MatrixFlows module is missing in Make?
It depends on what you need. The MatrixFlows app in Make has 12 modules and no Make an API Call module, so there is no generic way to reach a feature outside that list. Start by combining what exists: the list searches and Get an Item in Collection by ID often cover a read you thought was missing. If the gap remains, another app in your stack may hold the same data, or the team can look at the case with you through the help form on this page.
05Make or n8n for MatrixFlows?
It depends on your criteria. In Make, MatrixFlows comes with 12 ready modules, 1 scheduled trigger, 8 actions and 3 searches, and no Make an API Call module. Many apps also have an n8n node, but this page does not confirm one for MatrixFlows, so check that first. Then compare how each tool fits the scenarios you plan to build and the tools your team already runs. The n8n vs Make comparison linked above goes through the differences without ranking one over the other.
Same platform

Other docs you might need on this stack.

Browse all integrations