Figma, without opening Figma.
What the design says, answered for the developer asking.
- 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 Figma details, and Ray takes it from there.
@Ray what padding does the button use in the design system?
@Ray which components in the library is nobody using?
@Ray leave a comment on the checkout frame asking about the empty state.
@Ray what changed in that file since the last version?
What Ray can and cannot do in Figma
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.
28 reads wired, 1 action Ray does at once, and 2 actions that wait for your yes.
Runs on its own
What Ray reads in Figma
- Files, their nodes, components, styles, and variables
- Comments, reactions, and version history
- Design tokens, prototype interactions, and rendered images of any node
- Library analytics on what is actually being used
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Just does it
Ray does these at once
- Comment on a file
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 or update dev resources on a node
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 a comment or a reaction
- Create, change, or delete variables
- Create or delete a webhook
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Figma actions that stop in the thread with the real content before they happen.
- Create dev resources
- Update dev resources
Ray does these at once
- Comment on a Figma file
Everyday work. Anything Ray can put back comes with an Undo button on its reply.
Create dev resources
Showing the exact change before it happens, down to the amount.
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
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 Figma, and tell Dana it is being looked at.
Comment on a Figma file
- Done
- just now
Ray uses Figma together with the rest of your tools.
One ask can read Figma, 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 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 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 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.
- 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 Figma in a message, or uninstall Ray and every connection it held is revoked.
Figma and Ray, answered
The questions teams ask before they connect Figma. 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 Figma.
Free to start, no credit card, and nothing irreversible happens without your yes.
By adding Ray, you accept the Terms and Privacy Policy.