Short answer: You can get website stats in Umami by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Umami Get Website Stats action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Website ID websiteId | string | Required | Website ID |
Start (epoch ms) startAt | number | Required | Start (epoch ms) |
End (epoch ms) endAt | number | Required | End (epoch ms) |
{"websiteId": "{{trigger.websiteId}}","startAt": "{{trigger.startAt}}","endAt": "{{trigger.endAt}}"}
{"bounces": {"value": 800,"change": -5},"visitors": {"value": 2000,"change": 8},"pageviews": {"value": 5000,"change": 12},"totaltime": {"value": 300000,"change": 15}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.