Short answer: Drop the "Umami → Get Website Stats" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
Triggered by anything in the catalog. Free tier available. No credit card.