Resources · Make integration

Mural Make integrationAutomate Mural with Make.

Can Make keep your Mural boards in step with the rest of your tools? Yes. The Mural Make integration gives you 22 modules: 4 triggers, 14 actions and 4 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Mural integration on Make See the 22 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mural Make integration automate?

The Mural Make integration links your Mural workspace to Make so boards, rooms, areas and sticky notes can be created, updated or read without anyone clicking through Mural. You build a scenario (the automation itself, a chain of steps) out of modules, and each module is one brick: a trigger that starts things, an action or a search.

A board that opens with its brief already on it. Watch Murals spots every new mural, then Create a Sticky Note drops the agenda or the rules of the workshop onto it. Facilitators stop copying the same note by hand.

Workshop output that leaves the board. Watch Sticky Notes picks up each new note and hands it to the next module, so ideas from a retro can land in a task tool or a spreadsheet. Pair it with the Airtable Make integration if your backlog lives there.

Tidy rooms for each project. Create a Room and Duplicate a Mural let a project manager spin up a room with a template board as soon as a project starts elsewhere.

Be aware of one limit: Make's own documentation for Mural is thin. It says there is not enough public information about the app to write a full guide, so field details are best discovered in the module itself. If a module stalls, Make troubleshooting covers the usual causes. Mural may also have a node on n8n; the n8n vs Make comparison helps you weigh the two platforms.

Connect

How do you connect Mural to Make?

01
Add a Mural module
In your scenario, click the +, search for Mural and pick any module. In the panel that opens, click Create a connection. A connection is your Mural account linked to Make once, then reused by every Mural module.
02
Name the connection
This step is optional, but a clear name helps as soon as you link more than one workspace. Something like the team or client name is enough to tell connections apart later in the dropdown.
03
Authorize Make and save
Make sends you to Mural's page to grant access, or asks for a key if the app gives you one. Approve, come back to Make and click Save. The module can now read your murals.

First scenario

Your first scenario with Mural

GoalWhen a new mural is created in Mural, Make adds a starter sticky note to it.

01
Create the scenario
Open the Scenarios page, create a new scenario and click the big +. Search for Mural and choose Watch Murals as the first module.
02
Link your account
Click Create a connection and authorize Make on Mural. Once linked, Make lists what it can read from your account, so there is nothing to type from memory.
03
Add the sticky note
Click the + to the right of the trigger and pick Create a Sticky Note. Map the mural returned by Watch Murals so the note lands on the board that was just created.
04
Test with Run once
Create a test mural, then click Run once. Each module shows the bundles it received (a bundle is one item passed along, here one mural). Check the note appeared.
05
Schedule and switch on
On the first module, open the clock: a new scenario checks every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Then switch the scenario on.

Triggers

Mural triggers: what starts your scenario

4 modules start a scenario when something happens in Mural. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Mural as soon as it happens.

Mural1Watch Areas

Watch Areas

Scheduled trigger

In Make“Triggers when a new area is created.”

Watch Areas starts your scenario each time someone adds an area to a board, handing Make the new area so later modules can file it, announce it or react to it. It gives you a signal each time a board gains a new section.

How it fires

scheduled. Make checks the app on the scenario's schedule, shown by the clock badge on the module, so new areas are picked up at the next check rather than the second they appear.

When to use it

when a new zone on a shared board means work for someone, such as a new client section that should be logged in your tracker.

Mural2Watch Murals

Watch Murals

Scheduled trigger

In Make“Triggers when a new mural is created.”

Every freshly created mural becomes a bundle in Make with Watch Murals, which makes it the natural entry point for anything that should happen to a board right after it exists: a starter note, a log entry, a message to the team.

How it fires

scheduled. Make checks the app on the scenario's schedule; the clock badge reminds you that boards are collected in batches at each run.

When to use it

when your team opens a mural per workshop or per client and you want each one prepared or recorded without a manual step.

Mural3Watch Rooms

Watch Rooms

Scheduled trigger

In Make“Triggers when a new room is created.”

This trigger reacts to each new room created in Mural and passes it on so the rest of the scenario can prepare it. For many teams, a new room is the signal that a new project or team space has opened.

How it fires

scheduled. Make checks the app on the scenario's schedule, so a room created between two checks is found at the following one.

When to use it

when opening a room should kick off setup elsewhere, such as creating a starter mural with Create a Mural or noting the project in a spreadsheet.

Mural4Watch Sticky Notes

Watch Sticky Notes

Scheduled trigger

In Make“Triggers when a new sticky note is created.”

Watch Sticky Notes turns each new note on the board into a bundle, which is how ideas captured during a session can travel to other tools without anyone retyping them.

How it fires

scheduled. Make checks the app on the scenario's schedule; each check can return several notes, and each note it processes counts as operations on your plan (one operation is one module running on one bundle).

When to use it

after a brainstorm or retro, to push every note into a backlog or a sheet.

Watch out

avoid a Create a Sticky Note step on the same board, or the scenario will feed itself.

Modules

Mural modules: actions and searches

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

Mural1

Create a Mural

Action

In Make“Creates a new mural.”

A blank board appears in your workspace the moment the scenario reaches this module, ready for the next steps to fill it. It saves the round trip into Mural whenever a new project, client or workshop needs its own space.

When to use it

when an event outside Mural, like a signed deal or a new ticket, should give the team a fresh board. Choose Duplicate a Mural instead if you want a template's content.

Mural2

Create an Area

Action

In Make“Creates a new area on mural.”

Adding an area gives an existing board a new zone, so incoming content has an obvious place to go instead of piling up in one corner. Useful when a board is shared by several topics or clients.

When to use it

when a new participant, topic or sprint joins a running board. Map the mural from an earlier module or from Search Murals so the area lands on the right board.

Mural3

Create a Room

Action

In Make“Creates a new room.”

With Create a Room, Make opens a new room in Mural for you, giving a project or team its own space before anyone asks for it. It is often the first brick of a setup flow, followed by Create a Mural.

When to use it

at the start of a project tracked elsewhere. Watch out: run it once per project, or a retried scenario can leave duplicate rooms behind.

Mural4

Create a Sticky Note

Action

In Make“Creates a new sticky note.”

This action writes a sticky note straight onto a board, so information from a form, a CRM or a support tool shows up where the workshop happens. It is the most direct way to bring outside data into Mural.

When to use it

to post an agenda on a new board or to drop each new request onto a triage mural. Watch out: never pair it with Watch Sticky Notes on the same board.

Mural5

Delete a Mural

Action

In Make“Deletes an existing mural.”

Removing a board from the scenario keeps the workspace clean once a project closes, without someone hunting through old murals. The module deletes the mural you point it to, nothing more.

When to use it

when a project is archived in your main tool. Watch out: treat the deletion as final and test on a throwaway mural with Run once before pointing it at real boards.

Mural6

Delete a Room

Action

In Make“Deletes an existing room.”

Delete a Room clears out a whole room when its purpose is over, which is handy for temporary spaces like a hiring panel or an event. Choose it over Delete a Mural when the room itself should go.

When to use it

at the end of a short-lived collaboration. Watch out: read it first with Get a Room to confirm it is the right room before letting the scenario remove it.

Mural7

Duplicate a Mural

Action

In Make“Creates a new mural from existing one.”

Duplicating copies an existing mural into a new one, so a carefully built template (canvas, columns, instructions) can be reused without rebuilding it. It beats Create a Mural whenever the board should not start empty.

When to use it

for a recurring format such as onboarding, a client kickoff or a retro. Keep one master board untouched and let the scenario copy it each time the event happens.

Mural8

Get a Mural

Action

In Make“Retrieves an existing mural.”

Fetching one mural brings its details into the scenario so later modules can reuse them, for instance to post its name in a message or record it in a sheet. It works on a board you already know.

When to use it

when a previous module handed you a specific mural. If you only know a name or need several boards, start with Search Murals instead.

Mural9

Get a Room

Action

In Make“Retrieves an existing room.”

Get a Room reads a single room and passes its details to the next modules, which helps when a scenario must check a room before acting on it. It needs the room to be identified already.

When to use it

before Update a Room or Delete a Room, to confirm you have the right space. To find rooms by criteria or list them all, reach for Search Rooms.

Mural10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the listed modules does what you need, this one lets you call any endpoint of Mural's API from the scenario, reusing the same connection. It is the escape hatch that covers the rest of the app.

When to use it

for an operation missing from the 22 modules. Watch out: you write the request yourself, and Make's documentation for Mural is limited, so test each call with Run once.

Mural11

Update a Mural

Action

In Make“Updates an existing mural.”

Changing an existing mural from Make keeps boards aligned with what happens elsewhere, for example renaming one when a deal changes stage. It saves someone reopening the board to fix a title.

When to use it

when the source of truth sits in another tool and Mural should follow it. Get the mural first, from a trigger, Search Murals or Get a Mural.

Mural12

Update an Area

Action

In Make“Updates an existing area.”

Update an Area edits a zone that already exists on a board, so labels or content follow changes in your process without anyone reopening the mural. Pick it instead of Create an Area to avoid stacking duplicates.

When to use it

when a status or owner changes in your project tool. Find the target with Search Areas before this step so the scenario knows which area to touch.

Mural13

Update a Room

Action

In Make“Updates an existing room.”

Room details can drift from reality as projects evolve; this module brings them back in line from the scenario. Nobody has to remember to fix the room by hand.

When to use it

when a project is renamed or handed to another team in your main tool. Pair it with Search Rooms or Get a Room to point at the right room.

Mural14

Update a Sticky Note

Action

In Make“Updates an existing sticky note.”

Editing a note that is already on the board lets outside progress show up in Mural, such as a ticket moving to done. Nobody has to hunt for the note and retype it.

When to use it

to mirror status changes from another tool. Locate the note with Search Sticky Notes first, and filter so only the notes that changed get updated.

Mural15

Search Areas

In Make“Searches for areas or lists them all.”

Search Areas finds areas matching what you ask, or lists them all, and returns zero, one or several bundles. Each bundle then runs through the modules that follow, one after the other.

When to use it

to find the zone to update or fill. Watch out: many results mean many bundles, and each one costs operations in the modules that follow.

Mural16

Search Murals

In Make“Searches for murals or lists them all.”

Looking up boards by criteria, or listing every one, is the job of Search Murals. It is how a scenario finds the right mural when all you have is a name or a context, not the board itself.

When to use it

before Update a Mural, Duplicate a Mural or Delete a Mural. Watch out: several matches return several bundles, so tighten the search before acting.

Mural17

Search Rooms

In Make“Searches for rooms or lists them all.”

This search returns the rooms that fit your query, or all of them, as separate bundles. It gives the scenario a way to reach a team's space without hard-coding it, which keeps the flow working when rooms change.

When to use it

to route new content to the room of the matching project. If you already hold the room from a trigger, Get a Room is simpler.

Mural18

Search Sticky Notes

In Make“Searches for sticky notes or lists them all.”

Pulling notes from a board in bulk is what Search Sticky Notes is for: it lists them all or only those matching your query, one bundle per note, ready to export or update.

When to use it

after a workshop, to send the whole board's output to a sheet in one pass. Watch out: each note returned counts as operations in every module that follows.

Need help

Need help automating Mural with Make?

A person reads every message.

FAQ

Mural and Make: common questions

01Is the Mural Make integration free?

Yes, you can use it on the Free plan. Mural is a standard app in Make, not an Enterprise one, so its modules are open on every plan. The Free plan still has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module per bundle.

02What do you need to connect Mural to Make?

A Mural account and a Make account. Make's documentation lists no specific prerequisite for Mural and no dedicated connection steps, so the generic flow applies: add a Mural module, click Create a connection, give it a name if you like, authorize Make on Mural's page or paste the key it gives you, then click Save. The connection is reused by all 22 Mural modules, so you only do this once per account.

03Do Mural triggers fire instantly in Make?

No. All 4 Mural triggers are scheduled, and none is instant. Make checks Mural on the scenario's schedule, every 15 minutes by default, and collects what was created since the last check. On the Free plan 15 minutes is the shortest interval; paid plans can go down to 1 minute. If you need to start a scenario the moment something happens, it has to come from another app that can call Make directly.

04What if a Mural module is missing in Make?

Use Make an API Call. It reaches any endpoint of Mural's API from your scenario with the connection you already set up, which covers what the 14 actions and 4 searches leave out. Keep in mind that Make's own documentation for Mural is limited, as it says there is not enough public information about the app, so test each call with Run once on a throwaway board before relying on it in a live scenario.

05Should you use Make or n8n for Mural?

It depends on the platform your team already runs. This page covers Make, where Mural has 22 modules and works on the Free plan as a standard app. Many apps also have a node on n8n, so check whether Mural does and which operations it offers before deciding. Compare the modules you actually need, the way each tool counts usage and where your other automations already live. Neither choice changes what Mural itself allows.

Add a Mural module

Name the connection

Authorize Make and save

Create the scenario

Link your account

Add the sticky note

Test with Run once

Schedule and switch on

Need help automating Mural with Make?