Miro, without opening Miro.
Read-only boards, the items on them and who is collaborating.
In your channel
Ask Ray for something in Miro 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 Miro
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 Miro
- Get all groups
- Get boards2
- Get board items
- Get board members
- Get connector
- Get connectors
- Get group by id
- Get items by group id
- Get items within frame
- Get item tags
- Get mindmap nodes experimental
- Get specific board
- Get specific board member
- Get specific item
- Get tag
- List board tags
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Tag a Miro item
- Add an app card to a Miro board
- Create 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
- Add a frame to a Miro board
- Create group
- Add an image to a Miro board
- Create items in bulk
- Add a mind-map node to a Miro board
- Add a shape to a Miro board
- Add a sticky note to a Miro board
- Create a Miro tag
- Add text to a Miro board
- Update a Miro app card
- Update a Miro board
- Update a Miro card
- Update a Miro connector
- Update a Miro document
- Update a Miro embed
- Update a Miro frame
- Update a Miro group
- Update a Miro image
- Move a Miro item
- Update a Miro shape
- Update a Miro sticky note
- Update a Miro tag
- Update Miro text
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, 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 app card item
- Delete card item
- Delete connector
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
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 Miro, and tell Dana it is being looked at.
Tag a Miro item
- Waiting on
- your approval
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, 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 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.
- 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 Miro 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 Miro.
Free to start, no credit card, and it asks before it acts.