List Files: Anthropic action

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
Limit limit	string	Optional	Max files to return (1-1000)

Sample request

{
  "limit": "20"
}

Returns

{
  "data": [
    {
      "id": "file-abc123",
      "type": "file",
      "filename": "report.pdf",
      "mime_type": "application/pdf",
      "created_at": "2026-04-17T10:00:00Z",
      "size_bytes": 204800
    }
  ],
  "has_more": false
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Files.

What does the List Files action do in Anthropic?

Lists uploaded files in your Anthropic workspace with their IDs, names, and sizes. Used to render a file picker or for cleanup automations.

What inputs does List Files require?

List Files has no required inputs. Sensible defaults are applied if you leave fields blank.

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 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 List Files support batch operations?

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

More actions