Samsara integration
Connect Samsara to Demurly, read-only
Early access for Pro carriers: connect your Samsara account so Demurly can read your trucks. Next, the truck's GPS opens and closes demurrage waits.
Pro carriers ($199 a month), early access
What it does
For carriers
- An admin signs in to Samsara and allows Demurly to read the fleet. Demurly never changes anything in Samsara.
- Demurly checks the connection and shows what it can read, for example how many vehicles it found.
- Next: the truck's own GPS opens and closes waits at terminals and customer sites, with no Demurly app on the driver's phone.
How it works
- 1An admin opens Settings > Connected systems > Trucks (ELD) and clicks Connect on the Samsara card.
- 2Samsara shows the read-only permissions Demurly asks for; allow them and you come back to Demurly, connected.
- 3Disconnect removes Demurly's access, at Samsara too; your records aren't changed.
Not supported
- Waits opened and closed by the truck's GPS (coming next)
- Writing to Samsara: the connection is read-only
Questions
- Can the truck open demurrage records by itself yet?
- Not yet. Today the connection is made and checked; truck-opened waits come next. Until then, send waits the way you do now, by the driver app, EDI or the API.
- Which permissions and redirect URIs does Demurly use?
- The setup guide lists them: every permission is read-only, and the redirect URIs are on demurly.com.
- We use Motive. Is that supported?
- Yes, Samsara and Motive both connect the same way, in early access.
Other integrations
QuickBooks Online
Invoices for carriers, bills for fuel buyers, payments both ways.
NetSuite
Invoices for carriers, vendor bills for fuel buyers, payments both ways.
SAP Business One
A/R invoices for carriers, A/P invoices or drafts for fuel buyers.
PDI Enterprise
Import files for approved charges, and payment registers back.
Motive
Early access: read-only fleet connection; truck-opened waits next.
EDI
214s open and close waits; 210s go out for approved charges.
API and webhooks
REST API, signed webhooks, test mode and an MCP server.