Short answer: Drop the "Bitbucket → Pull Request 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": "OPEN","title": "Feature branch","author": "Developer","source": "feature","destination": "main"}
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 | "OPEN" |
| title | string | "Feature branch" |
| author | string | "Developer" |
| source | string | "feature" |
| destination | string | "main" |
One trigger. 10+ downstream actions. Zero glue.