Short answer: Drop the "Hotjar → Hotjar Survey Response" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Hotjar, not on a polling schedule.
Drop it on the canvas. Configure a couple of fields. Publish.
You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"url": "https://example.com/checkout","answers": [{"answer": "Smooth","question": "How was your experience?"}],"survey_id": "sv_789","response_id": "sr_456"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| url | string | "https://example.com/checkout" |
| answers | array | [{"answer":"Smooth","question":"How was your experience?"}] |
| survey_id | string | "sv_789" |
| response_id | string | "sr_456" |
One trigger. 2+ downstream actions. Zero glue.