Weekday Slack digest of stuck AfterShip shipments

Every weekday at 8am, pull my AfterShip trackings that are still in transit or in an exception state using the List Trackings action, then reason about which shipments are genuinely stuck versus normal in-flight ones.

A shipment counts as stuck if any of these apply: it is past its estimated delivery date, its last checkpoint update was more than 48 hours ago, or it is sitting in an exception status like "Attempt Fail" or "Available for Pickup" for longer than it should be. Skip normal in-transit shipments so the Slack channel does not get spammed.

For each shipment flagged as stuck, use Get Tracking by ID to fetch the full checkpoint history so the digest has real context about where and when things went wrong.

Then, using Slack's Send a Message action, post a single prioritized digest to my Slack channel. Group the flagged shipments by severity (for example, critical, warning, watch), and for each one include the courier, the tracking number, the last known checkpoint with its timestamp, the estimated delivery date, the AfterShip tracking URL, and a concrete suggested next step such as contact the carrier, notify the customer, or escalate to ops. Use Slack's mrkdwn formatting so the message is readable at a glance.

If there is nothing stuck on a given day, skip posting entirely rather than sending an empty message. Use cron for the trigger since AfterShip does not have a polling trigger on this platform.