Automated Figma Dev Handoff Queue
Every morning, WebRun opens your Figma projects, finds the frames and sections newly marked ready for development, posts each one to Microsoft Teams with its file link and the components it uses, and texts the engineering lead through Twilio so work never waits for a designer to remember.
How do I get finished Figma designs to engineering without chasing?
WebRun scans your Figma projects every morning for frames newly marked ready for development. It posts each one to Microsoft Teams with a direct file link, the designer, and a warning if comments are still open, then texts the engineering lead through Twilio, so handoff happens the day a design is finished.
- Finished designs reach engineering the morning they are marked ready
- Frames with unresolved comments are flagged before anyone builds them
- Designs unpicked after three days get chased automatically
Built for engineering leads · product designers · design managers · product 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
www.figma.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Figma - find newly ready frames
figma.com
WebRun opens Figma to find newly ready frames. - Open each project in your Figma team and list the files changed since yesterday
- Find frames and sections newly marked ready for development
- Capture the file, the page, the frame name, and who marked it
- Note the components used and whether the frame is still carrying open comments
Done when Every frame newly marked ready is listed with its file and owner.
-
2
Microsoft Teams - post the handoff queue
microsoft.com
WebRun opens Microsoft Teams to post the handoff queue. - Post the handoff queue to your engineering channel, one line per frame
- Give each line a direct Figma link, the designer's name, and the date it was marked ready
- Flag frames that still have unresolved comments so nobody builds against a moving target
- Repeat frames that were marked ready more than three days ago and still have no engineer on them
Done when The handoff queue with links is in Teams.
-
3
Twilio - text the engineering lead
twilio.com
WebRun opens Twilio to text the engineering lead. - Text the engineering lead's own number a one-line count of frames ready today
- Name the oldest frame still waiting for someone to pick it up
- Send only to internal team numbers you configured. WebRun never texts anyone outside your team
- Leave assigning the work to the lead. WebRun never edits a Figma file or changes a status
Done when The engineering lead knows how many designs are ready and which is oldest.
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 edit Figma files or change a frame's status?
No. WebRun reads your files and reports what changed. Marking a frame ready, resolving a comment, or editing a design stays entirely with the designer who owns it.
Who receives the text message?
Only the internal team numbers you configure when connecting Twilio, normally the engineering lead. WebRun never texts a client, a stakeholder, or anyone outside your team.
What stops the same frame being posted every day?
A frame is posted the day it is marked ready, then only repeated if it is still unpicked after three days, with its waiting time shown so it reads as a nudge rather than noise.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.