Get File: Slack action · Tiny Command

Inputs

The fields this action accepts.

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.

Sample request

{
  "file": "e.g. F0123ABC456"
}

Returns

{
  "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.

FAQ

Questions about Get File.

What does the Get File action do in Slack?

Fetches metadata for a specific Slack file by ID (name, mimetype, size, download URL, shares). Used to verify a file or to prep a download.

What inputs does Get File require?

Required: File ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Slack returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get File support batch operations?

Yes. Run Get File inside a Loop node to process arrays. Tiny Command handles Slack's rate limits automatically so you don't have to throttle manually.

More actions