Digest orders running behind their ship date
Every morning, WebRun opens AMFG, finds orders whose current progress puts them past their scheduled ship date, records each on a Google Sheet with the days late, and posts you a short Slack list so you can pull the slipping jobs forward.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I spot 3D printing orders that will miss their ship date?
WebRun catches slipping orders before they blow a deadline. Each morning it opens AMFG, compares every order's production stage against its ship date, logs the ones running late to a Google Sheet, and posts a Slack list ranked by days behind, so your team can pull at-risk jobs forward in time.
- Slipping orders surface every morning, not at ship time
- A running sheet shows which jobs go late and how often
- The team reschedules at-risk work before deadlines are missed
Built for 3D printing bureaus · production managers · additive manufacturing shops · operations 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
app.amfg.aiin a real browser with your saved login - no setup, no API keys. -
1
AMFG - find orders past their ship date
WebRun opens AMFG to find orders past their ship date. - Open AMFG and review orders with an upcoming or passed ship date
- Compare each order's production stage against its scheduled ship date
- Capture the order, customer, ship date, and days behind for each slipping job
Done when Every order behind its scheduled ship date is listed with the delay.
-
2
Google Sheets - log the late orders
WebRun opens Google Sheets to log the late orders. - Open the tracking sheet and append a dated row for each late order
- Record the customer, ship date, current stage, and days behind
- Update any order already listed so the sheet reflects today's status
Done when The sheet holds today's late orders with their delays.
-
3
Slack - post the at-risk list
WebRun opens Slack to post the at-risk list. - Post a short list of the late orders to your operations channel
- Put the most overdue jobs first with their days behind
- Leave it for the team to reschedule. Never message the customer directly
Done when The team has today's at-risk order list in Slack.
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 tell customers their order is late?
No. WebRun keeps the at-risk list internal, on your Google Sheet and in Slack. It never contacts a customer about a delay. Your team decides who to update and how.
How does it know an order is behind?
It compares each order's current production stage in AMFG against its scheduled ship date. Any order whose progress puts it past that date is listed, with the number of days it is behind.
Is it safe to run every morning unattended?
Yes. It only reads order status, writes to your own tracking sheet, and posts an internal Slack digest. Nothing is sent externally and no order is changed, so it is safe to run on a schedule.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.