Mailhook and Slack: Supplier Shipment Delay Alert Template
When a supplier emails about a shipment delay, this Spojit template extracts the affected purchase order and new ETA, then posts a prioritized alert to your procurement Slack channel.
What It Builds
A Mailhook trigger gives the workflow its own inbound email address, so any delay notice a supplier sends starts a run. An Agent-mode Connector node reads the message body and pulls out the affected PO number, the original and revised ETA, and how urgent the slip is. A Slack connector node then posts a formatted alert to your procurement channel so the team can react before it impacts the line.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that triggers when a supplier emails our Mailhook address about a shipment delay. Read the email, extract the affected purchase order number, the new ETA, and how serious the delay is, then post a prioritized alert to the #procurement Slack channel with the PO number, supplier name, new ETA, and a one-line summary.Connectors Used
- Mailhook - the trigger; the supplier's delay email starts each run.
- Agent-mode Connector - reads the email and extracts the PO, ETA, and priority.
- Slack - posts the alert to your procurement channel.
Customize It
Change #procurement to your own channel, adjust which fields the alert includes (carrier, line items, or the matching NetSuite sales order), or have Miraxa look up the PO in NetSuite to attach order value so the team can triage by impact.
Tips
- Give the Slack connection access to the target channel before the first run.
- Add a Response Schema to the Agent-mode Connector node so PO and ETA come back as clean, structured fields every time.
- Forward or filter only genuine delay notices to the Mailhook address to keep alerts signal-rich.