Box integration

What it does

The Box integration lets your agency move work in and out of your clients' Box accounts without leaving TaskJuice. Connect a Box account once and your workflows can list folder contents, create new folders, copy files between locations, soft-delete files, and search across the account using the Box Content API v2. When a file is uploaded, copied, deleted, or any other subscribed event fires inside the connected account, Box notifies TaskJuice and your workflow reacts in seconds.

Connect a Box account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Box and click Connect.
3. Sign in to the Box account you want to wire up and approve the requested scopes (root_readwrite, manage_webhook).
4. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access, sign in at box.com, open Account Settings, go to Apps, and remove the TaskJuice authorization. The full grant flow is documented in the Box OAuth 2.0 guide.

Triggers

• box/content-event fires when any subscribed Box content event occurs in the connected account (file uploaded, copied, moved, deleted, restored, previewed, downloaded, or commented; folder created or renamed). The activation payload carries the Box event id, the trigger string (for example FILE.UPLOADED), and the file or folder the event references.

Every inbound POST is authenticated by recomputing HMAC-SHA256 over the raw request body concatenated with the box-delivery-timestamp header using your Box webhook primary key, then comparing the base64 digest against the value Box sends in the box-signature-primary header. Activations that fail the check are rejected before they reach your workflow.

Actions

• box/get-folder fetches metadata for a single folder by id. Use 0 for the All Files root.
• box/list-folder-items lists the immediate children of a folder, with marker-based pagination.
• box/create-folder creates a new folder inside the specified parent.
• box/copy-file copies a file into a destination folder, optionally renaming the copy.
• box/delete-file moves a file to the Box trash. Items remain restorable until the trash retention window expires.
• box/search searches across files and folders by query string, with marker-based pagination and an optional result-type filter.

Known limitations

• The Box API enforces per-app and per-user rate limits. When a 429 status is returned, TaskJuice surfaces it as a retryable error so the workflow can back off and retry.
• This integration covers the JSON endpoints under api.box.com/2.0/*. Content-upload and content-download endpoints, which require the separate upload.box.com and dl.boxcloud.com hosts, are not exposed.
• Webhooks v2 must be created against a specific file or folder target in Box (Developer Console > Webhooks). Workflows can scope a single trigger to a single Box target; subscribe multiple targets by creating additional Box webhooks.
• Folder and file names are case-preserving but case-insensitive within a parent in Box; pass names in the casing you want surfaced in the UI.