Figma, without opening Figma.
Read-only design files, comments, version history and the design system a developer asks about.
In your channel
Ask Ray for something in Figma 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 Figma
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 Figma
- Discover resources
- Extract design tokens
- Extract prototype interactions
- Get comments in a file
- Get component2
- Get component set
- Get current user
- Get dev resources
- Get files in a project
- Get file components
- Get file component sets
- Get file json
- Get file metadata
- Get file nodes
- Get file styles
- Get library analytics component usage data
- Get library analytics style usage data
- Get library analytics variable usage data
- Get local variables
- Get projects in a team
- Get published variables
- Get reactions for a comment
- Get style
- Get team components
- Get team component sets
- Get team styles
- Get versions of a file
- Render images of file nodes
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Comment on a Figma file
- Create dev resources
- Update dev resources
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 a comment
- Delete a reaction
- Delete a webhook
How Ray works with Figma
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Figma
One click, right where you asked. Ray posts a connect card, you authorise Figma 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 Figma, and tell Dana it is being looked at.
Comment on a Figma file
- Waiting on
- your approval
What does connecting Figma to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Figma and it can do the Figma 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 Figma account, so Ray can only reach what that person can already reach, and the history in Figma shows who actually asked.
Security and permissions
- You authorise Figma 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 Figma 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 Figma.
Free to start, no credit card, and it asks before it acts.