Zeplin, without opening Zeplin.
The handoff details a developer needs, and the annotation updated in place.
- 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 Zeplin details, and Ray takes it from there.
@Ray what does the spec say for the empty state on that screen?
@Ray which screens changed in the checkout project this week?
@Ray what is the brand color for the primary button?
@Ray note on that screen that the copy is final.
What Ray can and cannot do in Zeplin
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
14 reads wired, 1 action that wait for a human.
Runs on its own
What Ray reads in Zeplin
- Screens, their versions, sections, and components
- Developer annotations on a screen
- Project and styleguide colors and text styles
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Update an annotation on a screen
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 an annotation
- Change styleguide or project colors and text styles
- Invite someone to a project
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Zeplin actions Ray can take, each one stopping in the thread with the real content before it happens.
- Screen annotations update
Screen annotations update
Showing the exact change before it happens, down to the amount.
How Ray works with Zeplin
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Zeplin
One click, right where you asked. Ray posts a connect card, you authorise Zeplin 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 Zeplin, and tell Dana it is being looked at.
Screen annotations update
- Waiting on
- your approval
Ray uses Zeplin together with the rest of your tools.
One ask can read Zeplin, 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 Zeplin to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Zeplin and it can do the Zeplin 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 Zeplin account, so Ray can only reach what that person can already reach, and the history in Zeplin shows who actually asked.
Security and permissions
- You authorise Zeplin 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 Zeplin in a message, or uninstall Ray and every connection it held is revoked.
Zeplin and Ray, answered
The questions teams ask before they connect Zeplin. 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 Zeplin.
Free to start, no credit card, and it asks before it acts.