Short answer: Drop the "Slack → Slash Command Used" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Slack, 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.
{"raw": {},"text": "weekly sales","command": "/run-report","user_id": "U0123","user_name": "alice","channel_id": "C0123","trigger_id": "12345.67890.abcdef","response_url": "https://hooks.slack.com/commands/..."}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| raw | object | { … } |
| text | string | "weekly sales" |
| command | string | "/run-report" |
| user_id | string | "U0123" |
| user_name | string | "alice" |
| channel_id | string | "C0123" |
| trigger_id | string | "12345.67890.abcdef" |
| response_url | string | "https://hooks.slack.com/commands/..." |
One trigger. 45+ downstream actions. Zero glue.