Build a custom MyGeotab Add-In using the Geotab SDK to embed a UI page inside the MyGeotab portal.
domain: developers.geotab.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Scaffold an Add-In project (HTML/CSS/JavaScript) with a configuration.json manifest per the Geotab SDK's Add-In structure.
Use the injected MyGeotab API object inside the Add-In to call standard Get/Add/Set methods against the logged-in database.
Register the Add-In in MyGeotab under System Settings > Add-Ins, pointing to your hosted files or a local dev URL during testing.
Combine MyGeotab data calls with your own backend APIs to build a full 'custom page' Add-In rather than a simple button Add-In.
Package and submit the Add-In to the Geotab Marketplace if distributing it beyond a single database.
Known gotchas
Add-Ins run inside an iframe scoped to the MyGeotab session, so calls to arbitrary external APIs may need a CORS-enabled backend proxy you control.
Local development typically requires serving the Add-In from https://localhost with a self-signed certificate, which triggers browser security warnings if misconfigured.
Add-In JavaScript errors can fail silently inside the MyGeotab shell — use the browser console/network tab rather than the Add-In UI to debug.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?