Automated Zeplin Developer Handoff Tracking
When a new screen is published to Zeplin, WebRun checks which project and sprint it belongs to, creates or updates a developer handoff card in Trello with the spec and asset links, and posts to Microsoft Teams that a new handoff is ready, so developers find out the same day a design is finalized instead of during standup.
How do I make sure developers know when a new Zeplin screen is ready?
WebRun watches Zeplin for newly published screens, creates or updates a developer handoff card in Trello with the spec and asset links, and posts to Microsoft Teams that a new handoff is ready. Developers find out the same day a design is finalized, so handoffs stop depending on someone remembering to mention it.
- Developers see new handoffs the same day, not at the next standup
- Every screen gets a tracked Trello card instead of a forgotten link
- The design to development gap closes without a manual check in
Built for product design teams · software agencies · engineering managers · design systems teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.zeplin.io/loginin a real browser with your saved login - no setup, no API keys. -
1
Zeplin - find newly published screens
- Open Zeplin and check for screens published since the last run
- Note the project, screen name, and spec link for each
- Confirm the screen has assets and style notes attached
Done when Every screen published since the last run has been found.
-
2
Trello - create the handoff card
trello.com
WebRun opens Trello to create the handoff card. - Create or update the developer handoff card on the Trello board for that project
- Attach the Zeplin spec link and note what changed
- Move the card into the ready for development column
Done when A Trello handoff card exists for each with the spec link attached.
-
3
Microsoft Teams - post that a handoff is ready
microsoft.com
WebRun opens Microsoft Teams to post that a handoff is ready. - Post to the engineering channel in Microsoft Teams that a new handoff is ready
- Include the screen name and a link to the Trello card
- Tag the developer assigned to that project if one is set
Done when The team has been notified in Microsoft Teams.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it change or approve the design?
No. WebRun only tracks that a screen was published and creates the handoff card. Design review and approval stay a manual step in Zeplin.
What if a card for that screen already exists?
WebRun updates the existing card with what changed instead of creating a duplicate, so the Trello board stays clean.
Will it notify the right developer?
It tags whichever developer is already assigned to that project on the Trello card. If nobody is assigned, the card still gets created and posted for the team to claim.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.