Integrations Overview
Connect StarShipper to your existing systems and workflows
Showing every variant, each marked with the profiles it applies to.
Overview
StarShipper integrations let you automatically deliver extracted document data to your other business systems. All integrations are managed from the Integrations page in the sidebar, where you can add connections, configure routing rules, and monitor delivery activity.
How it works: When a document is processed and approved (automatically or manually), StarShipper checks your active integrations and routing rules, then dispatches the extracted data to all matching destinations. Delivery status is tracked in the activity log.
Integration Types
Seven delivery destinations, plus one download-only export
CargoWiseTMS
Push extracted data directly to your CargoWise One instance via the eAdaptor API. Document data is automatically mapped to CargoWise Universal XML format to create or update forwarding shipments, consols, and warehouse orders.
When to use it: Use this if you run CargoWise and want documents to flow straight in without manual data entry. Upload a document, StarShipper reads it, and the shipment appears (or updates) in CargoWise.
CargoWise matches on business keys: house bill number, master bill number, or booking number. If it finds an existing shipment it updates that one; if not, it creates a new one. No placeholder keys, and no duplicate jobs.
Custom WebhooksAPI
Send extracted data as JSON payloads to any HTTP endpoint. Perfect for connecting to CRMs, ERPs, accounting software, or custom applications. Supports field mapping to rename fields to match your system's expected format.
When to use it: Use this when you want to connect to a system that is not one of the named destinations below. If it has an API or accepts webhooks, this is the one.
Field mappings remap the payload before it is sent. If the receiving system expects "house_bill" where StarShipper sends "hblNumber", set that up on the route and the translation is handled for you.
Google SheetsSpreadsheet
Keep one row per shipment in a Google Sheet, with columns created automatically for each field. Sending the same shipment again updates its row in place. Useful for reporting and for sharing with people who will not log in.
When to use it: Use this for reporting, for sharing data with people who do not use StarShipper, for building dashboards, or for keeping a simple audit trail that anyone can open in a browser.
Requires a one-time Google sign-in. Pick an existing spreadsheet or create a new one. If a shipment has already been sent, its row updates in place — matched by reference number — rather than a duplicate being appended.
ExpedientTMS
Send a forwarding manifest CSV to your Expedient intake address, so jobs land in the incumbent system without rekeying.
When to use it: Use this if you run Expedient and want shipment data to flow in automatically. Upload your documents, StarShipper extracts the data, and the CSV arrives in Expedient by email.
Expedient takes EDI intake by email rather than through a public API, so StarShipper sends the CSV as an attachment to the intake address you configure. One row per container and line-item combination, with the shipment-level fields repeated on each row.
XeroAccounting
Push extracted invoice data into Xero as purchase bills over OAuth 2.0, so the finance side of a job does not get typed twice.
When to use it: Use this if you run Xero for accounting and want invoice data to arrive as purchase bills without re-keying supplier names, amounts and due dates.
Requires a one-time Xero sign-in. StarShipper reads invoice amounts, payment terms (Net 14, Net 30 and so on) and supplier names from your extracted documents. Duplicate invoices are detected — if one has already been sent, the second attempt is skipped rather than billed twice.
SAPERP
Export shipment data as a CSV emailed for SAP import, for teams whose ERP is the system of record.
When to use it: Use this if your organisation runs SAP and imports data through email-based CSV intake.
Third Party EmailCSV
Email a NEW JOB CSV to any nominated address. Each connection picks which columns it sends, so a customs agent and a transport provider can receive different views of the same job.
When to use it: Use this to give someone outside StarShipper — a customs agent, a transport provider, an overseas partner — the job data they need, without giving them a login.
TradeWindowDownload only
Download shipment data as CSV formatted for TradeWindow import, in either SpeEDI Cargo format (for ABF cargo reporting) or TW Freight Manifest format (for job creation). TradeWindow cannot be configured as an automatic delivery route. You take the download yourself whenever you need it.
When to use it: Use this if you lodge customs declarations through TradeWindow and want shipment data in the CSV format it expects.
Comparison
Choose the right destination for your use case
| Destination | Format | Scope | Authentication | Best for | Offered to |
|---|---|---|---|---|---|
| CargoWise | Universal XML over eAdaptor | Whole shipment | SOAP Basic Auth | Forwarders and brokers on CargoWise One | All profiles |
| Expedient | Forwarding manifest CSV | Whole shipment | Emailed to intake address | Teams still running Expedient | Customs broker, Freight forwarder, Freight forwarder & customs broker and Transport / 3PL |
| Xero | Purchase bills | Whole shipment | OAuth 2.0 | Pushing supplier invoices into accounts | All profiles |
| Google Sheets | Spreadsheet rows | Whole shipment | OAuth 2.0 (Google) | Reporting and sharing with non-technical people | All profiles |
| SAP | CSV export | Whole shipment | Emailed for import | Teams whose ERP is the system of record | Customs broker, Freight forwarder, Freight forwarder & customs broker and Transport / 3PL |
| Third Party Email | NEW JOB CSV | Whole shipment | Emailed to any address | Sending a job to an agent or subcontractor | Customs broker, Freight forwarder, Freight forwarder & customs broker and Transport / 3PL |
| Webhook | JSON | Whole shipment or per doc type | Bearer, Basic, API key | Custom systems and APIs | All profiles |
| TradeWindow | SpeEDI / TW Freight CSV | Download only | None (manual download) | ABF cargo reporting | All profiles |
Most destinations send one indivisible artefact per shipment, so they always cover the whole shipment and have no per-doc-type selector. Webhooks are the exception, where routing a particular document type to a particular endpoint is a genuine feature.
Which of these you are offered depends on your industry profile. Expedient, SAP and Third Party Email build a forwarding manifest or a cartage instruction, so they are offered to customs brokers and freight forwarders rather than to shipping agencies.
Managing Integrations
Monitor and manage your connections
Connections Page
View all your configured integrations at Integrations > Connections. From here you can add new connections, test existing ones, enable/disable them, and configure routing rules.
Activity Log
Each delivery attempt is logged at Integrations > Activity. See delivery timestamps, response status, error messages, and which documents were sent to which integrations. Filter by status, integration type, and date range.
Testing Connections
Each integration has a "Test" button that sends a test request to verify the connection is working. This is useful after initial setup or when troubleshooting delivery failures.