DPD Germany
LogisticsConnect AI agents to DPD Germany, the parcel carrier's public shipping web services. Agents obtain an auth token, create parcel shipments with printable labels, and retrieve tracking data so German parcel dispatch runs straight from a flow.
What This Integration Enables
This is a carrier account, not a shipping platform, and the three actions on it are not a gap. DPD Germany's public web services do exactly three things for a shipper on a direct Delis contract: prove who you are, mint a parcel, and tell you where that parcel is. Get Auth Token exchanges your Delis ID and password for a 64 character token valid for 24 hours and returns the sending depot that shipment creation needs. Create Shipment stores the order with DPD and returns the parcel label number plus a printable label. Get Tracking Data returns the current status and scan history for a 14 digit parcel label number. If your business ships on your own DPD contract in Germany, that is the whole job, and a thinner connector that maps cleanly onto the carrier's own model is easier to reason about than a broad one that abstracts it away.
Two details shape how the flow should be built. First, the token: it lasts 24 hours and login attempts are limited to roughly ten per day, so Get Auth Token is a once per day step whose result is cached and passed into the other two actions, never a step that runs at the top of every shipment. Second, the label: Create Shipment returns the PDF as a Base64 string, and with Store Label File enabled it is also uploaded to FlowRunner file storage and returned as a downloadable URL, which is the form a packing bench, an email to a customer, or an archive can actually use. Weight is entered in grams and converted to DPD decagram units automatically, so the flow never handles the carrier's internal unit.
It is worth being clear about what this connector is not, because the name it shares with another entry in this catalog invites confusion. DPD Romania is a different API, a different credential, and a materially different product: a REST interface with cash on delivery, declared value, address validation against the DPD nomenclature, office and locker lookup, pickup requests, and shipment cancellation. None of that is here. This is the German public SOAP service, and it does what a German shipper on a Delis account needs it to do. There are no triggers, so a flow starts from an order event, a pick confirmation, or a schedule.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Order to printed label at the bench
An order is marked packed in Shopify or WooCommerce. The agent takes the cached auth token and the sending depot from the day's Get Auth Token call, reads the recipient address off the order and the measured weight in grams off the bench scale, and calls Create Shipment. Back comes the parcel label number and, with Store Label File enabled, a URL to the label PDF in FlowRunner file storage. The URL goes straight to the label printer queue and the parcel label number goes back onto the order so customer service and the customer see the same reference. The packer never opens a second application.
Tracking that reaches the customer before the complaint does
Get Tracking Data returns the scan history for a parcel, and only for parcels created under your own account, which is exactly the set you care about. On a schedule the agent walks the open parcels, pulls each one's status, and diffs it against the last recorded state. Progress updates go quietly into the order record in Airtable. Two states do not go quietly: a parcel with no scan at all a day after the label was created, meaning it was almost certainly never handed over, and a delivery attempt that failed. Both post to Slack with the parcel number and the scan history, because both have a short window where a person can still fix the outcome for the customer.
Deciding what to route to a direct DPD contract
A shipper with a Delis contract usually also has a multi-carrier option in the mix. The agent can route deliberately: parcels on lanes where the negotiated DPD rate wins go through this connector, and the rest go to a broader platform such as shipcloud, which fronts DHL, DPD, UPS, GLS, and others behind one API. The split is a business rule, and keeping it in the flow means it is visible and changeable rather than baked into whichever tool the warehouse happened to open. Both paths write the same fields back onto the order, so downstream reporting in Google Sheets does not care which one shipped the parcel.
Human-in-Loop Highlight
The gate on DPD Germany is defined by an action that is not here. This connector has three operations, and none of them cancels, voids, or deletes a shipment. Once Create Shipment returns a parcel label number, that parcel exists in DPD's system under your Delis ID, and putting it right is a conversation with the carrier rather than a call in the flow. Compare that with DPD Romania, which does ship a Cancel Shipment operation for shipments not yet ordered for pickup. Same brand, different recourse, and the difference should change how much care sits in front of the create call.
Two failure modes are worth stopping for specifically, and both are quiet. Weight is entered in grams. A field mapped from a system that stores kilograms produces a 2 gram parcel that DPD will happily accept, and the discrepancy surfaces later as a correction rather than immediately as an error. And the recipient address is read from the order record, which may be older than the address the customer gave support last Tuesday. So the agent checks both before it calls: it compares the supplied weight against the expected weight for the picked items, and it compares the shipping address against the most recent address on the customer record. When either disagrees it stops and asks the packer in Slack: "Order 5518 reports 2.4 g, expected around 2,400 g for these items. Address on the order is Hauptstrasse 14, support has Lindenweg 3 as of 4 days ago. Confirm weight and address before I create the label?" The packer is holding the box and can settle both in seconds.
That is what human-in-the-loop is for on a connector this narrow. There is no clever recovery to automate, so the value has to be created before the irreversible call rather than after it. One operational note in the same spirit: the ten logins per day limit makes authentication itself worth protecting. A flow that calls Get Auth Token per shipment instead of caching the token for its 24 hour life will exhaust the budget and take the entire day's dispatch down with it, which is a failure a person should be alerted to immediately rather than discovering at the cutoff.
Agent Capabilities
3 actionsAuthentication
1- Get Auth Token Authenticates with the DPD login service using the configured Delis ID and password and returns a 64 character auth token, valid for 24 hours, along with the sending depot that Create Shipment requires. Login is limited to roughly ten attempts per day, so call this once and reuse the token across shipment and tracking calls rather than authenticating per parcel.
Shipments
1- Create Shipment Creates a parcel shipment and returns the DPD parcel label number plus a printable shipping label. The label PDF comes back as a Base64 string and, with Store Label File enabled, is also uploaded to FlowRunner file storage and returned as a downloadable URL. Requires the auth token and the sending depot from Get Auth Token. Weight is entered in grams and converted to DPD decagram units automatically. This is the one call on this connector that cannot be undone here.
Tracking
1- Get Tracking Data Retrieves the current tracking status and scan history for a parcel by its 14 digit DPD parcel label number. Only parcels created under your own account can be tracked, which makes this the read behind proactive delivery updates on your own shipments rather than a general tracking lookup.
Frequently Asked Questions
What can FlowRunner do with DPD Germany?
FlowRunner agents can run Get Auth Token, Create Shipment, and Get Tracking Data in DPD Germany.
Does connecting DPD Germany to FlowRunner require OAuth?
No. DPD Germany connects to FlowRunner with session-based authentication, no OAuth flow required.
Can DPD Germany trigger a FlowRunner workflow automatically?
DPD Germany doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with DPD Germany
$100 in credits. No card required. Connect in minutes.