All templates

Cabinet Vision Automated CNC Cut List Handoff

As soon as a job in Cabinet Vision is marked released to production, WebRun pulls the cut list and the nested CNC program, saves both to the shop's CNC queue folder in Google Drive, and posts the floor lead a Slack note with the job number, sheet count, and where to find the files.

Runs on WebRun · Strict Lockdown policy
Runs within minutes of a job being marked released to production WebRunorchestrates each step
1 Cabinet Vision generate the cut list and CNC program
2 Google Drive file the cut files in the CNC queue
3 Slack tell the floor lead it's ready to run
In short

How do I get a finished cut list to the CNC machine without retyping it?

WebRun watches Cabinet Vision for jobs marked released to production, pulls the cut list and nested CNC program, and files both in a job numbered folder in the shop's Google Drive CNC queue. It then posts the floor lead a Slack note with the sheet count and a link, so the next job is staged and ready to run within minutes.

  • The floor lead knows the moment a job is ready to run
  • Cut list and CNC files are never lost between design and the saw
  • Mismatched part counts get flagged before they reach the machine

Built for cabinet shops · millwork manufacturers · CNC shop floors · closet and cabinet fabricators

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens cabinetvision.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Cabinet Vision - generate the cut list and CNC program
    cabinetvision.com
    WebRun in Cabinet Vision: generate the cut list and CNC program
    WebRun opens Cabinet Vision to generate the cut list and CNC program.
    • Open Cabinet Vision and list jobs newly marked released to production
    • Pull the cut list, the sheet goods nesting, and the CNC program for each
    • Confirm the part count on the cut list matches the nested sheets

    Done when Every newly released job has a matching cut list and CNC program.

  3. 2
    Google Drive - file the cut files in the CNC queue
    drive.google.com
    WebRun in Google Drive: file the cut files in the CNC queue
    WebRun opens Google Drive to file the cut files in the CNC queue.
    • Create a job folder in the shop's CNC queue if one doesn't exist
    • Save the cut list PDF and the CNC program files to that folder
    • Name each file with the job number so the operator can find it fast

    Done when The cut list and CNC files are filed and named in the queue folder.

  4. 3
    Slack - tell the floor lead it's ready to run
    slack.com
    WebRun in Slack: tell the floor lead it's ready to run
    WebRun opens Slack to tell the floor lead it's ready to run.
    • Post the job number, sheet count, and material to the shop floor channel
    • Link straight to the Drive folder
    • Flag any job where the part count did not match the nesting for a human to check

    Done when The floor lead has a link to run the job and any mismatch is flagged.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
cabinetvision.com
ScheduleRuns automatically on this cadence
Runs within minutes of a job being marked released to production
DeliveryHow each run's result reaches you
Run notice · Slack
OutputWhat each run produces - A shop floor note with the job number, sheet count, material, and a link to the filed cut list and CNC program.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does it load the file into the CNC machine itself?

No. WebRun only files the cut list and CNC program in Drive and tells the floor lead it's ready. An operator still loads and runs the machine.

What if the cut list and nesting don't match?

It flags the mismatch in Slack instead of filing the job, so a bad nest never reaches the saw or router without a human check.

Where do the files end up?

In a job numbered folder in the shop's CNC queue on Google Drive, alongside the cut list PDF, so anyone can find the right files fast.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.