Skip to content
Pixie CRMPixie CRMHelp Centre
Ctrl K
Back to Pixie CRM ↗

Pixie CRM integration guide

DHL Express Shipping API

Connect Pixie CRM with DHL Express Shipping API through a controlled integration workflow. Review authentication, data scope and test behaviour before enabling live synchronisation.

Pixie CRMIntegration referenceUpdated 2026-10-26
Where to startSetup → Modules / Integration settings → DHL Express Shipping API
Availability firstAvailability can vary by workspace, subscription and staff role. Confirm the capability is enabled and that your role is authorised before changing configuration or moving live data.

Set up and verify

  1. Confirm that the relevant integration capability is available in Setup → Modules or the integration settings area for your Pixie CRM workspace.
  2. Open the DHL Express Shipping API configuration screen and identify the connection method required by the provider.
  3. Add credentials, OAuth authorisation or API details only through the secure configuration fields provided for the integration. Never place secrets in CRM notes or support messages.
  4. Choose the data scope, mappings, permissions, webhook behaviour or synchronisation direction required by your workflow.
  5. Save the configuration and run the available authentication or connection test before moving live data.
  6. Perform a limited test action or synchronisation with a record you can safely verify at both ends.
  7. Check Pixie CRM activity, integration logs and the external system to confirm the expected result and rule out duplicates or unexpected field changes.
  8. Enable broader production use only after the test is successful and the responsible administrator is satisfied with access, mappings and failure handling.

Checks before wider use

  • Connection credentials are stored only in authorised secure settings.
  • Data scope and field mappings are limited to what the workflow needs.
  • A test record has been verified in Pixie CRM and the connected service.
  • Failure, retry and duplicate-handling behaviour is understood before production use.
Keep configuration controlled.Use authorised credentials and least-privilege permissions. Test with low-risk data first, preserve audit evidence and never expose secrets in notes or tickets.