Box#

Access Box via the Box API with managed OAuth authentication. Browse files, inspect metadata, manage sharing and collaboration, and coordinate file workflows from chat.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Box API access yourself.

Setup in 3 Steps#

Step 1: InstallStep 2: Pair AccountStep 3: Connect Box_App-specific connection GIF coming soon_Run the install command in OpenClawSign in and approve the deviceOpen the dashboard and connect Box

How It Works#

text

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│     Box API        │
│   (User Chat)   │     │   (OAuth)    │     │   (Files) │
└─────────────────┘     └──────────────┘     └──────────────────┘
          │                       │                       │
          │  1. Install Plugin    │                       │
          │  2. Pair Device       │                       │
          │  3. Connect Box      │                       │
          │                       │  4. Secure Token      │
          │                       │  5. Proxy Requests    │
          │                       │                       │
          ▼                       ▼                       ▼
    ┌──────────┐           ┌──────────┐           ┌──────────┐
    │  SKILL   │           │ Dashboard│           │  Box     │
    │  File    │           │ Auth     │           │ Web App │
    └──────────┘           └──────────┘           └──────────┘

Install#

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

bash

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Box again."

Quick Start#

bash

# List integrations
clawlink_list_integrations

# List Box tools
clawlink_list_tools --integration box

# Search for a specific tool
clawlink_search_tools --query "file" --integration box

Authentication#

All Box tool calls are authenticated automatically by ClawLink using the user's connected Box account.

No API key is required in chat. ClawLink stores the OAuth token securely and injects it into every Box API request on the user's behalf.

Getting Connected#

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=box and connect Box.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management#

List Connections#

bash

clawlink_list_integrations

Response: Returns all connected integrations. Look for box in the list.

Verify Connection#

bash

clawlink_list_tools --integration box

Response: Returns the live tool catalog for Box.

Reconnect#

If Box tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=box
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration box

Discovery Workflow#

1. Call clawlink_list_integrations to confirm Box is connected.
2. Call clawlink_list_tools --integration box to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration box.
5. If no Box tools appear, direct the user to https://claw-link.dev/dashboard?add=box.

Execution Workflow#

text

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → search → describe → call                      │
│                                                             │
│  Example: List files → Get metadata → Show results │
└─────────────────────────────────────────────────────────────┘
                               │
                               ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  list → get → describe → preview → confirm → call           │
│                                                             │
│  Example: Describe tool → Preview changes → User approves   │
│           → Execute update                                  │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.
4. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Tool Reference#

Files& Folders#

ToolDescriptionModebox_list_folderList items in a folderReadbox_get_fileGet file metadata and detailsReadbox_create_folderCreate a new folderWritebox_upload_fileUpload a file to BoxWritebox_copy_fileCopy a file to another folderWritebox_move_fileMove a file to another folderWritebox_delete_filePermanently delete a fileWritebox_download_fileDownload a file from BoxRead

Sharing & Collaborations#

ToolDescriptionModebox_create_collaborationAdd a collaborator to a file or folderWritebox_delete_collaborationRemove a collaboratorWritebox_add_shared_link_to_fileAdd a shared link to a fileWritebox_add_shared_link_to_folderAdd a shared link to a folderWritebox_get_file_collaboratorsList collaborators on a fileRead

Metadata& Templates#

ToolDescriptionModebox_create_metadata_templateCreate a metadata templateWritebox_create_metadata_instance_on_fileApply metadata to a fileWritebox_create_metadata_instance_on_folderApply metadata to a folderWritebox_get_metadata_templateGet metadata template detailsRead

Box Sign (Signature Requests)#

ToolDescriptionModebox_create_box_sign_requestCreate a signature requestWritebox_cancel_box_sign_requestCancel a pending signature requestWritebox_get_sign_requestGet signature request statusRead

Users& Groups#

ToolDescriptionModebox_list_usersList enterprise usersReadbox_create_userCreate a new managed userWritebox_create_groupCreate a new groupWritebox_add_user_to_groupAdd a user to a groupWrite

Retention & Legal Hold#

ToolDescriptionModebox_create_retention_policyCreate a retention policyWritebox_assign_retention_policyAssign a retention policyWritebox_create_legal_hold_policyCreate a legal hold policyWritebox_assign_legal_hold_policyAssign a legal hold policyWrite

AI (Box AI Studio)#

ToolDescriptionModebox_ask_questionAsk questions about Box files using AIReadbox_create_ai_agentCreate a custom AI agentWrite

Code Examples#

List folder items#

bash

clawlink_call_tool --tool "box_list_folder" \
  --params '{
    "folder_id": "0",
    "limit": 20
  }'

Get file metadata#

bash

clawlink_call_tool --tool "box_get_file" \
  --params '{
    "file_id": "123456789"
  }'

Create a folder#

bash

clawlink_call_tool --tool "box_create_folder" \
  --params '{
    "name": "New Project Folder",
    "parent_folder_id": "0"
  }'

Create a collaboration#

bash

clawlink_call_tool --tool "box_create_collaboration" \
  --params '{
    "item": {
      "type": "file",
      "id": "123456789"
    },
    "accessible_by": {
      "type": "user",
      "email": "collaborator@example.com"
    },
    "role": "viewer"
  }'

Security & Permissions#

• Access is scoped to the connected Box account's permissions and enterprise policies.
• All write operations require explicit user confirmation. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
• Destructive actions (deleting files, folders, users) are marked as high-impact and must be confirmed.
• Collaboration changes affect external user access; confirm before adding or removing collaborators.
• Legal hold and retention policy operations require appropriate admin permissions.

Notes#

• Folder ID "0" refers to the root (All Files) folder.
• File IDs and folder IDs are distinct namespaces in Box.
• Shared links can be configured with different access levels (open, company, collaborators).
• Some enterprise features (classifications, legal hold, retention) require specific Box plans.

Error Handling#

Status / ErrorMeaningTool not foundThe tool name does not exist in the current catalog. Verify with clawlink_list_tools --integration box.Missing connectionBox is not connected. Direct the user to https://claw-link.dev/dashboard?add=box.ItemNotFoundFile or folder does not exist. Check the ID.ConflictA file or folder with that name already exists in the target location.AccessDeniedNo permission to access this resource. Verify account permissions.Write rejectedUser did not confirm a write action. Always confirm before executing writes.

Troubleshooting: Tools Not Visible#

1. Check that the ClawLink plugin is installed: bash

   openclaw plugins list
   
   

2. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.

3. If a fresh chat does not help, run: bash

   openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
   openclaw gateway restart
   
   

4. After restart, tell the user to send /new again and retry.

Troubleshooting: Invalid Tool Call#

1. Ensure the integration slug is exactly box.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For write operations, always call clawlink_preview_tool first.

Resources#

• Box Developer Documentation
• Box API Reference
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=box-files
• ClawLink Docs: https://docs.claw-link.dev/openclaw
• ClawLink Verification: https://claw-link.dev/verify

---

Powered by ClawLink — an integration hub for OpenClaw