ActionBoxUpdated May 2026

How do I fetch Box file metadata?

Short answer: Drop the "Box → Get File Metadata" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 6 Box actions

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 fileId	string	Required	File ID

Sample request

{
  "fileId": "{{trigger.fileId}}"
}

Returns

{
  "id": "123456",
  "name": "report.pdf",
  "size": 1024,
  "type": "file",
  "parent": {
    "id": "0",
    "name": "All Files"
  },
  "shared_link": null
}

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

Triggered by

Apps that pair well as the trigger for Get File Metadata.

Any of these apps can fire this action as part of a workflow.

2 Google Sheets triggers

HubSpot → Box

18 HubSpot triggers

FAQ

Questions about Get File Metadata.

What does the Get File Metadata action do in Box?

Returns file metadata — size, MIME type, parent folder, owner, modification time, custom metadata. Use this when you need file context without downloading the bytes.

What inputs does Get File Metadata 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 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 Get File Metadata support batch operations?

Yes. Run Get File Metadata 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