ShipStation and Slack: Stuck-In-Transit Watchdog Template
A scheduled Spojit workflow that scans recent ShipStation shipments and flags any parcel stalled in transit to a Slack channel for follow-up.
What It Builds
A Schedule trigger runs the workflow on a cron you set. A ShipStation Connector node pulls recent shipments, a Condition node keeps only those whose tracking status has not advanced past your threshold, and a Slack Connector node posts each stalled tracking number to a channel so your team can chase the carrier.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that runs every morning at 8am, pulls recent ShipStation shipments, finds any parcel whose tracking has not updated or moved past "in transit" for more than 3 days, and posts each stalled tracking number, order number, carrier, and last-update date to the #shipping Slack channel.Connectors Used
- Schedule trigger - runs the watchdog on a recurring cron (set your own time and IANA timezone).
- ShipStation - lists recent shipments and their tracking status.
- Slack - posts each flagged tracking number to a channel for follow-up.
Customize It
Change the stall window (3 days), the run time, the Slack channel (#shipping), and the fields included in each alert. You can narrow the scan to a single carrier or store, or post a daily summary instead of one message per parcel by adjusting the prompt before you build.
Tips
- Use a ShipStation Connector node in Direct mode for the exact list call, no AI cost; switch to Agent mode if you want Miraxa to reason over edge-case statuses.
- Give the Slack connection access to the target channel, and consider tagging an on-shift owner so stalled parcels get picked up fast.
- Start with a wider window while you tune thresholds, then tighten it to cut noise.