Umami
Reads traffic, referrer, campaign, and conversion metrics from a self-hosted Umami instance so agents can report on a site without third-party trackers.
What it provides
Connect an existing HTTPS deployment with an optional scoped token. Heavy jobs stay on that service instead of using bot memory.
Connection requirements
A self-hosted Umami deployment. Umami reads a bearer token from the Authorization header, and POST /api/auth/login returns one for a self-hosted instance. Keep Bearer selected and paste that token below. Website IDs come from the Umami dashboard URL.
- Protocol
- REST / OpenAPI
- Endpoint
https://umami.example.com- Authentication
- bearer
Where to add it
Open Dashboard Tools, select a running OpenClaw or Hermes instance, then use the card’s Install or Connect action. External services may require an HTTPS endpoint and credentials; the dashboard shows those fields before anything is saved.