Resources · n8n integration

DHL n8n integrationAutomate DHL with n8n.

Where is that parcel right now? The DHL n8n integration answers that from inside a workflow: one node, one resource, one operation, Get Tracking Details. No DHL trigger ships with n8n, so a Schedule Trigger or a Webhook starts the run. Built for ops and support teams.

Try the DHL integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the DHL n8n integration actually do?

The DHL n8n integration is a single node, n8n-nodes-base.dhl, wired to the DHL shipment tracking API. It carries one resource, Shipment, and one operation, Get Tracking Details. A workflow hands it a tracking number, the node comes back with what the carrier knows, and the next node in the chain decides what to do with that answer.

Learn one gesture and the node is yours: a workflow already holds a tracking number, DHL turns that number into an answer, the next node acts on it. Everything after that is wiring you already know.

First shape, the support desk. A buyer writes in asking where the package is. The workflow picks up the ticket, reads the tracking number off the order, runs Get Tracking Details, and drops the answer into the Slack channel the support team already lives in. Nobody opens a carrier portal to reply.

Second shape, the morning batch. A Google Sheets tab lists every shipment still in transit. A Schedule Trigger, the n8n node that fires on a fixed interval, runs the sheet once a day, loops over the rows, calls DHL for each number, and writes the answer back beside the row. The status column stops being a manual chore.

Third shape, the proactive email. Same loop, different ending. Instead of landing in a cell, the answer feeds a Gmail message to the buyer, with an IF node in the middle deciding which shipments are worth writing about at all.

The node covers the catalogue operation, Get Tracking Details. Anything that sits outside the catalogue's operations goes through the HTTP Request node, which calls any endpoint of the DHL API and reuses the very same credential through predefined authentication. That is standard n8n practice, not a workaround.

New to this kind of node? The n8n training covers credentials and expressions before you touch a carrier API, and the n8n review weighs the platform against the alternatives.

Connect

How do you connect DHL to n8n?

  1. 01

    Open a DHL Developer account

    The credential the node expects is an API key, and the key lives in the DHL Developer portal. Register there first, then select the user icon to open User Apps. That page is where every key you will ever paste into n8n comes from, so it is worth keeping a tab on it while you set the rest up.

  2. 02

    Create an app and attach the tracking API

    Select Create App, fill in an App name such as n8n integration and a Machine name such as n8n_integration. In SELECT APIs, pick Shipment Tracking - Unified. The API then appears in the Add API to app section, where you select the plus sign next to it. Finish with Create App.

  3. 03

    Paste the key into an n8n credential

    Open the app you just created, select Show key next to API Key, and copy the value. In n8n, go to Credentials, create a DHL credential and paste it in. A credential is created once and reused by every workflow after that, and the node offers it in its own dropdown list, on n8n Cloud and on a self-hosted instance alike.

Actions

What can the DHL node do?

The DHL node exposes 1 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGet Tracking Details
Shipment✓

Shipment

1 operation
01

Get tracking details for a shipment

shipment.get

What you see in n8n

Notes & use cases

This operation asks DHL about one shipment and hands the carrier's answer back to the workflow as an item the next node can read.

Key parameters

  • Tracking Number: the number identifying the shipment. It is required, so an empty value stops the node. It usually arrives from the previous node as an expression, written {{ $json.field }}.
  • Recipient's Postal Code: optional, inside the Options collection. DHL returns more detailed information on the shipment when you provide it, because it acts as a verification step.
Use cases
a support workflow settles a "where is the parcel" ticket without anyone leaving the chat window.
Need help

Need help automating DHL with n8n?

A person reads every message.

FAQ

DHL and n8n, the questions that come next

01Is the DHL n8n integration free?
Yes on the n8n side. The DHL node is bundled with n8n, so there is nothing to install and nothing extra to pay, whether you run n8n Cloud or self-host the Community Edition under the Sustainable Use license. The same workflow behaves identically in both. What DHL itself asks for a developer account and a tracking API key is a separate matter, decided in the DHL Developer portal and not covered here. Budget the n8n side at zero and check the carrier side in your own portal before you build a workflow that runs every day.
02What credentials does the DHL node need?
One API key, and that is the only supported authentication method for this node. You get it from a DHL Developer account: open User Apps, create an app with an App name and a Machine name, select Shipment Tracking - Unified under SELECT APIs, attach it with the plus sign in the Add API to app section, then reveal and copy the API Key from the app details. Paste that value into a DHL credential in n8n. The node has no authentication selector of its own, so once the credential exists you simply pick it from the dropdown.
03What are the limits of the DHL node in n8n?
The catalogue gives this node one resource, Shipment, and one operation, Get Tracking Details, built around a required Tracking Number and an optional Recipient's Postal Code. That is the surface you get out of the box. Anything that sits outside the catalogue's operations goes through the HTTP Request node, which calls any endpoint of the DHL API and reuses the same credential through predefined authentication. So the practical limit is not a wall, it is a switch: dedicated node for tracking, HTTP Request for the rest, both pointing at the same key.
04Does DHL trigger an n8n workflow in real time?
No. DHL has no trigger node in n8n, so a workflow about shipments never starts by itself from the carrier. Something else has to start it. A Schedule Trigger fires on a fixed interval, which suits a daily or hourly sweep of open shipments. An n8n Webhook, an URL that a third-party service calls, suits the case where your shop or helpdesk already pushes events. Or another tool's trigger opens the run, and the DHL node simply sits further down the chain. Pick the starter first, then add the node.
05n8n or Make for DHL tracking?
It depends on four things, and price is only one of them. Make is a hosted automation platform with no self-hosting option, billed per operation. n8n runs on n8n Cloud or on your own server through Docker or npm, and the workflow is the same either way. So ask: do you need the data to stay on infrastructure you control, do you prefer a predictable bill over per-operation billing, does your team read a visual canvas more easily on one side than the other, and do you expect to drop down to HTTP Request often. Answer those and the choice makes itself.
Same platform

Other docs you might need on this stack.

Browse all integrations