About the Box connector

Box is a cloud-based content management and file sharing platform. After connecting, automate the entire content lifecycle-creating and sharing new files, collaborative editing, signature gathering, and more.

Authentication

Before automating processes, you need to establish a connection with your Box instance. Step-by-step instructions are available in the Box authentication page.

Events

The Box connector supports events via polling. More information about the events supported for the Box connector is available in the Box events page.

Activities

You can use the connection to enable the Box activities in UiPath® Studio and build automations that interact with your Box data. This allows you to execute create, read, update, and delete operations on your Box objects.

Provider documentation

The UiPath connector is compatible with Box v2 REST API. Learn more from the Box API documentation.

Frequently asked questions

Which authentication method should I use?

Refer to Box authentication in the documentation. This section explains each authentication method and helps you choose the one that best fits your security and deployment requirements.

Which scopes should I configure during the connection?

See Understanding Box scopes on the authentication page. As a best practice, start with the least-privileged scopes, and only add additional scopes if an activity requires them.

What if an activity I need is not supported?

If a specific activity is not available, use the HTTP Request activity to call the Box API directly. You can refer to the official Box API documentation to identify the correct endpoint and payload format.

Why does the Box token expire or stop working after a few weeks?

If a workflow is kept active (not idle) within every 60-day window, the refresh token continues to renew automatically, and no re-authentication is required. Authentication is only needed if the workflow stays idle for at least 60 days or if the vendor’s refresh call fails or expires due to their own session limits.

Why does the “Add Shared Link to Folder” action or other Box actions fail with a 403 error?

The user or API key lacks the permissions required to create shared links or access folder settings.

I do not see an activity or trigger in Maestro. Why?

Not all activities or triggers are supported across all UiPath products (Maestro, API Workflow, Agent Builder, RPA) or platforms.