Automated Air Cargo Load Status Digest
Every morning, WebRun opens Awery, reads booked cargo weight and volume versus available capacity for each active flight departing that day and the next, organises the data by flight number and ULD type, and posts a clean load status digest to your Slack ops channel.
How can I automatically get a daily air cargo load status digest for my flights?
WebRun opens Awery every morning and reads booked cargo weight and volume against available payload capacity for every flight departing in the next 48 hours. It groups the data by flight number and ULD type and posts a structured load status digest to your Slack ops channel, with high-load flights flagged automatically.
- Ops teams open Slack to a ready-made load status view every morning without logging into Awery
- Flights approaching full payload are flagged before the slot is wasted
- No manual capacity checking or report exporting required
Built for airline cargo operations teams · capacity managers · air freight ops managers · ground handling supervisors
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
awery.aeroin a real browser with your saved login - no setup, no API keys. -
1
Awery - read booked capacity vs available by flight and ULD
WebRun opens Awery to read booked capacity vs available by flight and ULD. - Open Awery and navigate to Cargo Reservation and flight planning views
- Filter for flights departing today and tomorrow
- For each flight, capture flight number, booked weight, booked volume, available capacity, and ULD type
- Note any flights approaching or exceeding 90% load factor
Done when Load data for every active flight in the next 48 hours is captured with capacity figures.
-
2
Slack - post daily load status digest to ops channel
WebRun opens Slack to post daily load status digest to ops channel. - Format the data as a clean digest grouped by departure date and flight number
- Flag flights at 90% or above load factor with a warning marker
- Post the digest to the #cargo-ops Slack channel
Done when The ops team has today's full load status digest in Slack, with high-load flights highlighted.
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
Can it cover flights beyond the next 48 hours?
Yes. The default lookout window is 48 hours, and you can extend it to 72 hours or 7 days in your WebRun settings.
Does it make any changes to bookings or capacity in Awery?
No. WebRun only reads flight and booking data from Awery and posts the digest to Slack. No bookings are created or modified.
What counts as a high load factor?
The default alert threshold is 90% of payload capacity. You can set a different threshold to match your revenue management policy.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.