Short answer: Drop the "Hotjar → List Hotjar Heatmaps" 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 |
|---|---|---|---|
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.
Triggered by anything in the catalog. Free tier available. No credit card.