DHL

Track shipments across every DHL business unit and find DHL service points, post offices, and parcel lockers by address or geo-coordinate.

4 actions API key available

DHL website ↗ Platform Documentation ↗ Platform Documentation ↗ Capability data verified 2026-07-14

A DHL tracking number is captured after a label is bought

Agent calls Track Shipment to read the latest status and event timeline

Agent confirms whether the status is in-transit, delivered, or an exception

Agent checks the exception type and the order value behind the shipment

Agent updates the order record and, for a delay, finds a nearer drop-off point

Customer or fulfillment channel is updated with the current event detail

A stalled high-value shipment is routed to ops for a reroute or reship decision

What This Integration Enables

Agents work across the full DHL read surface: Track Shipment for live status and a chronological delivery event timeline, and Find Locations by Address, Find Locations by Geo, and Get Location by ID for the service-point network behind returns and drop-offs. Every operation is read-only, so the connector is a monitoring and enrichment layer rather than a system of record. It gives a fulfillment workflow eyes on the parcel: what happened, when, and where the customer should go next.

Without FlowRunner

Manual status checks Someone opens the DHL portal and re-checks tracking numbers throughout the day

Late exception discovery A stuck or misrouted parcel is noticed only when the customer complains

Generic drop-off guidance Customers are told to "find a DHL location" with no specific point suggested

With FlowRunner

Status read on the event The agent polls Track Shipment and reacts the moment a status changes

Exceptions surfaced early Delivery exceptions are caught and triaged before the customer writes in

Nearest point suggested The agent returns the closest service point with full opening hours attached

Use Case Scenarios

Delivery Monitoring After Label Purchase

A label is bought upstream and returns a DHL tracking number. The agent polls Track Shipment on a schedule, building a delivery event timeline as the parcel moves. On a delivered event, it posts to the fulfillment channel in Slack and closes the order. On an exception event, it does not close anything. It gathers the event detail and routes the case for a human decision, so the shipments that need attention are the only ones a person sees.

Nearest Drop-Off in a Return Confirmation

A customer requests a return. The agent takes the customer's address, calls Find Locations by Address to suggest the closest DHL drop-off point, then Get Location by ID to pull the full opening hours. It writes the location and hours into the return confirmation so the customer gets a specific place to go, not a generic instruction to search.

Order Dashboard Enrichment

An operations dashboard needs a status column that stays current. The agent calls Track Shipment for each open DHL shipment, maps the raw status to a plain-language stage, and updates the order record. Support agents read a chronological event timeline per order instead of pasting tracking numbers into the carrier site one at a time.

Human-in-Loop Highlight

A tracking exception on a low-value parcel is routine. A high-value shipment that has stopped moving for days is a judgment call, and human-in-the-loop is the pattern where the agent pauses, assembles the context and the choices, routes to the right person, and resumes on their answer. When Track Shipment reports a stalled or exception status on a shipment above a configurable value, the agent does not auto-reship or sit on it. It assembles the event timeline, the customer, the order value, and the two viable paths, then messages ops in Slack: "DHL shipment for order #4471 has shown no movement for 4 days. Value $920. Reroute to a nearer service point, or reship? Timeline attached." Ops decides. The agent records the decision with the approver and acts.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

4 actions

Tracking

Track Shipment Retrieves the live status and a chronological delivery event timeline for a DHL tracking number. Used to monitor shipments in flight and detect delivery or exception events as they happen.

Location Finder

Find Locations by Address Finds DHL service points, lockers, and drop-off locations near a postal address. Used to suggest the closest drop-off point in a return or pickup flow.
Find Locations by Geo Finds DHL service points, lockers, and drop-off locations near a set of geo-coordinates. Used when a workflow already has latitude and longitude rather than a formatted address.
Get Location by ID Retrieves the full details of a specific DHL location, including opening hours. Used to enrich a suggested drop-off point with the information a customer needs to actually use it.

Frequently Asked Questions

What can FlowRunner do with DHL?

FlowRunner agents can run Track Shipment, Find Locations by Address, and Find Locations by Geo in DHL, plus 1 more action.

Does connecting DHL to FlowRunner require OAuth?

No. DHL connects to FlowRunner with an API key, no OAuth flow required.

Can DHL trigger a FlowRunner workflow automatically?

DHL doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with DHL

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us

DHL