List Folder Contents: Box 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
Folder ID folderId	string	Required	Use 0 for root folder
Limit limit	number	Optional	Limit

Sample request

{
  "folderId": "{{trigger.folderId}}",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "entries": [
    {
      "id": "123",
      "name": "report.pdf",
      "size": 1048576,
      "type": "file",
      "modified_at": "2026-04-11T10:00:00Z"
    }
  ],
  "total_count": 1
}

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

FAQ

Questions about List Folder Contents.

What does the List Folder Contents action do in Box?

Returns files and sub-folders within a specific folder with metadata. Useful for "inventory all files in this client folder" reporting or for "iterate over folder contents and process each" batch workflows.

What inputs does List Folder Contents require?

Required: Folder 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 Box 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 Folder Contents support batch operations?

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

More actions