Contents6
After an order, the customer wants to know one thing: when it will arrive. If they do not know, they call, or they write to support. These requests are not problems to solve, they are information to give, and yet they take up a good share of customer service time in many companies that ship goods.
An n8n workflow gives this information before anyone asks. This article is part of the n8n workflows: what each department can automate series, logistics section.
In short
The customer gets a message at the steps that matter, not at every carrier scan.
A delay is announced before the expected date, with a new estimate.
A stuck parcel creates an alert for support, who act before the complaint.
Messages come from the company, in its own tone, not from the carrier.
The same circuit works for online sales and for B2B.
Why the carrier’s tracking is not enough
Carriers send their own notifications. They have three flaws. They talk about the parcel, not the order: a customer who ordered three items gets two tracking links and does not know where the third one is. They arrive under the carrier’s brand, often mistaken for spam. And they say nothing about what happens before dispatch, during picking, where many delays are hidden.
The company’s workflow starts from the order, not the parcel. It knows what the customer bought, what has left and what is still waiting.
The messages that matter
- Order confirmed
A summary with the estimated delivery date.
- Picking running late
If the order has not left on the expected date, an honest message with a new estimate.
- Dispatch
The tracking link, with the list of items in the parcel.
- Carrier incident
An alert to support, and a message to the customer if they need to act.
- Delivery
A short confirmation, which can lead to the satisfaction survey.
The second message is the most important and the rarest. Announcing a delay before the customer notices it completely changes how they see it. The same delay, discovered by the customer, becomes a complaint. This message often depends on an upstream delay, at a supplier: the workflow that spots supplier delays feeds it.
How the workflow connects
Tracking a customer order
- The ERP
The order, its items and its promised date.
- The warehouse
The picking status and the parcel number.
- The carrier
Tracking events, read through its API.
- The customer and support
The right message to the right person.
Carriers expose their events through an API or through notifications sent to an address you provide. The n8n documentation describes the webhook trigger, which receives these notifications as soon as they are sent. The workflow then translates a carrier’s dozens of status codes into a few steps people understand.
Support, warned first
The parcel stuck at a depot, the incomplete address, the refused delivery: these incidents end up as complaints if nobody deals with them. The workflow flags them to support as soon as they appear, with the order and the customer. Support can call, correct the address, chase the carrier, before the customer notices. It is the same logic as an alert before a support deadline is missed: act on what is about to go wrong, rather than react to what has gone wrong.
Online sales and B2B, same circuit
An online shop often has some of these messages already, thanks to its platform. The workflow adds what it does not do: the picking delay message and the alert to support. For a company that delivers to businesses, the need is the same, with other recipients: the customer’s buyer, sometimes the storekeeper who receives the goods. The circuit does not change, only the address book does.
To connect your ERP, your warehouse and your carriers, our n8n automation offer starts from the requests your support receives today, and the steps where orders get lost.
Frequently asked questions
How many messages can you send without tiring the customer?
Three or four are enough: confirmation, dispatch, delivery, plus one message if there is a delay or an incident. Passing on every carrier scan tires the customer and drowns the useful information. The tracking link lets those who want it see the detail. The right number is the one that answers the questions the customer would ask, without raising new ones.
Do you need an ERP for this tracking?
You need a place where the order and its promised date exist: an ERP, an online sales platform or sales management software. The workflow reads this source, then the carrier’s. Without any reliable source, the first job is to record orders in a consistent way, before automating their tracking.
Can the customer reply to these messages?
Yes, and you need to plan for it. A reply to a tracking message must reach support, attached to the order, not land in an inbox nobody reads. The workflow can create a ticket from the reply, with the context of the order. The customer then has a real way in, and support does not have to work out which order it is about.
Sources
- Webhook, n8n documentation (new tab)docs.n8n.io
Jim · founder of Brain Plus AI
Also in n8n workflows by department
Practical guide5 min The topic guide
n8n workflows: what each department can automate
Accounting, sales, HR, support, purchasing, marketing, logistics, management: every department has tasks that travel from one tool to another. Here, department by department, are the n8n workflows that save time, and those that are not worth the effort.
Understand4 min
Supplier delays: spot them before the customer does
A supplier delay is usually discovered when the customer calls. An n8n workflow compares promised dates with the confirmations received every day, and warns the buyer early enough to act.
Choose and price4 min
Which department should you automate first with n8n?
Accounting, sales, HR, support: every department has good reasons to go first. Four simple criteria help you choose, and avoid the first project that discourages everyone.