Short answer: Drop the "Bitbucket → Issue Created" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Bitbucket, 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.
{"id": 1,"state": "new","title": "Bug report","priority": "major","reporter": "User"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| id | number | 1 |
| state | string | "new" |
| title | string | "Bug report" |
| priority | string | "major" |
| reporter | string | "User" |
One trigger. 10+ downstream actions. Zero glue.