Carrier Tracking Sync for Zendesk - FedEx + UPS
Kyle Tully
Ingest: an HMAC-verified Zendesk webhook detects the carrier and upserts an idempotent shipment record linked to the ticket.
Sync: every 30 minutes, active shipments are polled from FedEx and UPS, statuses normalized to one enum, scan history appended idempotently.
Prune: a daily job retires shipments terminal for over 90 days, deleting their scan events first to bound record growth.
Error handler: a shared workflow on every flow emits a structured alert on failure, so nothing fails silently.
System Overview: purpose, components, flows, and risks, documented from the codebase.
Data model: two Zendesk Custom Objects, carrier_shipment and tracking_event, with the status lifecycle and a traceability table back to source.
Integration spec: the Zendesk, n8n, FedEx, and UPS interfaces with their auth methods and resilience rules.
Like this project
Posted Jun 1, 2026
Self-refreshing FedEx/UPS shipment records inside Zendesk. 4 idempotent n8n workflows, normalized statuses, plus docs an ops team runs without me. Dev/sandbox.
