How to connect Box to OpenClaw
Connect Box to OpenClaw with ClawLink in one click — 284 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
BoxOAUTH2MCPStore, share, and manage files and folders. Once connected, OpenClaw can read and act on Box from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Box access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Box setup: install one ClawHub skill, connect Box in the browser, and OpenClaw can call real Box actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Box skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Box" (hith3sh/box-files) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/box-files
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Box.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Box
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Box?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Box in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Box to add allowed collaboration domain and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Box is connected in the dashboard, that agent calls the same 284 Box tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Box MCP for OpenClaw
Looking for a Box MCP server for OpenClaw? ClawLink connects Box to OpenClaw and exposes 284 Box tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Box integration works the same way.
What the OpenClaw Box integration can do
284 Box tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 284.
30 of 284 Box tools for OpenClaw
| Tool | What it does |
|---|---|
Add allowed collaboration domain box_add_allowed_collaboration_domain | Add an allowed domain for collaboration |
Add classification to file box_add_classification_to_file | Add a classification to a file |
Add shared link to file box_add_shared_link_to_file | Add a shared link to a file |
Add shared link to folder box_add_shared_link_to_folder | Add a shared link to a folder |
Add user to group box_add_user_to_group | Add a user to a group |
Apply watermark to file box_apply_watermark_to_file | Apply a watermark to a file |
Ask question box_ask_question | Ask questions about Box files using Box AI |
Authorize user box_authorize_user | Authorize a user by sending them through the Box website and request their |
Download file box_download_file | Returns the contents of a file in binary format |
Download zip archive box_download_zip_archive | Downloads a zip archive containing files and/or folders from Box |
Extract metadata freeform box_extract_metadata_freeform | Extract metadata from Box files using AI with freeform prompts |
Extract metadata structured box_extract_metadata_structured | Extract structured metadata from files using Box AI |
Find app item for shared link box_find_app_item_for_shared_link | Returns the file, folder, web link, or app item represented by a shared link |
Find file for shared link box_find_file_for_shared_link | Returns the file represented by a shared link |
Find folder for shared link box_find_folder_for_shared_link | Return the folder represented by a shared link |
Find metadata template by instance ID box_find_metadata_template_by_instance_id | Finds a metadata template by searching for the ID of an instance of the template |
Generate text box_generate_text | Generate text using Box AI based on a prompt and file context |
Get AI agent box_get_ai_agent | Retrieves detailed information about a specific AI Agent by its unique identifier |
Get AI agent default configuration box_get_ai_agent_default_configuration | Retrieve the default AI agent configuration for a specific mode |
Get allowed collaboration domain box_get_allowed_collaboration_domain | Retrieves details of a specific allowed collaboration domain entry within your enterprise |
Get box sign request box_get_box_sign_request | Retrieves the details of a specific Box Sign request by its unique ID |
Get box sign template box_get_box_sign_template | Retrieves details of a specific Box Sign template by its unique ID |
Get collaboration box_get_collaboration | Retrieves details of a single collaboration by its ID |
Get collection box_get_collection | Retrieves details of a specific collection by its unique identifier |
Get comment box_get_comment | Retrieves the message and metadata for a specific comment, as well as information on the user |
Get current user box_get_current_user | Retrieves information about the user who is currently authenticated |
Get device pin box_get_device_pin | Retrieves information about an individual device pin in the enterprise |
Get events long poll endpoint box_get_events_long_poll_endpoint | Returns a list of real-time servers that can be used for long-polling user events |
Get file information box_get_file_information | Retrieves the details about a file |
Get file request box_get_file_request | Retrieves detailed information about a file request in Box |
Try it: find the Box tool you need
Browse the 30 Box tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Box to add allowed collaboration domain and walk me through the result in plain English.
Use Box to add classification to file and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Box working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Box app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Box through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Box. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Box actions to the runtime in a format your agent can reliably use. | 284 tools for Box are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Box to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Box in the browser, and the 284 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Box skill but can't call the tools
The ClawHub skill teaches OpenClaw about Box, but the calls run through the ClawLink plugin and your connected account. Make sure Box is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Box from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Box tools
Box tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Box call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Box returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Box and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Box integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Box: link your Box account once in the browser and OpenClaw can call the Box API through 284 ready-made tools — no custom code or token handling.
How do I add Box to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Box skill from ClawHub, then you click Connect in the dashboard to authorize Box. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Box to OpenClaw?
About two minutes. Sign in, click Connect next to Box in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Box up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Box working from chat.
OpenClaw installed the Box skill but can't call the tools
The ClawHub skill teaches OpenClaw about Box, but the calls run through the ClawLink plugin and your connected account. Make sure Box is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
