Short answer: Drop the "Slack → File Shared" 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": {"type": "event_callback","event": {"type": "file_shared","file_id": "F0123ABC","user_id": "U0123DEF","event_ts": "1712835600.000100","channel_id": "C0123ABC"},"token": "verification_token","team_id": "T1234567890","event_id": "Ev1234567890","api_app_id": "A1234567890","event_time": 1712835600},"user": "U0123DEF","channel": "C0123ABC","file_id": "F0123ABC"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| raw | object | { … } |
| raw.type | string | "event_callback" |
| raw.event | object | { … } |
| raw.event.type | string | "file_shared" |
| raw.event.file_id | string | "F0123ABC" |
| raw.event.user_id | string | "U0123DEF" |
| raw.event.event_ts | string | "1712835600.000100" |
| raw.event.channel_id | string | "C0123ABC" |
| raw.token | string | "verification_token" |
| user | string | "U0123DEF" |
| channel | string | "C0123ABC" |
| file_id | string | "F0123ABC" |
One trigger. 45+ downstream actions. Zero glue.