Skip to content

Box, without opening Box.

Files, folders, and the tasks on them, kept moving from the thread.

  • Free to start
  • No card
  • Every write waits for you
  • Your own account, not a shared login
Try asking Ray

Ask in your own words.

Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Box details, and Ray takes it from there.

  • @Ray who has commented on the SOW, and is the task still open?

  • @Ray where is the latest version of the security questionnaire?

  • @Ray create a review task on that contract and assign it to Dana.

  • @Ray make a folder for the Northwind onboarding under clients.

What Ray can and cannot do in Box

Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.

11 reads wired, 11 actions that wait for a human.

Runs on its own

What Ray reads in Box

  • Files, folders, and what was recently opened
  • File versions, comments, and tasks
  • Search across your content

Reading changes nothing, so Ray never stops to ask whether it may look something up.

Asks first, every time

What waits for your approval

  • Create a folder
  • Copy, rename, or move a file or folder
  • Comment on a file, or edit a comment
  • Raise a task, assign it, or update it

Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.

Not on the list

Things Ray is never handed

These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.

  • Delete a file or a folder, permanently or otherwise
  • Create a collaboration, so sharing stays with you
  • Change retention, legal hold, or security policies
Before it acts

Exactly what Ray will ask you to approve.

Not a category of permission. These are the Box actions Ray can take, each one stopping in the thread with the real content before it happens.

  • Assign a Box task
  • Copy a Box file
  • Copy a Box folder
  • Comment on a Box file
  • Create a Box folder
  • Raise a Box task
  • Edit a Box comment
  • Rename or move a Box file
  • Rename or move a Box folder
  • Update a Box task
The card Ray posts

Assign a Box task

Showing Task id, each carrying the exact content that will land.

ApproveDecline

How Ray works with Box

No workflow to build, and nothing to maintain when the work changes.

  1. 01

    Connect Box

    One click, right where you asked. Ray posts a connect card, you authorise Box with your own account, and the work you asked for picks up where it left off.

  2. 02

    Ask in plain words

    In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.

  3. 03

    Approve, and it lands

    Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.

and the rest

Priya

@Ray the checkout bug is back. Take a look in Box, and tell Dana it is being looked at.

Assign a Box task

Waiting on
your approval
ApproveDecline
Works with your stack

Ray uses Box together with the rest of your tools.

One ask can read Box, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.

What does connecting Box to Ray actually do?

Ray is an AI teammate that works in your team chat, on Slack today. Connect Box and it can do the Box part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.

It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.

Every person on the team connects their own Box account, so Ray can only reach what that person can already reach, and the history in Box shows who actually asked.

Security and permissions

  • You authorise Box on its own login screen. Your password never passes through Ray.
  • Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
  • Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
  • Disconnect Box in a message, or uninstall Ray and every connection it held is revoked.

How Ray handles your data

Box and Ray, answered

The questions teams ask before they connect Box. Every answer is how this integration is built rather than a promise about it.

More storage & files integrations

Ray uses them together in a single run when a request spans more than one.

Browse every integration

Put Ray to work in Box.

Free to start, no credit card, and it asks before it acts.

Add to Slack for free