Short answer: You can get file in Slack by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Slack Get File action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
File ID file | string | Required | Slack file ID (starts with F). Find via List Files. Not the filename. |
{"file": "e.g. F0123ABC456"}
{"id": "F0123ABC","ok": true,"raw": {},"name": "report.pdf","size": 12345,"mimetype": "application/pdf","url_private_download": "https://files.slack.com/..."}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.