# Ray and Zeplin

> The handoff details a developer needs, and the annotation updated in place.

Source: https://heyray.io/integrations/zeplin

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. 14 reads run without asking. 1 action waits for a human approval.

## What Ray reads in Zeplin

Reading changes nothing, so Ray never stops to ask whether it may look something up.

- Screens, their versions, sections, and components
- Developer annotations on a screen
- Project and styleguide colors and text styles

## What waits for your approval

Every one of these posts an approval card in the thread showing exactly what is about to happen. Nothing runs until someone clicks approve, and no setting turns that off.

- Update an annotation on a screen

## 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

## Ask it like this

- "@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."

## Connecting Zeplin

Every person on the team connects their own Zeplin account on Zeplin's own login screen, so Ray can only reach what that person can already reach, and the history in Zeplin shows who actually asked. Passwords never pass through Ray. Disconnecting Zeplin or uninstalling Ray revokes the connection.

## More

- This page for people: https://heyray.io/integrations/zeplin
- Every integration: https://heyray.io/integrations.md
- Install Ray: https://heyray.io/install.md
- Pricing: https://heyray.io/pricing.md