Upload File: Box 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
Folder ID folderId	string	Required	Folder ID. Example: 0 for root
File Name fileName	string	Required	File Name
File Content (base64) fileContent	string	Required	Base64-encoded file content

Sample request

{
  "folderId": "e.g. 0 for root",
  "fileName": "{{trigger.fileName}}",
  "fileContent": "{{trigger.fileContent}}"
}

Returns

{
  "entries": [
    {
      "id": "123456",
      "name": "report.pdf",
      "size": 1024,
      "type": "file"
    }
  ],
  "total_count": 1
}

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

FAQ

Questions about Upload File.

What does the Upload File action do in Box?

Uploads a file from URL or base64 content to a specific Box folder with optional metadata. For workflows that auto-archive content into Box (transcripts from Fireflies, screenshots from automated tests, exports from BI tools).

What inputs does Upload File require?

Required: Folder ID, File Name, File Content (base64). 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 Upload File support batch operations?

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