Box

!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

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   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.

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

# 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

clawlink_list_integrations

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

Verify Connection

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

┌─────────────────────────────────────────────────────────────┐
│  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

Sharing & Collaborations

Metadata& Templates

Box Sign (Signature Requests)

Users& Groups

Retention & Legal Hold

AI (Box AI Studio)

Code Examples

List folder items

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

Get file metadata

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

Create a folder

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

Create a collaboration

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

Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:

```bash

openclaw plugins list

```

1. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.
2. If a fresh chat does not help, run:

```bash

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

openclaw gateway restart

```

1. 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

!ClawLink Logo