- Integrations
- /
- Box
- /
- Actions
- /
- Search Box
ActionBoxUpdated May 2026
How do I search files in Box?
Short answer: Drop the "Box → Search Box" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
|---|---|---|---|
Search Query query | string | Required | Search Query. e.g. "quarterly report" |
Type type | options | Optional | Type. Options: All, Files only, Folders only |
Limit limit | number | Optional | Limit |
Sample request
{"query": "quarterly report","type": "{{trigger.type}}","limit": "{{trigger.limit}}"}
Returns
{"entries": [{"id": "789","name": "Q1 Report.pdf","size": 2097152,"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 Search Box.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Search Box.
What does the Search Box action do in 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.
What inputs does Search Box require?
Required: Search Query. 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 Search Box support batch operations?
Yes. Run Search Box 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
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/").
ActionDownload 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).
ActionGet 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.
ActionList 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.
ActionUpload File
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).
Send search box from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.