Shippit and Slack: Warehouse Dispatch Email to Order Template

This Spojit template turns a plain dispatch email from your warehouse into a booked Shippit order, then replies with the tracking number.

What It Builds

A Mailhook trigger gives your workflow its own inbox address. When the warehouse sends a dispatch email there, a Transform step parses the order reference and delivery address from the message body, a Shippit connector node books the shipment, and the workflow replies to the sender with the booked tracking number while posting a confirmation to a Slack channel.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that triggers when an email is sent to a mailhook address. Parse the order reference and delivery address out of the email body, create a Shippit order for that shipment, then reply to the sender with the booked tracking number and post a confirmation with the order reference and tracking number to the #dispatch channel in Slack.

Connectors Used

  • Mailhook - the trigger; the workflow gets its own dispatch inbox address and runs on each email received.
  • Shippit - creates the order and returns the tracking number.
  • Slack - posts the booked confirmation to your dispatch channel.

Customize It

Change the Slack channel from #dispatch to wherever your fulfillment team watches, and adjust which fields are pulled from the email (for example add a weight or service level) so the Shippit order matches your account. You can also swap the Slack post for your own carrier or warehouse references without a second prompt.

Tips

  • Give the Mailhook address only to the warehouse so unrelated mail does not start runs; add a subject filter if needed.
  • Run the Shippit step as a Connector node in Direct mode for one exact, no-cost booking call once the fields are stable.
  • If dispatch emails vary in format, an Agent-mode Connector node with a Response Schema parses messy bodies into clean order fields.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.