SmartFreight and Slack: Consignment Tracking Alert Template
A ready-to-build Spojit template that watches your open SmartFreight consignments on a schedule and posts every status change straight to a Slack channel.
What It Builds
A Schedule trigger runs the workflow at a regular interval. A SmartFreight Connector node in Direct mode pulls the latest tracking events for your open consignments, a Condition node keeps only those whose status has changed, and a Slack Connector node posts each change to your chosen channel. The result is a live feed of in-transit, delivered, and exception updates without anyone refreshing a carrier portal.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that runs every 30 minutes, pulls SmartFreight tracking events for all open consignments, and for each consignment whose status has changed since the last run, posts a message to the #shipping Slack channel with the consignment number, the new status (in transit, delivered, or exception), the destination, and the latest tracking timestamp.Connectors Used
- Schedule - the trigger that runs the check at your chosen interval.
- SmartFreight - fetches tracking events for open consignments.
- Slack - posts each status change to a channel.
Customize It
Change every 30 minutes to fit your volume, swap #shipping for the right channel, and edit the status list so you only alert on exception if delivered updates are too noisy. You can also add fields like the carrier name or estimated delivery date to the Slack message.
Tips
- Use the SmartFreight Connector node in Direct mode here for a precise, no-AI tracking lookup; reserve Agent mode for cases where the next step is genuinely open-ended.
- Make sure your Slack connection has access to the target channel before the first run.
- Keep the schedule sensible: very frequent runs add little value when carriers update events in batches.