Short answer: You can list hotjar heatmaps in Hotjar by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Hotjar List Hotjar Heatmaps action to a workflow, map its 2 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 |
|---|---|---|---|
Site ID site_id | string | Required | Hotjar site ID |
Limit limit | number | Optional | Max heatmaps to return |
{"site_id": "{{trigger.site_id}}","limit": "{{trigger.limit}}"}
{"heatmaps": [{"id": "hm_123","url": "https://example.com/","name": "Homepage clicks","type": "click","createdAt": "2026-04-15T10:00:00Z"}]}
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.