Content under development


Box is a file sharing, storage, and collaboration service for enterprises. You can integrate Box with ManyWho to modify, share, or edit documents and folders stored in Box in an app. You can also use the integration to trigger an action in ManyWho if a document or folder is edited, downloaded, or uploaded in Box.

Box has three types of plans – Personal Plans, Business Plans, and Platform Plans. The functionalities you will get, depend on the type of Box account you have. For example, if you want to use Metadata, an Enterprise plan is required.

ManyWho does not distinguish between Box users. It will work with App Users, as well as personal or corporate Box users.

If you want your app to access Box on behalf of your users, you will need to have each user authenticate with Box to a] Verify their identity, and b] Grant your app permission to access the content stored in their Box account. Users can revoke permission any time.

ManyWho uses OAuth 2.0 for flow authorization, and OAuth 2.0 with JSON Web Tokens when installing the service (to create Types from Box Metadata). OAuth 2 with JSON Web Tokens enables an application to connect directly to Box, and obtain authorization to access files and folders without requiring users to log in.

ManyWho does not need nor stores the Box user credentials of the builder. Instead, Enterprise ID is used for identity and authentication. The Enterprise ID can be found in the Box Admin Console. If you do not find your Enterprise ID, please contact your IT administrator.

Features of the Box Service

The Box Service as used with ManyWho supports:

  1. Identity
  2. Database
  3. Files
  4. Logic
  5. Listening
1.  Identity

The Box credentials of your users can be used to authenticate them in a ManyWho app. You can use authentication to a] Verify their identity, and b] Grant your app permission to access the contents stored in their Box account.

Box authentication works for both external and managed users. As defined by Box, an external user is an account created by a Box user for that person’s own use. A managed user is an account that was created by an administrator for use by another person. You can find more information on users here.

Box uses OAuth 2.0 for  authentication and verification, and users can revoke permission any time. ManyWho does not store the user’s Box credentials.

2. Database

This service supports loading and saving data from Box.

3. Files

This service supports uploading, listing, and deleting files.

4. Logic

This service contains message actions:

File Copy

Use File Copy to copy a file to a different folder. Optionally, you can rename the file, as you are copying it. File Copy does not modify the original file.

Name Type Required Description
Source File File Object Yes The file you are copying.
Destination Folder Folder Object Yes The folder you are copying the file to.
Name String Optional New name of the file.

File Move

Use File Move to move a file to a different folder. Optionally, you can rename the file, as you are moving it. File Move removes the original file in the source folder.

 Name  Type  Required  Description
 Source File  File Object  Yes  The file you are copying.
 Destination Folder  Folder Object  Yes  The folder you are copying the file to.
 Name  String  Optional  New name of the file.

Tasks — Assign a Task over email

Tasks in Box help you create, assign and manage tasks related to individual files. You can use Tasks to assign a task to yourself, and/or your collaborators. Currently, Tasks can only be created if comments are enabled.

You can use Tasks to assign a task to a user over email.


Name  Type Required Description
Task Task Object Yes Description of the task.
Email String Yes Email of the user assigned the task.


Name Type Required Description
Task assignment Task Assignment Object Yes


Webhooks  – Assigning Webhooks to a flow

Adding webhooks to an application, lets you monitor the application for changes. When a monitored object changes, Box notifies your application of the change. Webhooks notifications are sent as POST requests with a JSON array of notification objects as the body data. Multiple events will be included in a single request, where possible.

Name Type Required Description
 Flow ID  String  Yes  The Flow ID of the flow
 Flow Version ID  String  Yes  The version ID of the flow
 Tenant ID  String  Yes  The tenant ID where the flow is
 Target Type  String  Yes  Target Type in Box (e.g. file or folder).
 Target ID  String  Yes  ID of the Target in Box (e.g. id of the file if Target Type is a file).
 Trigger  String  Yes  The event trigger you want the webhook to monitor.

5. Listening

This service supports listening to Objects.

 Developer Docs
 Configuring Box  Developer Guide: Box Uploading files in Box
Launching an app from Box
Listening to Box Objects


Configuration Developer Docs Tutorials
 Configuring Twilio Developer Guide: Twilio Getting an app to text you (TextBot app using Twilio)
Getting an app to call you (AlarmBot app using Twilio)


 Configuration  Developer Docs  Tutorials

Google Apps

 Configuration  Developer Docs  Tutorials

Microsoft Exchange

 Configuration  Developer Docs  Tutorials


 Configuration Developer Docs Tutorials