Automated Penpot Design Handoff to Developers
Each time a Penpot component is marked ready for development, WebRun creates a Trello handoff card with the component's link and specs, then posts it to the dev team's Microsoft Teams channel with the assigned developer tagged.
How do I hand off finished Penpot components to developers?
WebRun watches your Penpot file for components marked ready for development. Each time one is flagged, it creates a Trello handoff card with the component's link and specs, then posts it to the dev team's Microsoft Teams channel with the assigned developer tagged, so design work moves into the backlog the same day it's finished.
- Every ready component gets handed off without a manual message
- Developers know exactly what's ready to build and by whom
- Design and development stay in sync without a status meeting
Built for Product design teams · frontend developers · design systems teams · startups
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
design.penpot.appin a real browser with your saved login - no setup, no API keys. -
1
Penpot - check components marked ready for dev
- Open the file and check for components marked ready for development
- Note the component name, specs, and which screen it belongs to
Done when Every component marked ready is listed with its specs.
-
2
Trello - create a handoff card
trello.com
WebRun creates a handoff card in Trello. - Create a handoff card on the development board
- Attach the component link and specs
- Set it to the dev backlog
Done when A handoff card exists for every ready component.
-
3
Microsoft Teams - notify the dev team
microsoft.com
WebRun notifies the dev team in Microsoft Teams. - Post the handoff card link to the dev channel
- Tag the assigned developer
- Note which screen or feature it's part of
Done when The dev team knows a component is ready to build.
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 write or generate the code?
No. WebRun only routes the design for handoff. Writing the actual code stays with the developer.
How does it know a component is ready?
It reads the ready-for-dev status or tag the designer sets on the component in Penpot, so nothing gets handed off before a human marks it done.
Can it route different components to different developers?
Yes. Tell WebRun which developer owns which screen or feature, and it tags the right person on each handoff card.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.