n8n 聚合 FedEx/UPS/DHL 轨迹：统一状态表 + 断路器

Aggregate FedEx/UPS/DHL tracking into one status schema

据 n8n 官方模板：每 15 分钟拉取未完结货件，按承运商查轨迹，归一化为 PRE_TRANSIT/IN_TRANSIT/EXCEPTION 等，写入同一张表；429/5xx 走断路器。

据公开帖摘要

Kyle T. 的 n8n 模板写明：定时拉取 Data Table shipment_tracking 中未完结货件 → 按 carrier 路由 FedEx/UPS/DHL → 带断路器调轨迹 API → 归一化 canonicalStatus（含 PRE_TRANSIT、IN_TRANSIT、OUT_FOR_DELIVERY、DELIVERED、EXCEPTION、UNKNOWN）→ 以 trackingNumber 回写。适合跨境卖家把头程/尾程多承运商轨迹收成一张异常看板，再交给客服 Agent 起草说明（不自动承诺放行）。

可复制 Prompt 用 n8n 工作流

You normalize multi-carrier tracking for a cross-border seller.
Input rows: trackingNumber, carrier (fedex|ups|dhl|other), rawStatus, httpStatus, lastCheckedAt.
Output for each row:
- canonicalStatus: one of PRE_TRANSIT | IN_TRANSIT | OUT_FOR_DELIVERY | DELIVERED | EXCEPTION | RETURNED_TO_SENDER | UNKNOWN
- exception_hint: short note if EXCEPTION (customs hold, address issue, delay) — only from rawStatus text, never invent
- action_for_ops: SLA_OK | WATCH | ESCALATE_CARRIER | NOTIFY_BUYER_DRAFT
Skip rows already DELIVERED or RETURNED_TO_SENDER.
Do not invent ETAs or tracking events missing from input.

读原文 Read the original 推广此用例 Boost this case

来源： n8n · Jun 1, 2026 · 约；模板页写 Last update 约 4 months ago（相对 2026-10） · 工具：n8n · FedEx Track API · UPS Track API · DHL API · n8n Data Table