ActionAnthropicUpdated September 2026
How do I get metadata about an Anthropic uploaded file?
Short answer: You can get file in Anthropic by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Anthropic 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.
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_id | string | Required | File ID. Example: file-abc123 |
Sample request
{"file_id": "e.g. file-abc123"}
Returns
{"id": "file-abc123","type": "file","filename": "report.pdf","mime_type": "application/pdf","created_at": "2026-04-17T10:00:00Z","size_bytes": 204800,"downloadable": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get File.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get File.
What does the Get File action do in Anthropic?
Returns metadata about an uploaded file (filename, mime type, size, created_at). Use to verify an upload succeeded or to render a file picker.
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 Anthropic returns an error?
The run history shows the failed step with its input and the error message Anthropic returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get File support batch operations?
Run Get File inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Anthropic's rate limits.
More actions
Other Anthropic actions.
Action
Analyze Image
Sends an image to Claude for analysis (vision), via URL or base64 bytes alongside a text prompt. Use for OCR, chart extraction, accessibility alt-text, or visual QA flows.
ActionCancel Message Batch
Cancels a message batch that is still processing. Already-completed entries in the batch keep their results; in-flight ones get cancelled with no charge.
ActionComputer Use
Sends a message with the computer-use tool, letting Claude take screenshots and click/type on a virtual desktop. Requires Opus 4.x or Sonnet 4.x; you provide the sandboxed desktop environment.
ActionCount Tokens
Counts the number of tokens a Messages API call would consume without actually sending the message. Useful for cost estimation and to stay under context-window limits.
ActionCreate Message
Sends a message to a Claude model and gets a response. The core Anthropic action; supports system prompts, multi-turn conversation, temperature, and stop sequences.
ActionCreate Message Batch
Creates a batch of messages for async processing on the Messages API, with a 50% cost reduction and up to 24-hour turnaround. Perfect for bulk classification, summarization, or labeling jobs.