Automated Locofy Design-to-Code Export Handoff
Every few minutes, WebRun checks Locofy for a design export that just finished converting to code, logs the project name, framework, and export time to a Google Sheet, and emails the dev lead a heads-up with the export link so it gets reviewed the same day.
How do I make sure a finished Locofy code export gets reviewed?
WebRun watches Locofy for a design export that finishes converting to code, logs the project, framework, and export time to a Google Sheet, and emails the dev lead a heads-up with the link. Design-to-code exports get reviewed the same day instead of sitting unnoticed after the designer moves on to the next screen.
- Finished exports reach the dev lead within minutes
- Every export is logged for reference in one sheet
- No design-to-code handoff gets lost between design and dev
Built for Product design teams · frontend developers · design system teams · agencies
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
locofy.aiin a real browser with your saved login - no setup, no API keys. -
1
Locofy - check for a finished export
WebRun opens Locofy to check for a finished export. - Open Locofy and check for a design export that just finished converting
- Note the project name, target framework, and export time
- Confirm the export link is ready to share
Done when Every newly finished export has its details captured.
-
2
Google Sheets - log the export details
WebRun opens Google Sheets to log the export details. - Open the design-to-code export tracker
- Add a row with the project, framework, and export time
- Mark it as awaiting dev review
Done when Every finished export has a row in the tracker.
-
3
Gmail - email the dev lead a heads-up
WebRun opens Gmail to email the dev lead a heads-up. - Draft and send the dev lead an email with the project name and export link
- Note the target framework so they know what to expect
- Send one email per finished export, not a batch
Done when The dev lead has been emailed about every finished export.
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
Will it merge or push the generated code?
No. WebRun only logs the export and emails the dev lead. Reviewing, merging, and pushing the code stays a manual step for your developers.
Does it touch the Figma design itself?
No. It only reads Locofy's finished export status. Your Figma file and design are never edited.
What if two exports finish close together?
Each one gets its own row in the tracker and its own email, so nothing gets merged together or missed.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.