Skip to main content

Geotab 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 database's vehicles' positions from MyGeotab's LogRecord feed every minute, carrying on from the feed's position, so a fleet with Geotab devices is seen alongside its own trackers.

  • Regions: SA, AE, US, EU
  • Capabilities: integration.fleet.sync.telemetry.position

How to use it​

Not yet: see its status above.

Configuration​

SettingTypeRequiredAllowed values and default
geotab_databasestringyesThe MyGeotab database's name (as in the address bar after /)
geotab_usernamestringyesA MyGeotab user of the database for ZAITRACK (a service account that can view the vehicles and their trips)
geotab_serverstringnoLeave empty: my.geotab.com names the database's server itself
add_vehicles_automaticallybooleannodefault true; Each vehicle becomes one of the organisation's devices on its first position, unbound until you fit it to a vehicle. Off: positions 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.

  • geotab_password

Limits​

  • Memory: 256 MB
  • Time per call: 30,000 ms
  • Largest message: 1,048,576 bytes
  • Calls at once: 16
  • Network: only my.geotab.com, *.geotab.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/geotab