GuardDog
DocumentationIntegrationsGeotab
MyGeotab service-account credentialsManual webhook setup

MyGeotab and Geotab Video

Connect Geotab to GuardDog

GuardDog authenticates a dedicated MyGeotab service account, binds one database, discovers devices, accepts Web Request notifications from selected rules, enriches events, and resolves Geotab Video or GO Focus media.

Open GuardDog integrationsMyGeotab rule notifications
On this page

Requirements

Prepare the provider account, permissions, and camera access before opening the integration in GuardDog.

Credentials

Database

Required

The MyGeotab database name shown in the fleet’s MyGeotab URL.

Username

Required

A dedicated MyGeotab service-account user with API, device, exception-event, and video permissions.

Password

Required

The password for the service-account user.

Server

Optional

Only required for a federated MyGeotab server. GuardDog otherwise follows the authentication redirect automatically.

Geotab Video API key

Optional

Optional SAI-Key fallback for fleets that require API-key access to GO Focus video.

Provider account checklist

  • A dedicated MyGeotab service account with API access to the intended database.
  • Read access to Devices and ExceptionEvents, plus permission to view/request Geotab Video or GO Focus clips and live video.
  • Permission to create a Web Request notification template and attach it to safety rules.
  • At least one device and supported camera assigned to the same MyGeotab asset.

Capabilities

Device discovery

Supported

Sync MyGeotab devices and match callbacks by device ID, serial number, VIN, and display name.

Safety events

Manual setup

Deliver selected rule exceptions through a MyGeotab Web Request notification.

Incident video

Supported

Resolve or request road- and cab-facing Geotab Video/GO Focus clips.

Live video

Supported

Open authenticated road- and cab-facing Geotab Video player sessions.

Setup guide

  1. 1

    Create the MyGeotab service account

    Create a dedicated user with API access and only the device, exception-event, notification-template, and video permissions required for GuardDog.

  2. 2

    Connect Geotab in GuardDog

    Enter the database, username, password, optional federated server, and optional Geotab Video API key. Test and save the connection.

  3. 3

    Discover and assign devices

    Run device discovery and assign each MyGeotab device/camera to the corresponding GuardDog unit.

  4. 4

    Copy the tenant webhook URL

    Copy the Geotab callback URL from the saved GuardDog integration. The URL contains the organization binding and must be copied exactly.

  5. 5

    Create the Web Request template

    In MyGeotab, go to Groups & Rules → Notification Templates → Web. Create a POST template using the GuardDog URL and JSON body below.

  6. 6

    Attach the template to safety rules

    For each rule that should create a GuardDog incident, add the Web Request template as a notification recipient.

  7. 7

    Verify events and video

    Trigger one controlled rule, confirm device matching and event context, then verify recorded and live video on the assigned unit.

Provider configuration

  • The database is the immutable tenant boundary. If the fleet moves databases, contact GuardDog support before changing the integration.
  • Rule names are normalized into GuardDog categories. Clear names such as Collision Detected, Seatbelt Violation, Distracted Driving, Speeding, Harsh Braking, and Lane Departure produce the best classification.
  • Attach the Web Request template only to rules that should create GuardDog incidents.
  • The service account must be able to see the same devices and camera/video records referenced by the notification.

Web Request JSON body

Use POST and application/json. Keep the MyGeotab tokens intact so GuardDog can match the device, classify the rule, and enrich the event.

{
  "event_id":      "{Exception Id}",
  "device_id":     "{Device ID}",
  "device_serial": "{Serial number}",
  "device_name":   "{Device name}",
  "device_label":  "{Device}",
  "vin":           "{Vin}",
  "rule_name":     "{Rule}",
  "occurred_date": "{Date}",
  "occurred_time": "{Time}",
  "latitude":      "{Latitude}",
  "longitude":     "{Longitude}",
  "speed":         "{Speed}",
  "driver_name":   "{Driver Name}"
}

Verify the integration

Complete each check before enabling the provider for production alerting.

  • CheckThe service account authenticates to the intended database.
  • CheckDevice discovery lists the expected assets, serial numbers, and VINs.
  • CheckA selected rule sends a successful Web Request delivery.
  • CheckThe resulting event maps to the correct unit and includes rule/time/location context.
  • CheckRecorded clips resolve or enter a pending request state, and available live feeds start and stop.

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

Authentication redirects or fails+

Confirm the database and credentials. For federated environments, add the correct server; otherwise allow GuardDog to follow MyGeotab’s returned server.

Events arrive without a matching unit+

Include Device ID, Serial number, VIN, and Device in the template, then confirm the discovered device is assigned to the GuardDog unit.

A rule never creates an event+

Confirm the Web Request template is attached to that exact rule and review its delivery status in MyGeotab and GuardDog.

Video is unavailable+

Confirm the service account has video permissions and the camera is associated with the same asset. Add the optional Geotab Video API key when the tenant requires it.