Automated Magaya Container Rollover Alerts
Every morning, WebRun opens Magaya, scans ocean shipments for any container that has been rolled to a later vessel or whose ETD has shifted by 24 hours or more since the last run, and posts a consolidated rollover alert to your Slack operations channel so your team can act before clients call.
How do I get automatic alerts when containers roll to a later vessel in Magaya?
WebRun scans Magaya every morning for ocean shipments where the vessel or ETD has changed since the previous day. It posts a consolidated rollover alert to your Slack ops channel within minutes, listing every affected shipment with the original and new vessel details. Your team can reach out to clients and rebook before the news reaches them another way.
- Rollovers detected within 24 hours, before clients discover them independently
- Ops team sees a single consolidated Slack alert instead of scanning every shipment record
- Time-sensitive shipments flagged as priority items in the alert
Built for freight forwarders · ocean freight operations teams · logistics account managers · import-export coordinators
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.magaya.comin a real browser with your saved login - no setup, no API keys. -
1
Magaya - detect vessel changes and ETD shifts on open shipments
WebRun opens Magaya to detect vessel changes and ETD shifts on open shipments. - Open Magaya and navigate to active ocean shipments
- Compare the current ETD and vessel name against the values recorded on the previous run
- Flag any shipment where the vessel has changed or the ETD has moved by 24 hours or more
- Capture the shipment reference, client name, original vessel and ETD, and new vessel and ETD for each flagged shipment
Done when Every container rollover or significant ETD change is identified with its before-and-after details.
-
2
Slack - post consolidated rollover alert to ops channel
WebRun opens Slack to post consolidated rollover alert to ops channel. - Post a rollover alert to the Slack operations channel listing every affected shipment
- Include the shipment reference, client name, original and new vessel, and the number of days delay for each
- Flag any rollover affecting a time-sensitive shipment as a priority item
Done when Your operations team has the complete rollover 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
Will it notify clients about the rollover automatically?
No. Client notifications require human judgment about tone, compensation, and alternatives. WebRun posts the alert to your team in Slack so they can decide how and when to inform each client.
How does it know a container has rolled?
It compares the vessel name and ETD on each Magaya shipment record against the values from the previous run. Any change of 24 hours or more is treated as a rollover.
What if multiple containers on the same booking roll at once?
Each container is reported individually in the Slack alert, grouped under the same booking reference so your team can see the full scope of the rollover at a glance.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.