A HubSpot Elite Solutions Partner built to help organizations unify strategy, systems, and execution. We design HubSpot systems that scale.

See how we've solved complex HubSpot challenges across migrations, integrations, CMS, automation, and optimization.

Join a team building smarter HubSpot systems. We value strategic thinkers who move proactively, care about quality, and want to do meaningful work.

Integration

HubSpot <> CargoWise Integration

Powered by Commercient
HubSpot and CargoWise integration
Integration Assessment
Integration Assessment · Logistics

CargoWise × HubSpot

How a freight forwarder or customs broker running CargoWise can bring client organizations, quotes, bookings, shipment milestones, customs events and lane volumes into HubSpot, so sales and account management work from real freight data, and how HubSpot rate requests can reach the operations team as CargoWise quotes.

WiseTech GlobaleAdaptor inbound & outboundUniversal Shipment (XUS)Universal Event (XUE)eAdaptor Next · OAuth 2.0Custom build
Platform ownerWiseTech Global
Integration typeCustom build on CargoWise eAdaptor
Primary directionCargoWise → HubSpot
FeasibilityBuildable, license-gated
API accessGated API
01 — Summary

Does CargoWise integrate with HubSpot?

CargoWise is the operating system of many freight forwarders and customs brokers: every client organization, shipment, consol, customs declaration and invoice runs through it. HubSpot is where those clients are won and grown. Account managers need to see in HubSpot what each client actually ships, and sales needs quote requests to reach operations without re-keying.

API access
Open APIOpen with conditionsGated API

Documentation and credentials come only through the vendor, under a license, partner agreement or customer login.

Gated API. The forwarder buys and enables the eAdaptor modules. WiseTech releases the developer guide and endpoint details to licensed customers.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

CargoWise exposes its records through eAdaptor, so shipment, customs and client data can reach HubSpot as it happens, once the forwarder has eAdaptor enabled.

Campaign Creators assessment

eAdaptor is CargoWise's integration interface. The inbound service accepts XML to query, add and update records. The outbound service sends XML messages when workflow triggers or milestones fire in CargoWise: Universal Shipment messages (XUS) carry the full record, and Universal Event messages (XUE) carry the record identifier and the event. WiseTech's newer eAdaptor Next replaces SOAP for inbound and outbound communication and uses OAuth 2.0. CC builds a sync module that receives these messages, matches each one to the right HubSpot company and deal, and writes milestones, lane volumes and revenue rollups. The gate is commercial: eAdaptor is licensed and enabled by the forwarder, and its developer guide is released after purchase.

Scorecard
Data richnessHigh
Real-time eventsWorkflow-driven
API accessLicensed
Build complexityMod–High

Ratings are CC judgments from WiseTech's public product pages and public profiles of the eAdaptor interface. Message types, field paths and limits are confirmed with the forwarder's CargoWise administrator and WiseTech during discovery.

Strength

Every client and shipment in one system

Organizations, shipments, consols, customs declarations and accounting all live in CargoWise, so one interface supplies everything an account manager needs.

Plan for

Outbound messages depend on workflow setup

CargoWise only sends what its workflow templates are configured to send. The forwarder's CargoWise administrator adds the triggers and milestones the integration needs, and tests them with CC.

Gate

eAdaptor is licensed by the forwarder

The forwarder buys and enables the eAdaptor modules (or eAdaptor Next) and shares the developer guide and endpoint details with CC. Make this a client-owned dependency with a date in the SOW.

02 — API modules

Which CargoWise APIs does the integration use?

Seven parts of CargoWise matter to a HubSpot build. Four carry the integration, two enrich it, and one is a scope decision the forwarder makes up front.

Integration path

eAdaptor Outbound

Workflow-triggered XML messages

CargoWise sends a message to a service CC hosts whenever a configured workflow trigger or milestone fires on a record.

  • Triggers set in CargoWise workflow templates
  • Sent messages logged in EDI Interchange
  • Recipient set up for the integration in CargoWise
Core

Universal Shipment (XUS)

UniversalInterchange · UniversalShipment

The full record behind a message: forwarding shipments, consols, customs declarations and their parties, routing, containers and charges.

  • Client organization and addresses on each shipment
  • Origin, destination, mode and container details
  • Basis for lane, volume and TEU rollups
Core

Universal Event (XUE)

UniversalEvent

A small message with the record identifier and the event or milestone that triggered it.

  • Shipment booked, departed, arrived, delivered
  • Customs events on declarations
  • Becomes a timeline event on the HubSpot deal and company
Write-back

eAdaptor Inbound

XML over HTTPS · query, add, update

Accepts Universal XML or Native XML to query CargoWise records or to add and update them.

  • Full records fetched on demand after an event
  • Rate requests from HubSpot sent to operations
  • Backfill of active clients and shipments
Preferred path

eAdaptor Next

OAuth 2.0 · JWT authorization

WiseTech's newer connectivity option, which replaces SOAP for inbound and outbound communication with modern security.

  • OAuth 2.0 authentication
  • Certificate-based identity and encryption
  • Used where the forwarder has it enabled
Enrichment

Native XML & Universal Transaction

Organizations · accounting

Organization records and accounting transactions, used for client master data and revenue per client.

  • Organization codes, names and addresses
  • Invoiced revenue by client and job
  • Message types confirmed in discovery
Scope decision

CargoWise CRM or HubSpot

Opportunities, enquiries, campaigns

CargoWise includes its own customer relationship tools. HubSpot becomes the place where marketing, pipeline and client reporting come together, and the forwarder decides which team works in which system.

  • Website enquiries and campaigns run in HubSpot
  • Operational quotes and bookings stay in CargoWise
  • One owner per record type, signed off in the SOW
03 — Framework

How does the CargoWise HubSpot integration work?

CargoWise sends XUS and XUE messages to a CC-hosted service. The integration layer parses the XML, matches the client organization to a HubSpot company, rolls up volumes and revenue, and writes to HubSpot. HubSpot rate requests travel back to CargoWise through eAdaptor Inbound.

CargoWise
eAdaptor OutboundXUS and XUE messages on workflow triggers
eAdaptor Inboundquery, add and update records
Organizationsclient codes, names, addresses
Accountinginvoiced revenue by client and job
CC integration layer
Message receiverauthenticates, acknowledges, queues
XML parserXUS, XUE and Native XML to JSON
Identity resolverorganization code → HubSpot company
Lane & revenue rollupsshipments, TEU, revenue by lane
HubSpot writerbatch upserts, error replay
HubSpot
Companiesclient organizations and their codes
Contactsshipper and consignee contacts
Dealsquotes, bookings and lane opportunities
Shipments (custom object)one record per shipment or consol
Workflows & reportsaccount health, lane growth, service alerts
CargoWise → HubSpot (clients, shipments, milestones, volumes)HubSpot → CargoWise (rate requests and new client details)
Principle

CargoWise owns the job

Shipments, customs declarations, charges and invoices are created and changed in CargoWise. HubSpot stores what sales and account management act on.

Principle

Store rollups, link the detail

HubSpot keeps shipment status, lane volumes and revenue totals. Full documents, charges and customs data stay in CargoWise, referenced by job number.

Principle

One client key

The CargoWise organization code is stored on the HubSpot company and used by every message, so a client never appears twice.

04 — Process

What does CargoWise HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins, so the fixed scope holds even when eAdaptor setup or message content differs from what was planned.

1

Licensing & access

Confirm the forwarder has eAdaptor (or eAdaptor Next) licensed and enabled, obtain the developer guide and a test environment, and agree who administers CargoWise workflow templates.

Gate to next phaseTest messages received from the forwarder's CargoWise test environment
2

Message design

Choose the triggers and milestones the integration needs (booking, departure, arrival, delivery, customs events) and whether each sends a full XUS or a short XUE.

Gate to next phaseSigned trigger list and sample messages for each
3

Identity & ownership

Agree the match rules (organization code first, then domain and name) and which system owns clients, contacts, opportunities and quotes.

Gate to next phaseSigned match rules and record ownership matrix
4

HubSpot data model

Create the Shipment custom object, company and deal properties, the quote and lane pipelines, and association labels for shipper and consignee in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build

Build the message receiver, XML parser, identity resolver, rollups and HubSpot writer, plus the rate request path back to CargoWise, with an error replay queue.

Gate to next phaseTest shipments flow end to end with correct milestones
6

Backfill

Load client organizations and an agreed window of shipment history through eAdaptor Inbound, then compute lane and revenue rollups once.

Gate to next phaseVolumes and revenue per client reconcile to CargoWise reports
7

Workflows, parallel run & launch

Build account health, lane growth and service alert workflows with emails paused, run two weeks in parallel, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the CargoWise HubSpot integration sync?

CargoWise field paths come from the Universal and Native XML schemas in the eAdaptor developer guide, which WiseTech releases to licensed customers. Fields below are described plainly and confirmed against the forwarder's sample messages in discovery.

CargoWise fieldHubSpot propertyObjectDirectionNotes
Clients · organizations & contacts
Organization codecw_org_codeCompanyCW → HSPrimary match key. Unique.
Organization namenameCompany↔ BothFill blanks; HubSpot edits stay in HubSpot.
Organization address and countryaddress, city, countryCompanyCW → HS
Organization role (shipper, consignee, importer)cw_org_rolesCompanyCW → HSMulti-select. Confirm role values in discovery.
Organization contactsfirstname, lastname, email, phoneContactCW → HSAssociated to the company.
Sales rep on the organizationhubspot_owner_idCompanyCW → HSMapped to HubSpot users.
Quotes & bookings
HubSpot rate request formQuote request in CargoWiseDealHS → CWOrigin, destination, mode, commodity, volume. Confirm the inbound message type in discovery.
Quote numbercw_quote_numberDealCW → HSLinks the deal to the CargoWise quote.
Quote statusDeal stageDealCW → HSQuoted, accepted or declined mapped to the quote pipeline.
Booking created from quoteDeal stage: BookedDealCW → HSFrom the booking trigger.
Shipment / job numbercw_job_numberShipment (custom object)CW → HSUnique per shipment.
Shipments, consols & milestones
Transport modecw_modeShipment (custom object)CW → HSSea, air, road, rail.
Origin and destinationcw_origin, cw_destinationShipment (custom object)CW → HSPort or location codes.
ETD / ETAcw_etd, cw_etaShipment (custom object)CW → HSUpdated on each event.
Milestone event (XUE)Custom event: Shipment milestoneCompanyCW → HSBooked, departed, arrived, delivered.
Latest milestonecw_shipment_statusShipment (custom object)CW → HS
Consol referencecw_consol_numberShipment (custom object)CW → HSGroups shipments on one consolidation.
Exception or delay eventTicketTicketCW → HSOpens a service ticket for the account team.
Lanes, volumes & revenue
Container count and sizecw_teu_12mCompanyCW → HSTEU rolled up in the integration layer.
Shipments per clientcw_shipments_12mCompanyCW → HSRolling 12-month count.
Top lanescw_top_lanesCompanyCW → HSOrigin–destination pairs by volume.
Invoiced revenue (Universal Transaction)cw_revenue_12mCompanyCW → HSConfirm accounting message and currency handling.
Last shipment datecw_last_shipment_dateCompanyCW → HSDrives dormant-client workflows.
Customs
Customs declaration eventsCustom event: Customs milestoneCompanyCW → HSLodged, cleared, held.
Declarations per clientcw_customs_entries_12mCompanyCW → HSRolled up in the integration layer.
06 — Auth & API

How are authentication and API limits handled?

WiseTech gates eAdaptor by licence; HubSpot uses one app token. Values WiseTech does not publish are marked for confirmation.

TopicCargoWiseHubSpot
Access modeleAdaptor modules are purchased and enabled by the forwarder. The developer guide and endpoint details are released to licensed customers.Self-serve in the client portal; custom objects and custom events need an Enterprise hub.
InterfaceseAdaptor Inbound (XML over HTTPS) and eAdaptor Outbound (XML messages to a listening service). eAdaptor Next replaces SOAP for both directions.REST APIs: CRM objects, associations, custom events, imports.
AuthenticationLegacy eAdaptor uses credentials issued per instance. eAdaptor Next uses OAuth 2.0, JWT authorization and certificate-based identity. Confirm the method in discovery.Private app access token or OAuth 2.0 public app, scoped per object.
Message formatsUniversal XML (UniversalShipment, UniversalEvent, UniversalTransaction in a UniversalInterchange envelope) and Native XML.JSON.
TriggersWorkflow templates in CargoWise decide which events send a message and whether it is a full XUS or a short XUE.HubSpot workflows and form submissions call the integration for rate requests.
Rate limitsNot published. Confirm with WiseTech.Per-10-second burst and daily limits by subscription tier.
MonitoringSent messages and their status appear in CargoWise EDI Interchange.Integration layer logs every message and replays failures.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

eAdaptor licensing and enablementHigh

Nothing can be built until the forwarder has eAdaptor enabled and shares the developer guide. Make it a client-owned dependency with a date, and plan for eAdaptor Next where the forwarder offers it.

Workflow templates set what CargoWise sendsHigh

Outbound messages exist only for configured triggers. The forwarder's CargoWise administrator configures and tests them with CC during message design.

Two places for customer relationshipsMedium

CargoWise includes CRM tools and HubSpot holds the commercial relationship. A signed ownership matrix decides which system owns opportunities, enquiries and contacts.

Organization codes and duplicatesMedium

One client can have several CargoWise organizations by branch or role. The integration groups them under one HubSpot company using a parent mapping agreed in discovery.

Message volumeMedium

Busy forwarders send many events a day. HubSpot stores shipment status and rollups; full documents and charges stay in CargoWise.

Customs data sensitivityLow

Customs declarations carry tariff and value details. HubSpot receives events and counts only, unless the client approves more.

Opportunities in HubSpot

Account management on real volumesHigh value

TEU, shipment counts, top lanes and revenue per client sit on the HubSpot company, so account managers see growth and decline as it happens.

Rate requests that reach operationsHigh value

A rate request from a HubSpot form or a sales rep goes to CargoWise as a quote request, and the quote status returns to the HubSpot deal.

Proactive service from milestonesHigh value

Delays and exceptions open HubSpot tickets for the account team, so the client hears from the forwarder first.

Lane-based cross-sellMedium value

Clients shipping a lane by sea can be offered air, customs or warehousing on the same lane, with HubSpot lists built from lane data.

Dormant client win-backMedium value

When a client's last shipment date passes a threshold, HubSpot starts a win-back sequence for the account owner.

Customs upsell for forwarding clientsNice to have

Forwarding clients with no customs entries become a target list for brokerage services.

Core customer journey

From rate request to repeat shipments.

The integration follows how a forwarder wins and grows a client. HubSpot handles the enquiry and the relationship, CargoWise runs the freight, and freight data drives the next conversation.

  1. Enquire: a rate request from the website or a sales rep is captured in HubSpot.
  2. Quote and book: the request reaches CargoWise as a quote, and quote and booking status return to the deal.
  3. Ship: XUE milestones and exceptions update the client record and open service tickets.
  4. Grow: lane volumes, TEU and revenue rollups drive account reviews, cross-sell and win-back.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the cw_ prefix in a CargoWise property group. Volumes and revenue are rolled up in the integration layer so every report agrees.

Internal nameLabelObjectTypeSource / logic
cw_org_codeCargoWise Organization CodeCompanySingle-line textOrganization code; unique
cw_org_rolesOrganization RolesCompanyMultiple checkboxesShipper, consignee, importer and other roles
cw_quote_numberCargoWise Quote NumberDealSingle-line textQuote reference
cw_job_numberJob NumberShipment (custom object)Single-line textShipment reference; unique
cw_modeTransport ModeShipment (custom object)DropdownSea, air, road, rail
cw_shipment_statusShipment StatusShipment (custom object)DropdownLatest milestone event
cw_etaETAShipment (custom object)DateLatest estimated arrival
cw_teu_12mTEU (12 months)CompanyNumberContainer rollup in integration layer
cw_shipments_12mShipments (12 months)CompanyNumberCount of shipments
cw_revenue_12mRevenue (12 months)CompanyNumber (currency)Invoiced revenue rollup
cw_top_lanesTop LanesCompanyMultiple checkboxesOrigin–destination pairs by volume
cw_last_shipment_dateLast ShipmentCompanyDateMost recent shipment
09 — Scope builder

Interactive scope builder

Choose the modules and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
10 — Sources

Sources & verification

Based on public documentation. eAdaptor message types, field paths and limits come from the developer guide WiseTech releases to licensed customers and are confirmed with the forwarder in the licensing and access phase.

CargoWise × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

CargoWise HubSpot integration FAQ

Does CargoWise integrate with HubSpot?

Yes, through eAdaptor, CargoWise’s integration interface. Its outbound service sends XML messages when workflow triggers or milestones fire, and its inbound service accepts XML to query, add and update records. Campaign Creators builds a custom integration on eAdaptor once the forwarder has it licensed and enabled.

What data syncs between CargoWise and HubSpot?

Client organizations sync to HubSpot companies and shipper and consignee contacts to contacts; quotes and bookings sync to deals; and shipments and consols sync to a Shipment custom object with milestones and customs events. Lane volumes and revenue totals are rolled up onto the company, and HubSpot rate requests travel back to CargoWise.

Which system owns which data?

CargoWise owns the job: shipments, customs declarations, charges and invoices are created and changed in CargoWise. HubSpot stores what sales and account management act on, such as shipment status, lane volumes and revenue totals, and runs website enquiries and campaigns. Record ownership is signed off before the build.

What does setting up the CargoWise HubSpot integration involve?

Seven phases, each closed by a client sign-off: licensing and access (eAdaptor enabled, with the developer guide and a test environment), message design, identity and ownership, the HubSpot data model, the build, backfill, and workflows with a two-week parallel run before launch.

How long does the integration take and what does it cost?

Timeline and cost depend on the messages, records and fields in scope (for example the forwarder’s eAdaptor licensing, the workflow triggers to set up and the rate request path back to CargoWise). Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.

Ready to Get More From HubSpot?

Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.