Connected systems, clear boundaries
Our integrations program starts with reliable identity and fleet data, then expands into accounting, load sourcing, fuel, and partner data exchange. Every connector must show what moves, in which direction, when it last worked, and what needs attention.
Telematics & ELD
We are hardening the existing Motive connection around secure tenant credentials, observable runs, and a controlled driver import before offering it as a production connection.
Initial data direction: Planned first direction: Motive to TMS Software
Provider dependency: A supported Motive credential and access to the required Motive API scope
Release boundary: The current build is undergoing provider-account validation and is not marketed as generally available. Expanded fleet and dispatch context stays behind separate release gates.
Integration roadmap
These are planned priorities, not claims of availability, partnership, or a committed delivery date. Provider access and customer demand influence the sequence.
Accounting
Reduce manual accounting handoff for invoices and recorded payments while preserving reconciliation state.
Direct connection is not available today. Provider-neutral accounting CSV exports remain available.
Telematics & ELD
Bring supported vehicle, driver, location, and readiness context into dispatch through a reusable telematics adapter.
Scope depends on provider access, customer permissions, and official API capabilities.
Telematics
Extend provider choice for equipment identity, fleet position, and operational context.
Scope depends on provider access and will reuse the telematics integration foundation.
Loads & rates
Evaluate supported load-search, posting, and rate workflows without forcing dispatchers to rebuild load information.
No direct connection or provider partnership is claimed. Delivery requires API access and applicable commercial agreements.
Loads & rates
Evaluate load and rate workflows as a second provider option for carrier teams.
No direct connection or provider partnership is claimed. Delivery requires API access and applicable commercial agreements.
Fuel & expenses
Import fuel transactions and connect them to drivers, equipment, shipments, and accounting records.
The initial provider will be selected from customer demand and verified API access.
Data exchange
Exchange load, status, document, and billing events with customer and partner systems using observable delivery controls.
Public partner credentials, webhooks, and EDI exchange are not available today.
Help set the factory order
Tell us the provider, workflow, expected data direction, and volume. That evidence helps us prioritize a durable connector over a logo checklist.