Requirements
Prepare the provider account, permissions, and camera access before opening the integration in GuardDog.
Credentials
API token
RequiredA Samsara API token belonging to the fleet organization with the required organization, vehicle, webhook, alert, and media-retrieval scopes.
Provider account checklist
- A Samsara administrator who can create or edit API tokens.
- An API token with Read Org Information, Read Vehicles, Read Webhooks, Write Webhooks, Read Alerts, Write Alerts, Read Media Retrieval, and Write Media Retrieval.
- At least one vehicle with an active road-facing or dual-facing Samsara dash cam.
Capabilities
Device discovery
Supported
Sync vehicles with VIN, serial, and fleet metadata for unit assignment.
Safety events
Supported
Automatically subscribe all vehicles and supported safety behaviors to signed, enriched Webhooks 2.0 delivery.
Incident video
Supported
Request road- and driver-facing clips through asynchronous media retrieval.
Live video
Not available
The current GuardDog Samsara integration does not start live camera sessions.
Setup guide
- 1
Create the API token
In Samsara, create a dedicated token and grant the required organization, vehicle, webhook, alert, and media-retrieval permissions.
- 2
Connect Samsara in GuardDog
Open Integrations, choose Samsara, paste the token, and test the connection.
- 3
Save the integration
GuardDog binds the token’s Samsara organization and creates or reconciles both a signed Webhooks 2.0 endpoint and its organization-wide safety alert.
- 4
Discover and assign vehicles
Run device discovery, then assign each Samsara vehicle to the matching GuardDog unit.
- 5
Verify an event and its media
Trigger a controlled safety alert or use a recent demo event. Confirm signed delivery, unit matching, and road/cabin clip retrieval.
Provider configuration
- GuardDog owns one dedicated Samsara safety alert covering all vehicles and supported safety behaviors. Existing customer alerts are not changed.
- The API token resolves to one Samsara organization. GuardDog locks that organization binding after the first successful connection.
- Incident media is asynchronous. A clip can remain pending while Samsara prepares and uploads it.
- Keep the Read and Write Webhooks and Alerts permissions enabled so GuardDog can safely reconcile its endpoint, signing-key state, and alert configuration.
Verify the integration
Complete each check before enabling the provider for production alerting.
- CheckThe token passes the GuardDog connection test.
- CheckThe integration reports an active signed webhook and safety-event alert.
- CheckDevice discovery lists the expected vehicles, VINs, and camera serials.
- CheckA Samsara safety event creates an event under the correct unit.
- CheckRoad- and driver-facing clips move from pending to available when supported by the camera.
Before generating a test event: verify the GuardDog organization, branch, contacts, call settings, and provider demo account. A real event can start texts and paid calls when alerting is enabled.
Troubleshooting
The organization cannot be resolved+
Add Read Org Information to the API token and confirm the token belongs to the intended Samsara organization.
Automatic event setup fails+
Grant Read Webhooks, Write Webhooks, Read Alerts, and Write Alerts, then retry automatic webhook setup.
The webhook is active but no events arrive+
Retry automatic webhook setup and confirm the GuardDog Safety Events alert is enabled in Samsara Settings → Alerts.
Incident video stays unavailable+
Confirm both media-retrieval permissions, camera availability for the event time, and the organization’s media-retrieval quota.