SmartFreight and Slack: Emailed Manifest to Consignment Template

When a dispatch manifest lands at a Spojit mailhook address, this template reads the consignment rows from the attachment and imports each one into SmartFreight, posting to Slack if any import fails.

What It Builds

A Mailhook trigger gives the workflow its own inbound email address, so any manifest mailed to it starts a run. An Attachment node pulls the attached file's bytes, the rows are parsed, and a Loop imports each consignment into SmartFreight through a Connector node. A Condition catches any row that fails and a Slack Connector node alerts your team with the offending reference.

The Prompt

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

Build a workflow with a mailhook trigger. When a dispatch manifest email arrives, read the consignment rows from the attached file, then create a consignment in SmartFreight for each row using the recipient, address, weight, and reference. If any row fails to import, post a message to the #dispatch Slack channel with the failed reference and the error.

Connectors Used

Mailhook - the trigger; manifests sent to the workflow's mailhook address start each run.
SmartFreight - creates a consignment per manifest row.
Slack - posts an alert when a row fails to import.

Customize It

Change #dispatch to your own channel, adjust which columns map to the recipient, address, weight, and reference fields, or add a service-level field if your carrier accounts vary. You can also tweak the prompt to alert only when more than one row fails.

Tips

Use the SmartFreight Connector node in Direct mode for a clean one-to-one import; switch to Agent mode only if rows need interpreting.
The Attachment node is available only in Mailhook workflows, so keep the Mailhook trigger in place.
Confirm your SmartFreight connection has create-consignment permission before going live.