# Box

Box is a cloud content management platform where teams store, share, and collaborate on files and documents. It's widely used for document workflows, file-level access control, and enterprise content governance.

Connecting Box to Coupler.io lets you pull your content metadata, user activity, and signing workflows into spreadsheets, data warehouses, or AI tools for analysis and reporting.

**Why connect Box to Coupler.io?**

* Audit file and folder access by exporting collaboration permissions across your organization
* Track document signing workflows by syncing sign requests and sign templates
* Monitor user activity and compliance using admin logs and event streams
* Combine Box data with other sources using Join or Append transformations for richer reporting

## Prerequisites

* A Box developer account with an app configured for Client Credentials Grant (CCG) authentication
* A **Client ID**, **Client Secret**, and **Enterprise ID** (or **User ID**) from your Box app settings
* Your Box app must have the appropriate scopes enabled (e.g., `admin_readwrite` for admin logs)

{% hint style="success" %}
If you're auditing file access or tracking sign requests, start with the **File collaborations** and **Sign requests** entities — they give you the most actionable data right away.
{% endhint %}

## Quick start

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** From your Coupler.io dashboard, click **Add data flow** and search for **Box** as your source.
{% endstep %}

{% step %}
**Enter your Box API credentials.** You'll need your Client ID and Client Secret from your Box developer app. Coupler.io uses these to authenticate via the Client Credentials Grant flow. Paste them into the corresponding fields.
{% endstep %}

{% step %}
**Enter your User ID.** Specify the Box User ID you want to authenticate as. You can find this in your Box developer console or via the Box API. This tells Coupler.io which account context to use when fetching data.
{% endstep %}

{% step %}
**Select an entity.** Choose which Box data you want to pull — for example, **Files**, **Users**, **Admin logs**, or **Sign requests**. Each entity maps to a specific set of Box data.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your Box data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI tool like ChatGPT, Claude, or Gemini.
{% endstep %}

{% step %}
**Run your data flow.** Click **Run** to execute a manual sync. Once it completes successfully, your Box data will appear in your chosen destination.
{% endstep %}
{% endstepper %}

## Available entities

| Entity                | Description                                 |
| --------------------- | ------------------------------------------- |
| Events                | User and enterprise activity events         |
| Admin logs            | Administrative logs for enterprise accounts |
| Files                 | Files stored in Box                         |
| Folders               | Folders organizing Box content              |
| File collaborations   | Collaboration permissions on files          |
| Folder collaborations | Collaboration permissions on folders        |
| File comments         | Comments added to files                     |
| File tasks            | Tasks assigned to files                     |
| Collections           | Groups of related Box content               |
| Collection items      | Items within Box collections                |
| Sign requests         | Document signing requests                   |
| Sign templates        | Templates for signing workflows             |
| Users                 | Box user accounts and profiles              |
| Recent items          | Recently accessed files and folders         |
| Trashed items         | Deleted files and folders in trash          |