ActionBoxUpdated September 2026

How do I upload a file to Box?

Short answer: You can upload file in Box by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Box Upload File action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Upload File in Box — start free All 6 Box actions

Upload File in Box — start free

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.

Triggered by

Apps that pair well as the trigger for Upload File.

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 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 run history shows the failed step with its input and the error message Box 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 Upload File support batch operations?

Run Upload 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 Box's rate limits.

More actions