EFI Automatic Spec Revision Alerts
Every hour during production, WebRun opens EFI, reviews specs revised since the last check, cross-references each against open jobs still on the old version, logs the change to a Google Sheet, and posts a Slack alert naming the job and what changed before the next run.
How do I stop a press from running an outdated packaging spec?
WebRun watches EFI every hour for spec revisions, dieline, board grade, ink, or coating changes, that touch a job still open or in production. It logs each change to a Google Sheet and posts a Slack alert naming the job and press so the crew confirms the current spec before running, catching an outdated spec before it becomes a reprint.
- An outdated spec is caught before it reaches the press, not after
- Every revision is logged with the exact field that changed
- Reprints from running the wrong dieline or board grade drop
Built for corrugated box converters · folding carton plants · label converters · packaging quality and production 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.efi.comin a real browser with your saved login - no setup, no API keys. -
1
EFI - find specs revised since last check
efi.com
WebRun opens EFI to find specs revised since last check. - Open EFI's spec and artwork records and review revisions since the last check
- Cross-reference each revised spec against jobs still open or in production
- Capture the customer, job, the field changed, dieline, board grade, ink, or coating, and the revision date
Done when Every spec revision touching an open job is listed with what changed.
-
2
Google Sheets - log the revision
google.com
WebRun opens Google Sheets to log the revision. - Open the revision log and append a row per change
- Record the customer, job, field changed, old value, new value, and revision date
- Mark the row as caught so it isn't logged twice
Done when The revision log holds a row for every change caught this run.
-
3
Slack - alert production to confirm the spec
slack.com
WebRun opens Slack to alert production to confirm the spec. - Post an alert to the production channel naming the job, press, and what changed
- Tell the crew to confirm the current spec in EFI before running the job
- Flag it clearly so it isn't missed in a busy channel
Done when Production has an alert for every open job on a revised spec before the next run.
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 update the job to the new spec automatically?
No. WebRun only detects a revision and alerts production. A person always confirms the current spec and updates the job traveler in EFI directly.
How does it catch a revision?
It compares each spec's revision timestamp in EFI against the last check, and flags anything changed that still has an open job attached to it.
What if the job already finished before the spec changed?
Only jobs still open or in production are flagged. A completed job tied to an older spec version is skipped since it can't be affected.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.