Start free
ActionBoxUpdated June 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.

FieldTypeRequiredDescription
Folder ID
folderId
stringRequiredFolder ID. Example: 0 for root
File Name
fileName
stringRequiredFile Name
File Content (base64)
fileContent
stringRequiredBase64-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.

Gmail → Box
1 Gmail triggers
Slack → Box
13 Slack triggers
Google Sheets → Box
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 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. TinyCommand handles Box's rate limits automatically so you don't have to throttle manually.
More actions

Other Box actions.

Action
Create Folder
Creates a folder under a specified parent. Useful for client-onboarding workflows that auto-provision a folder structure ("Client/Brand/Assets/", "Client/Contracts/", "Client/Deliverables/").
Action
Download File
Downloads file content by ID. For workflows that need to relocate files (Box → S3 archival, Box → email attachment) or process them downstream (OCR, transcoding, classification).
Action
Get File Metadata
Returns file metadata — size, MIME type, parent folder, owner, modification time, custom metadata. Use this when you need file context without downloading the bytes.
Action
List Folder Contents
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.
Action
Search Box
Full-text and metadata search across Box content the connecting user can see. Filterable by file type, owner, modification date, custom metadata. Useful for "find all contracts that mention term X" or for agentic workflows that ground answers in Box-stored knowledge.
Upload File in Box — start free