Short answer: Drop the "GitLab → GitLab Pipeline Completed" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in GitLab, 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": 789,"ref": "main","status": "success","duration": 120}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| id | number | 789 |
| ref | string | "main" |
| status | string | "success" |
| duration | number | 120 |
One trigger. 10+ downstream actions. Zero glue.