Miro, without opening Miro.
Build the board out from the conversation, item by item.
- Free to start
- No card
- Nothing irreversible without your yes
- 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 Miro details, and Ray takes it from there.
@Ray put those five ideas on the retro board as stickies.
@Ray make a board for the Q4 planning session.
@Ray what is on the roadmap board right now?
@Ray tag everything in the parked frame so we can find it later.
What Ray can and cannot do in Miro
Reading is free, because reading changes nothing. Everyday changes Ray just makes, and anything that can't be taken back waits for your yes. The rest is not on Ray’s list.
16 reads wired, 24 actions Ray does at once, and 6 actions that wait for your yes.
Runs on its own
What Ray reads in Miro
- Boards, the items on them, and how they connect
- Board members, groups, tags, and frames
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Just does it
Ray does these at once
- Add a sticky note, card, shape, text, image, or document
- Add an embed or an app card
- Connect or group items
- Create or update a tag, and tag an item
- Update a board
- Update a sticky note, card, shape, text, image, or document
- Update a frame, an embed, an app card, or a connector
Anything Ray can put back comes with an Undo button on its reply. In a schedule, a watch or a chase that has read outside content with nobody present, these wait for a yes too.
Asks first, every time
Always waits for your yes
- Create a board
- Add a frame or a mind-map node
- Create items in bulk
- Change which items are in a group
- Move an item on a board
Ray posts a card showing exactly what it is about to do. Nothing happens until someone approves, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Delete anything on a board, including tags and groups
- Take a tag off an item
- Change a board member
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Miro actions that stop in the thread with the real content before they happen.
- Create a Miro board
- Add a frame to a Miro board
- Create items in bulk
- Add a mind-map node to a Miro board
- Update a Miro group
- Move a Miro item
Ray does these at once
- Tag a Miro item
- Add an app card to a Miro board
- Add a card to a Miro board
- Create connector
- Add a document to a Miro board
- Embed something on a Miro board
- Create group
- Add an image to a Miro board
- Add a shape to a Miro board
- Add a sticky note to a Miro board
Everyday work. Anything Ray can put back comes with an Undo button on its reply.
Create a Miro board
Showing Name, Description, Team id and Policy, each carrying the exact content that will land.
How Ray works with Miro
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Miro
One click, right where you asked. Ray posts a connect card, you authorise Miro 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
It lands, with an Undo
Reading runs on its own. Everyday changes land at once with an Undo, and anything that sends, spends or can't be taken back waits for your yes with the exact content in front of you.
Megan
@Ray the checkout bug is back. Take a look in Miro, and tell Dana it is being looked at.
Tag a Miro item
- Done
- just now
Ray uses Miro together with the rest of your tools.
One ask can read Miro, 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 Miro to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Miro and it can do the Miro part of a request without anyone leaving the conversation: read what it needs and make the change, asking first before anything that can’t be taken back.
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 Miro account, so Ray can only reach what that person can already reach, and the history in Miro shows who actually asked.
Security and permissions
- You authorise Miro on its own login screen. Your password never passes through Ray.
- What waits for a yes is decided in the execution path, not by a prompt. No setting lets an irreversible action through without one.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect Miro in a message, or uninstall Ray and every connection it held is revoked.
Miro and Ray, answered
The questions teams ask before they connect Miro. 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 Miro.
Free to start, no credit card, and nothing irreversible happens without your yes.
By adding Ray, you accept the Terms and Privacy Policy.