MyGeotab

Reads raw fleet data from the MyGeotab API: trips, log records, status data, exceptions, devices, drivers, and more. Each entity type becomes a dataset.

Add a source

Enter the server and database

Server: my.geotab.com. You are redirected to your regional server automatically.
Database: your MyGeotab account (database) name.

Enter credentials

Username: your MyGeotab user, usually an email.
Password.

MyGeotab uses session authentication. Flitch signs in, then reuses the session for subsequent reads.

Pick an entity type

Add a dataset and choose the entity type (for example Trip, LogRecord, StatusData, Device, Driver).

Set the window (time-series types)

For time-series types like Trip or LogRecord, set:

History (days): how far back to load.
Max rows: a cap on the result size.

Reference types (for example Device, Driver) load all records up to Max rows.

Refresh

Refresh is set per dataset, in the dataset's Edit connection dialog. See Refresh.

Time-series types refresh incrementally: only records newer than the last load are fetched and merged into the cache, so a scheduled refresh stays cheap as history grows. Reference types refresh on a slower cadence by default.

The MyGeotab API enforces a per-minute request quota. Flitch reuses one session per connection and backs off on rate-limit responses rather than disabling the source. If a refresh is throttled it retries on the next scheduled run.

Troubleshooting

Authentication failed. Check the database name, username, and password. The database is the MyGeotab account name, not the server.

Service temporarily unavailable. A transient MyGeotab response, often during high load or a rate-limit window. The next scheduled refresh retries; cached data keeps serving meanwhile.

Fewer rows than expected for a time-series type. Increase History (days) or Max rows in the dataset's Edit connection dialog.