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, and media-retrieval scopes.
Provider account checklist
- A Samsara administrator who can create or edit API tokens and safety alerts.
- An API token with Read Org Information, Read Vehicles, Read Webhooks, Write Webhooks, Read Media Retrieval, and Write Media Retrieval.
- At least one vehicle with an active road-facing or dual-facing Samsara dash cam.
- Safety alerts configured to deliver to the GuardDog webhook after the endpoint is created.
Capabilities
Device discovery
Supported
Sync vehicles with VIN, serial, and fleet metadata for unit assignment.
Safety events
Supported
Verify signed Webhooks 2.0 deliveries from selected Samsara safety alerts.
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 six required organization, vehicle, webhook, 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 a signed Webhooks 2.0 endpoint.
- 4
Associate safety alerts
In Samsara Dashboard, open Settings → Alerts and configure each individual safety alert you want GuardDog to receive to send to the GuardDog webhook.
- 5
Discover and assign vehicles
Run device discovery, then assign each Samsara vehicle to the matching GuardDog unit.
- 6
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
- Creating the webhook endpoint does not automatically subscribe it to Samsara alerts. Each desired safety alert must be associated with the endpoint in Samsara.
- 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 Read Webhooks permission enabled so GuardDog can safely reconcile an existing endpoint and its signing-key state.
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.
- CheckDevice discovery lists the expected vehicles, VINs, and camera serials.
- CheckA selected Samsara safety alert 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.
Webhook creation or updates fail+
Grant both Read Webhooks and Write Webhooks, then test and save the integration again.
The webhook is active but no events arrive+
Associate each desired individual safety alert with the GuardDog endpoint 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.