DTDC

DTDC + Konnectify

DTDC Integration with Konnectify

Connect DTDC with Konnectify to automate shipment tracking lookups and operational workflows using DTDC actions inside your integrations.

Shipping & Tracking 0 Triggers 2 Actions

ON THIS PAGE

→ What is DTDC? → API & Authentication → How to connect → Triggers (0) → Actions (2) → Popular automations → FAQ

What is DTDC?

DTDC is a logistics and courier service provider used by businesses to ship packages and track consignments across delivery networks. By integrating DTDC with Konnectify, you can standardize tracking checks, enrich order workflows with shipment status, and route operational updates to your internal systems.

Use DTDC actions in Konnectify when you need shipment and tracking data available inside broader automations (e.g., updating order systems, notifying support, or generating operational reports).

New to DTDC?

Create an account / get access to DTDC services and request API access details from your DTDC representative.

Visit DTDC →

New to Konnectify?

Build workflows with a visual editor, connect apps, and automate tracking-based operations end-to-end.

Create Konnectify account →

What you can automate

• Fetch tracking details for a shipment/consignment

• Enrich order records with latest delivery status

• Trigger downstream notifications based on tracking updates

• Standardize tracking lookups across multiple stores/teams

• Build exception workflows for delayed/undelivered shipments

• Create reporting pipelines using DTDC status data

API & Authentication

Authentication type: Credentials (Base URL + API Key)

This connector uses a credentials-based setup. You’ll provide an API Key issued by DTDC and (optionally) a Base URL. Konnectify stores your connection securely and uses it to authenticate requests to DTDC on your behalf.

Connection fields

Base URL (optional): If your DTDC API is hosted on a specific domain, set it here (example: https://yourdomain.dtdc.com/).
API Key: The key/token used to authenticate API calls.

What the DTDC connector can do

Run tracking lookups (Track data)
Execute DTDC automation steps via an RPA-style action (RPA Agent)

Important DTDC API availability, feature access, and rate limits can vary by account type and agreement. If you see authentication failures or unexpected throttling, confirm your API plan and permitted endpoints with DTDC support.

API documentation: Refer to DTDC’s official site / API documentation provided by your DTDC representative.

How to connect DTDC to Konnectify

Prerequisites

A Konnectify account with permission to create/edit Workflows
Your DTDC API Key
(Optional) DTDC Base URL for your environment/tenant
At least one tracking/consignment identifier to test the action

Add DTDC to a Workflow

Open Konnectify and create a new Workflow (or open an existing one).
In the step/app picker, search for DTDC and add it to your flow.

Authorize via API Key (Credentials)

Click Connect or Add new connection.
Enter your API Key.
Optionally set Base URL if your DTDC endpoint differs from the default provided by your account.
Save the connection.

Configure the Action

Select the DTDC action you want to run (for example, Track data).
Map input fields from previous steps (e.g., AWB/consignment number from your order system).
Save the step.

Note: Ensure the identifiers you pass (AWB/consignment/reference numbers) match the format expected by your DTDC account/API. If the DTDC endpoint returns empty or partial results, test with a known valid shipment first.

Test the Workflow

Run a test with sample shipment data.
Verify the DTDC step returns expected tracking information.
If needed, adjust mappings and re-test.

Activate the Workflow

Turn on the Workflow.
Monitor initial runs to confirm tracking lookups and downstream steps behave as expected.

Triggers 0

This DTDC connector currently doesn’t include triggers. You can still use DTDC actions in workflows that start from other apps (e.g., eCommerce, CRM, helpdesk) or from Konnectify utilities like schedules and webhooks.

Tip: Start your workflow with a scheduler (e.g., every 2 hours) and then call Track data to poll shipment status and update your downstream systems.

Actions 2

Use DTDC actions to fetch tracking information and power shipment-related workflows across your stack.

Shipping & Tracking 2 actions

RPA Agent

Run DTDC-related automation via an RPA-style agent step.

Track data

Fetch shipment tracking data from DTDC for a given consignment/AWB.

Popular automations

Examples you can build with DTDC actions in Konnectify (your workflow trigger can come from any app, a webhook, or a schedule).

Scheduled shipment status monitor

Run on a schedule, pull the latest DTDC tracking info, and update downstream systems with the newest delivery status.

Schedule (e.g., hourly) → Track data

Support ticket enrichment with tracking

When a customer asks “Where is my order?”, automatically fetch DTDC tracking details and add them to the ticket or internal notes.

Ticket created/updated (other app) → Track data

Order follow-up after dispatch

After an order is marked as shipped in your store/OMS, look up DTDC tracking to confirm movement and branch into exception handling if needed.

Order shipped (other app) → Track data → RPA Agent

Late delivery exception workflow

On a daily schedule, check DTDC status for in-transit shipments and route delayed ones for manual review or escalation.

Schedule (daily) → Track data → RPA Agent

FAQ

How does DTDC authentication work in Konnectify?

The DTDC connector uses a credentials connection: you provide an API Key (and optionally a Base URL). Konnectify uses these credentials to authenticate DTDC API calls from your workflows.

Which DTDC plans/accounts are supported?

Any DTDC account that has API access and a valid API Key should work. Availability of specific endpoints can depend on your DTDC agreement and the API products enabled for your account.

How do DTDC triggers work here—webhooks or polling?

This integration currently provides 0 DTDC triggers. To automate based on shipment changes, use a trigger from another app or a Konnectify scheduler/webhook, then call Track data to fetch the latest status (polling pattern).

Does this connector support upserts or duplicate prevention?

No upsert-style DTDC actions are exposed in this connector. For duplicate prevention in your workflow, store a last-seen tracking checkpoint/status in your database/CRM and only continue when the new status differs from the stored one.

How does Konnectify handle DTDC API rate limits?

If DTDC enforces rate limits, requests may be throttled or rejected temporarily. Use scheduling, batching in upstream apps, and backoff/retry patterns in your workflow design (where available) to reduce spikes. If you expect high volume, ask DTDC about increasing limits for your account.

Can I connect multiple DTDC accounts?

Yes. Create multiple DTDC connections in Konnectify (each with its own API Key and Base URL if needed) and select the right connection per workflow or per step.

What should I use the “RPA Agent” action for?

Use RPA Agent when your DTDC use case requires automation beyond a simple tracking lookup—such as orchestrating multi-step operational tasks or handling scenarios that depend on your DTDC environment setup. If you only need shipment status, prefer Track data for a simpler, API-first approach.

Ready to automate your DTDC workflows?

Connect DTDC to Konnectify and build tracking-powered automations in minutes.

Get started free →