How TrackFlo Connects to Your TMS
Updated today
TrackFlo integrates with your TMS in two directions. Inbound, it keeps a live copy of your loads, legs and stops so trackers and automations can work from current data. Outbound, it writes what your team does in TrackFlo back to the TMS: status changes, check-call notes, stop arrivals and departures, driver and tracking details, and proof-of-delivery documents.
How each half works depends on the TMS. Some push events to TrackFlo as they happen, some are polled, and one is read from a database replica. Pick your system for the specifics, including what your TMS administrator needs to grant or configure before the first load can sync.
TMS | Inbound | Outbound |
|---|---|---|
Webhooks + scheduled polls | Status, notes, stop times, driver & tracking, POD | |
Scheduled polls, optional RapidAlerts webhooks | Status, call-ins, stop times, driver, POD | |
Event stream + REST reads | Status, notes, stop times, driver & tracking, POD | |
Webhooks + reconciliation poll | Status, stop times, tracking | |
Scheduled Salesforce queries, optional webhook | Status, notes, stop times | |
Database replica read by TrackFlo middleware | Dispatch, notes, stop times |
Every integration is scoped to one TrackFlo tenant. Credentials you hand us are stored in a managed secret store, never in code, and are used only for your tenant's connection.