All templates

Automated Plant Livestock ETA Updates

Every hour, WebRun opens M2X, reads each inbound load's live ETA, compares it to the plant's booked processing slot, posts any load running early or late to Slack, and drafts an ETA update email to the plant contact for your team to review and send.

Runs on WebRun · Strict Lockdown policy
Every hour WebRunorchestrates each step
1 M2X compare live ETA to the booked slot
2 Slack flag arrivals off their slot
3 Gmail draft an ETA update to the plant
In short

How do I automatically notify a plant when a livestock load will miss its slot?

Every hour WebRun opens M2X, reads each inbound load's live ETA, and compares it to the plant's booked processing slot. It posts loads running off their slot to Slack and drafts an ETA update email to each affected plant in Gmail for your team to review and send, so plants plan around real arrival times.

  • Plants learn about a late load while there is still time to adjust
  • Dispatch sees the exact minutes off slot, ranked worst first
  • On-time loads never generate a needless email to the plant

Built for livestock haulers · cattle transporters · processing plant schedulers · feedlot logistics teams

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 www.m2xgroup.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    M2X - compare live ETA to the booked slot
    m2xgroup.com
    WebRun in M2X: compare live ETA to the booked slot
    WebRun opens M2X to compare live ETA to the booked slot.
    • Open M2X and list loads inbound to a processing plant today
    • Read each load's live ETA and the plant's booked slot time
    • Work out which loads will arrive outside their booked window
    • Note the plant, load, head count, and the size of the gap

    Done when Every inbound load has its live ETA compared to its booked processing slot.

  3. 2
    Slack - flag arrivals off their slot
    slack.com
    WebRun in Slack: flag arrivals off their slot
    WebRun opens Slack to flag arrivals off their slot.
    • Post the loads running outside their slot to the dispatch channel
    • List the plant, truck, head, and minutes early or late for each
    • Put the largest gaps first so dispatch can act on them

    Done when Dispatch has a Slack list of every load arriving off its booked slot.

  4. 3
    Gmail - draft an ETA update to the plant
    gmail.com
    WebRun in Gmail: draft an ETA update to the plant
    WebRun opens Gmail to draft an ETA update to the plant.
    • Draft a short ETA update email to the plant contact for each affected load
    • State the new expected arrival time and the head count on the load
    • Leave every email unsent for your team to review and send. Do not email the plant automatically

    Done when A Gmail draft exists for each plant that needs an ETA update, awaiting your team's review.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.m2xgroup.com
ScheduleRuns automatically on this cadence
Every hour
DeliveryHow each run's result reaches you
Slot alerts · Slack
OutputWhat each run produces - A Slack list of loads arriving off their booked slot, plus a drafted ETA update email per affected plant for your team to send.
Alert + drafts
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

Will it email the processing plant without me?

No. Each plant ETA update is drafted in Gmail and left unsent for your team to review and send. The internal Slack alert posts automatically, but no message reaches a plant customer without human approval.

How does it know a load will miss its slot?

It compares each load's live ETA in M2X to the plant's booked processing slot every hour and flags any load projected to arrive outside its window, with the exact minutes early or late.

What if a load is running exactly on time?

Loads projected to arrive inside their booked slot are left off the alert and no email is drafted, so your team and the plant are only contacted about arrivals that actually need attention.

Put this on autopilot.

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