Skip to main content

Samsara Connector

Status: In development: its code is written and tested on its own, but it does not work end to end on the platform yet. It cannot be installed.

KindVersionPublisherLicence
Connector1.0.0ZAITRACKApache-2.0

What it does​

Reads the account's vehicles' positions, odometers and fuel levels from Samsara's stats feed every minute, carrying on from the feed's position, so a fleet with Samsara gateways is seen alongside its own trackers.

  • Regions: US, EU, CA
  • Capabilities: integration.fleet.sync.telemetry.position, integration.fleet.sync.telemetry.odometer, integration.fleet.sync.telemetry.fuel

How to use it​

Not yet: see its status above.

Configuration​

SettingTypeRequiredAllowed values and default
samsara_regionstringnoone of us, eu, ca; default "us"; Where the Samsara account is: us (api.samsara.com), eu, ca
add_vehicles_automaticallybooleannodefault true; Each vehicle becomes one of the organisation's devices on its first reading (a position, an odometer or a fuel level), unbound until you fit it to a vehicle. Off: readings of vehicles that are not yet devices are dropped and counted in the installation's health

Credentials​

Each is a secret setting of the installation: kept sealed (OpenBao in production), never shown again; Adapter Studio shows it as set.

  • samsara_api_token

Limits​

  • Memory: 256 MB
  • Time per call: 30,000 ms
  • Largest message: 1,048,576 bytes
  • Calls at once: 16
  • Network: only api.samsara.com, api.eu.samsara.com, api.ca.samsara.com

Troubleshooting​

  • Credentials refused. The secret settings must be the ones the provider issued for this account and environment (sandbox or live); give them again in Adapter Studio, since they are never shown back.
  • Rate limited. The provider's limit applies to the account: calls are retried with a growing pause; spread scheduled work or ask the provider for a higher limit.
  • Nothing is sent or synced. The installation must be active, its version approved; it reaches only the hosts listed under Limits.
  • Webhooks rejected. The webhook secret must match the one configured at the provider; a request whose signature does not match is refused.

Source​

adapters/connectors/samsara