Shippit and Slack: Delivery Exception Escalation Template
This Spojit template checks Shippit tracking on a schedule, flags stalled or failed deliveries, and escalates each exception to a Slack channel so your team can act before customers complain.
What It Builds
A Schedule trigger fires on a fixed cron interval and a Shippit Connector node pulls recent order tracking. A Condition node keeps only shipments that are stalled, delayed, or marked failed, and a Loop walks each one so a Slack Connector node posts a clear exception alert with the order and tracking reference.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that runs every hour, fetches the latest tracking status for recent Shippit shipments, and finds any that are stalled, delayed, or marked as failed. For each exception, post a message to the #delivery-exceptions Slack channel with the order number, the tracking reference, the current status, and how long it has been stuck.Connectors Used
- Schedule trigger - runs the check on a cron interval in your timezone.
- Shippit - reads order and shipment tracking status.
- Slack - posts each delivery exception to a channel.
Customize It
Change the channel name (#delivery-exceptions), the schedule frequency, and the status values that count as an exception (for example add "lost" or "returned to sender"). You can also adjust the stalled threshold so only shipments stuck beyond a set number of hours escalate, all without writing a second prompt.
Tips
- Use the Slack Connector in Direct mode for a single fixed channel post, with no AI cost per run.
- Confirm your Shippit connection has read access to order tracking before the first scheduled run.
- Tune the cron interval so you catch exceptions promptly without re-alerting the same stuck shipment too often.