Connect n8n, Make or Zapier

Before you start

These examples use each tool’s custom HTTP capabilities. Create an owner-issued key with the minimum scopes your workflow needs. Save it in the tool’s private credential store.

Persist the source request ID before sending so retries keep the same Idempotency-Key. Keep the external reference and returned HaulMatch ID on your source record.

• API credentials and retry rules

n8n

1. Download and import the create-load workflow.
2. Set the configured gateway base URL and a Header Auth credential containing Authorization: Bearer hm_org_....
3. Map the preceding node’s requestId, externalRef and data. Keep the source requestId unchanged across retries.
4. For return events, place a signature-verifying endpoint in front of the n8n Webhook node and preserve the raw body during verification.

• Download n8n create-load workflow

Make

1. Trigger the scenario from a form, CRM, database or parsed CSV row.
2. Use the HTTP request module to POST to https://YOUR_GATEWAY/api/integrations/v1/loads.
3. Configure private Authorization credentials, Content-Type: application/json and Idempotency-Key from the persisted source request ID.
4. Map the request body below and store the response ID on the source record. Retry transient failures with the same key; inspect 409 conflicts.

Zapier

1. Use a custom request through Webhooks by Zapier with the same load URL, headers and JSON payload.
2. Keep the credential private to the workflow. Persist a source UUID before sending and use it as Idempotency-Key.
3. Store the returned load ID. Put a signature verifier in front of a Catch Hook when consuming HaulMatch events.

Load request body

A fleet workflow uses POST /quotes with quotes:write, an explicit payoutMode, driverId for DRIVER pay, and data containing jobId, amount and message. COMPANY pay keeps the fleet as payee and requires an operating driver before transit.

{
  "externalRef": "TMS-LOAD-1001",
  "data": {
    "itemName": "Pallet shipment",
    "loadType": "Pallets",
    "readiness": "READY_NOW",
    "pickupLocation": "Melbourne VIC",
    "dropoffLocation": "Sydney NSW",
    "loadWeight": 1200,
    "details": "Tail lift required; collect 09:00–12:00"
  }
}

• Fleet quoting and dispatch
• Verify incoming events

Other transport systems

A custom partner adapter can map its fields and request IDs into the REST and event contract. MachShip and TransVirtual adapters are available in preview through company TMS settings. CargoWise and MyTrucking require vendor specifications before activation; Oracle, SAP, SFTP and EDI adapters remain future options.