Mural, without opening Mural.
What is on the murals, with a sticky added when the idea lands.
- Free to start
- No card
- Every write waits for you
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Mural details, and Ray takes it from there.
@Ray add that as a sticky on the roadmap mural.
@Ray what is on the retro mural from last sprint?
@Ray find the mural we used for the pricing workshop.
@Ray put each of those risks on the planning mural.
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.
20 reads wired, 1 action that wait for a human.
Runs on its own
What Ray reads in Mural
- Workspaces, rooms, and the murals in them
- The widgets on a mural, its tags, and templates
- Search across murals, rooms, and 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 a 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.
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Mural actions Ray can take, each one stopping in the thread with the real content before it happens.
- Create sticky note
Create sticky note
Showing the exact change before it happens, down to the amount.
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
Ray uses Mural together with the rest of your tools.
One ask can read Mural, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
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.
Mural and Ray, answered
The questions teams ask before they connect Mural. Every answer is how this integration is built rather than a promise about it.
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.