Integrations · Files & storage

Box in the conversation.

Enterprise content management — where regulated teams keep the documents everything else refers to. Connect it once and your copilot works with files, folders, shared links and collaborations without leaving the thread — and your workflows can act on it while the customer is still typing.

No credit card required · 7-day free trial

Box
Files & storage
01 · COPILOT

Ask for it in plain language. It does the Box part.

Copilot rides inside the inbox. With Box connected it reads files, folders, shared links and collaborations and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

  • Copy file
  • Assign task
  • Copy folder
  • Create task
  • Ask question
  • Create group

What a specific connection exposes is decided by Box, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.

02 · WORKFLOWS

Something happens in Box. A workflow starts.

Once Box is connected, its events show up in the workflow editor's trigger picker, and the fields the event carries become variables every later step can read — so the message you send is written from what actually happened.

  • Collaboration Details Changed
  • Comment Changed
  • New File Comment Added
  • File Metadata Changed

The picker is the authority on which events your Box connection publishes — these are the kinds that apps of this sort emit.

03 · THE AI AGENT STEP

One step that decides which Box tools to call.

A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.

You declare the output

The rows you name become the variables downstream steps read, so a branch can test what Box said.

You cap the effort

A step budget and a model tier per node — the loop stops where you told it to.

Only what you switched on

The loop can call the Box tools you left enabled and nothing else.

What teams do with it

Two ways Box earns its connection.

01

Send the current version, not last quarter’s

A customer asks for the terms or the spec sheet. The copilot finds the live document in Box and the agent sends it, rather than an attachment someone saved to their desktop in March.

02

Every escalation keeps its paper trail

A workflow files the transcript and its attachments into the Box folder for that account, so the record survives the conversation being closed.

Setup

Connect Box in about a minute.

  1. 1

    Open Settings → Apps

    It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.

  2. 2

    Find Box in Browse

    The catalogue runs to hundreds of apps and is searchable. Connect Box from its card.

  3. 3

    Authorize with your own Box account

    You sign in on Box's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.

  4. 4

    Choose the tools it may call

    Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.

Box questions.

How do I connect Box to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for Box. Connecting it opens Box's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.
What can Cloodot do in Box?
Work of this kind: copy file; assign task; copy folder; create task; ask question; create group. The exact list depends on what your Box account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which Box tools Cloodot may use?
Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Box connection is a matter of leaving the writes off.
Can an event in Box start a Cloodot workflow?
Yes. Events like collaboration details changed, comment changed, new file comment added, file metadata changed appear in the workflow editor's trigger picker once Box is connected, and the event's own fields become variables the rest of the workflow can read.
Who in my team can connect Box?
Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Box account that authorized it, so a files & storage connection is only ever as broad as the account behind it.
See it on your own inbox

Try the whole thing, today.

Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.