Short answer: Drop the "Jira → Issue Updated" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Jira, 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.
{"key": "PROJ-123","status": "In Progress","summary": "Login page returns 500 error","changelog": [{"to": "In Progress","from": "To Do","field": "status"}]}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| key | string | "PROJ-123" |
| status | string | "In Progress" |
| summary | string | "Login page returns 500 error" |
| changelog | array | [{"to":"In Progress","from":"To Do","field":"status"}] |
One trigger. 17+ downstream actions. Zero glue.