Cargoson
Cargoson is a freight and logistics management platform that helps businesses streamline shipping, compare carrier rates, track shipments, and manage transportation workflows.
Prerequisites
To sync Bookings from Cargoson, you need a table or model in your destination that contains the booking references you want to sync, attached to the Cargoson connector as a source.
Supported Features
| Feature name | Supported | |
|---|---|---|
| Column Hashing | False | |
| Blocking | False | |
| Incremental | True | |
| Custom data | False | |
| History | False | |
| ReSync | True | Table level |
| Templates | True |
Data Schema
Syncing Bookings
Unlike Cargoson's other objects, Bookings can't be synced from a fixed endpoint — the Cargoson API requires the unique booking references of the bookings you want to fetch. Because of this, syncing Bookings requires an extra setup step:
- In your destination, prepare a table or model containing the unique booking references you want Weld to sync. This is typically a table you already sync or transform from another source, such as an order or shipment system that stores your Cargoson booking references.
- In the Cargoson connector setup, attach this table/model as a source under the Bookings table configuration and pick the column with the booking references.
- Optionally, pick an alias column if your Cargoson account has more than one company. See Multiple companies in Cargoson below.
- Weld will use the booking references from the attached table/model to call the Cargoson API and sync the corresponding booking data.
Without an attached table/model containing the booking references, Weld has no way to know which bookings exist in Cargoson, so the Bookings table can't be synced.
Multiple companies in Cargoson
A single Cargoson account can hold more than one company. Each company is identified by an alias in Cargoson, and a booking reference is only valid within the company it belongs to. If your account has more than one company and the request does not tell Cargoson which company the booking belongs to, the request to Cargoson fails.
If your Cargoson account only has one company, you can skip this section — the alias column is optional and Weld looks up each booking without an alias. Weld still only fetches the bookings whose references are in the attached table/model; it does not discover bookings on its own.
If your account has more than one company:
- Add a column to the table/model with the booking references that holds the Cargoson alias of the company each booking belongs to. The alias is the value Cargoson shows for the company under your account settings.
- In the Cargoson connector setup, select that column as the Alias column under the Bookings table configuration. The dropdown lists the columns of the table/model you attached.
- For every booking reference, Weld sends the alias from that row along with the request, so Cargoson resolves the booking within the right company.
| Column in your table/model | Required | What Weld does with it |
|---|---|---|
| Booking reference column | Yes | Used as the booking id or reference to fetch from the Cargoson API. |
| Alias column | No | Sent as the Cargoson company alias for that booking. Required for every row when your account has more than one company. |
The alias column must be in the same table/model as the booking references, so that each row pairs a booking reference with the company it belongs to.