Automated SigmaNEST Cut List Production Handoff
Every few minutes, WebRun checks SigmaNEST for newly completed nests, saves the cut list and part quantities to that job's folder in Google Drive, and posts a Slack alert to the production channel so the floor knows the job is ready to load and run.
How do I automatically hand off a completed SigmaNEST nest to production?
WebRun checks SigmaNEST every few minutes for newly completed nests. As soon as one finishes, it files the cut list and part quantities into that job's Google Drive folder and posts a Slack alert naming the job, machine, and part count, so production can load and run the job without waiting on someone to walk over a printout.
- Completed nests reach the floor within minutes instead of a shift change
- Every cut list is filed automatically, so nothing is handed off on a loose printout
- Shift leads get a Slack alert naming exactly what just became ready to run
Built for sheet metal fabricators · nesting programmers · production supervisors · laser and plasma cutting shops
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.sigmanest.comin a real browser with your saved login - no setup, no API keys. -
1
SigmaNEST - detect newly completed nests
sigmanest.com
WebRun opens SigmaNEST to detect newly completed nests. - Check SigmaNEST for nests completed since the last check
- Capture the job number, part list, quantities, and program name for each
- Note the assigned machine and material for the nest
Done when Every newly completed nest is captured with its cut list details.
-
2
Google Drive - file the cut list in the job folder
drive.google.com
WebRun opens Google Drive to file the cut list in the job folder. - Open or create the job folder for each completed nest
- Save the cut list and part quantities into the folder
- Name the file with the job number and program version
Done when The cut list for every completed nest is filed in its job folder.
-
3
Slack - alert production the job is ready
slack.com
WebRun opens Slack to alert production the job is ready. - Post an alert to the production channel naming the job, machine, and part count
- Link to the job folder in Google Drive
- Tag the shift lead for the assigned machine
Done when Production has a Slack alert and a linked cut list for every completed nest.
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 release the job to the machine automatically?
No. WebRun files the cut list and alerts production that the job is ready. An operator still loads the program and starts the machine.
What if a nest gets revised after it was already handed off?
The next check picks up the revised nest as a new completion, files the updated cut list, and posts a fresh Slack alert so the floor knows a newer version exists.
Can office staff see what is running without walking the floor?
Yes. Every handoff lands in the shared Slack channel and the job's Google Drive folder, so anyone can see what just went to production and when.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.