Mural, without opening Mural.
Read-only workspaces, rooms, murals and the widgets on them.
In your channel
Ask Ray for something in Mural and it posts this card in the thread. One click, and the task you asked for carries on where it left off.
What Ray can and cannot do in Mural
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in Mural
- Get current user
- Get files for
- Get widgets
- Get room
- Get workspace
- Get workspaces
- List folders
- List open rooms
- List recent murals
- List recent templates
- List rooms
- List room murals
- List room users
- List tags
- List templates
- List workspace murals
- List workspace templates
- Search murals
- Search rooms
- Search templates
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Create sticky note
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
How Ray works with Mural
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Mural
One click, right where you asked. Ray posts a connect card, you authorise Mural with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Mural, and tell Dana it is being looked at.
Create sticky note
- Waiting on
- your approval
What does connecting Mural to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Mural and it can do the Mural part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own Mural account, so Ray can only reach what that person can already reach, and the history in Mural shows who actually asked.
Security and permissions
- You authorise Mural on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect Mural in a message, or uninstall Ray and every connection it held is revoked.
More design & whiteboards integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Mural.
Free to start, no credit card, and it asks before it acts.