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.
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.
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.
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.
Organizations, shipments, consols, customs declarations and accounting all live in CargoWise, so one interface supplies everything an account manager needs.
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.
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.
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.
CargoWise sends a message to a service CC hosts whenever a configured workflow trigger or milestone fires on a record.
The full record behind a message: forwarding shipments, consols, customs declarations and their parties, routing, containers and charges.
A small message with the record identifier and the event or milestone that triggered it.
Accepts Universal XML or Native XML to query CargoWise records or to add and update them.
WiseTech's newer connectivity option, which replaces SOAP for inbound and outbound communication with modern security.
Organization records and accounting transactions, used for client master data and revenue per client.
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.
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.
Shipments, customs declarations, charges and invoices are created and changed in CargoWise. HubSpot stores what sales and account management act on.
HubSpot keeps shipment status, lane volumes and revenue totals. Full documents, charges and customs data stay in CargoWise, referenced by job number.
The CargoWise organization code is stored on the HubSpot company and used by every message, so a client never appears twice.
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.
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.
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.
Agree the match rules (organization code first, then domain and name) and which system owns clients, contacts, opportunities and quotes.
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.
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.
Load client organizations and an agreed window of shipment history through eAdaptor Inbound, then compute lane and revenue rollups once.
Build account health, lane growth and service alert workflows with emails paused, run two weeks in parallel, then switch on.
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 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Clients · organizations & contacts | ||||
| Organization code | cw_org_code | Company | CW → HS | Primary match key. Unique. |
| Organization name | name | Company | ↔ Both | Fill blanks; HubSpot edits stay in HubSpot. |
| Organization address and country | address, city, country | Company | CW → HS | |
| Organization role (shipper, consignee, importer) | cw_org_roles | Company | CW → HS | Multi-select. Confirm role values in discovery. |
| Organization contacts | firstname, lastname, email, phone | Contact | CW → HS | Associated to the company. |
| Sales rep on the organization | hubspot_owner_id | Company | CW → HS | Mapped to HubSpot users. |
| Quotes & bookings | ||||
| HubSpot rate request form | Quote request in CargoWise | Deal | HS → CW | Origin, destination, mode, commodity, volume. Confirm the inbound message type in discovery. |
| Quote number | cw_quote_number | Deal | CW → HS | Links the deal to the CargoWise quote. |
| Quote status | Deal stage | Deal | CW → HS | Quoted, accepted or declined mapped to the quote pipeline. |
| Booking created from quote | Deal stage: Booked | Deal | CW → HS | From the booking trigger. |
| Shipment / job number | cw_job_number | Shipment (custom object) | CW → HS | Unique per shipment. |
| Shipments, consols & milestones | ||||
| Transport mode | cw_mode | Shipment (custom object) | CW → HS | Sea, air, road, rail. |
| Origin and destination | cw_origin, cw_destination | Shipment (custom object) | CW → HS | Port or location codes. |
| ETD / ETA | cw_etd, cw_eta | Shipment (custom object) | CW → HS | Updated on each event. |
| Milestone event (XUE) | Custom event: Shipment milestone | Company | CW → HS | Booked, departed, arrived, delivered. |
| Latest milestone | cw_shipment_status | Shipment (custom object) | CW → HS | |
| Consol reference | cw_consol_number | Shipment (custom object) | CW → HS | Groups shipments on one consolidation. |
| Exception or delay event | Ticket | Ticket | CW → HS | Opens a service ticket for the account team. |
| Lanes, volumes & revenue | ||||
| Container count and size | cw_teu_12m | Company | CW → HS | TEU rolled up in the integration layer. |
| Shipments per client | cw_shipments_12m | Company | CW → HS | Rolling 12-month count. |
| Top lanes | cw_top_lanes | Company | CW → HS | Origin–destination pairs by volume. |
| Invoiced revenue (Universal Transaction) | cw_revenue_12m | Company | CW → HS | Confirm accounting message and currency handling. |
| Last shipment date | cw_last_shipment_date | Company | CW → HS | Drives dormant-client workflows. |
| Customs | ||||
| Customs declaration events | Custom event: Customs milestone | Company | CW → HS | Lodged, cleared, held. |
| Declarations per client | cw_customs_entries_12m | Company | CW → HS | Rolled up in the integration layer. |
WiseTech gates eAdaptor by licence; HubSpot uses one app token. Values WiseTech does not publish are marked for confirmation.
| Topic | CargoWise | HubSpot |
|---|---|---|
| Access model | eAdaptor 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. |
| Interfaces | eAdaptor 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. |
| Authentication | Legacy 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 formats | Universal XML (UniversalShipment, UniversalEvent, UniversalTransaction in a UniversalInterchange envelope) and Native XML. | JSON. |
| Triggers | Workflow 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 limits | Not published. Confirm with WiseTech. | Per-10-second burst and daily limits by subscription tier. |
| Monitoring | Sent messages and their status appear in CargoWise EDI Interchange. | Integration layer logs every message and replays failures. |
Severity reflects impact on the SOW, not technical difficulty alone.
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.
Outbound messages exist only for configured triggers. The forwarder's CargoWise administrator configures and tests them with CC during message design.
CargoWise includes CRM tools and HubSpot holds the commercial relationship. A signed ownership matrix decides which system owns opportunities, enquiries and contacts.
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.
Busy forwarders send many events a day. HubSpot stores shipment status and rollups; full documents and charges stay in CargoWise.
Customs declarations carry tariff and value details. HubSpot receives events and counts only, unless the client approves more.
TEU, shipment counts, top lanes and revenue per client sit on the HubSpot company, so account managers see growth and decline as it happens.
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.
Delays and exceptions open HubSpot tickets for the account team, so the client hears from the forwarder first.
Clients shipping a lane by sea can be offered air, customs or warehousing on the same lane, with HubSpot lists built from lane data.
When a client's last shipment date passes a threshold, HubSpot starts a win-back sequence for the account owner.
Forwarding clients with no customs entries become a target list for brokerage services.
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.
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 name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| cw_org_code | CargoWise Organization Code | Company | Single-line text | Organization code; unique |
| cw_org_roles | Organization Roles | Company | Multiple checkboxes | Shipper, consignee, importer and other roles |
| cw_quote_number | CargoWise Quote Number | Deal | Single-line text | Quote reference |
| cw_job_number | Job Number | Shipment (custom object) | Single-line text | Shipment reference; unique |
| cw_mode | Transport Mode | Shipment (custom object) | Dropdown | Sea, air, road, rail |
| cw_shipment_status | Shipment Status | Shipment (custom object) | Dropdown | Latest milestone event |
| cw_eta | ETA | Shipment (custom object) | Date | Latest estimated arrival |
| cw_teu_12m | TEU (12 months) | Company | Number | Container rollup in integration layer |
| cw_shipments_12m | Shipments (12 months) | Company | Number | Count of shipments |
| cw_revenue_12m | Revenue (12 months) | Company | Number (currency) | Invoiced revenue rollup |
| cw_top_lanes | Top Lanes | Company | Multiple checkboxes | Origin–destination pairs by volume |
| cw_last_shipment_date | Last Shipment | Company | Date | Most recent shipment |
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.
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.
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.
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.
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.
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.
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.