ActionUmamiUpdated September 2026
How do I check my Umami connection?
Short answer: You can get account info in Umami by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Umami Get Account Info action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Sample request
{}
Returns
{"status": "active"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get Account Info.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Account Info.
What does the Get Account Info action do in Umami?
Returns account information from the connected Umami analytics instance. Useful as a connection-check or in admin dashboards.
What inputs does Get Account Info require?
Get Account Info has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Umami returns an error?
The run history shows the failed step with its input and the error message Umami returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get Account Info support batch operations?
Run Get Account Info inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Umami's rate limits.
More actions