Box Trigger

Triggers when Box file, folder, or collaboration events occur.

Overview

The Box Trigger node listens for webhook events from Box cloud content management. It can detect file operations (upload, download, copy, move, delete, lock/unlock, preview, rename, trash, restore), folder operations (create, copy, move, delete, download, rename, trash, restore), collaboration changes (created, accepted, rejected, removed, updated), comment activity (created, updated, deleted), shared link changes, metadata instance changes, task assignment changes, and webhook deletion events. When an event occurs on a monitored file or folder, Box sends the event payload to this trigger, which then starts the connected workflow with the full event data.

Category: Data & Storage
Tool Name: box_trigger
Version: 1

Appearance: Icon: si-box | Color: #0061d5

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires Box credentials. See the Credentials Guide for setup instructions.

Parameters

Parameter	Type	Required	Default	Description
Events	multiOptions	Yes	[]	The events to listen to.
				Options: COLLABORATION.ACCEPTED, COLLABORATION.CREATED, COLLABORATION.REJECTED, COLLABORATION.REMOVED, COLLABORATION.UPDATED, COMMENT.CREATED, COMMENT.DELETED, COMMENT.UPDATED, FILE.COPIED, FILE.DELETED (the file is moved to the trash), FILE.DOWNLOADED, FILE.LOCKED, FILE.MOVED (from one folder to another), FILE.PREVIEWED, FILE.RENAMED, FILE.RESTORED (from the trash), FILE.TRASHED, FILE.UNLOCKED, FILE.UPLOADED (a file is uploaded to or moved into this folder), FOLDER.COPIED, FOLDER.CREATED, FOLDER.DELETED (permanently removed), FOLDER.DOWNLOADED, FOLDER.MOVED, FOLDER.RENAMED, FOLDER.RESTORED (from the trash), FOLDER.TRASHED, METADATA_INSTANCE.CREATED (a metadata template instance is associated with a file or folder), METADATA_INSTANCE.DELETED, METADATA_INSTANCE.UPDATED (an attribute of an existing instance is updated or deleted), SHARED_LINK.CREATED, SHARED_LINK.DELETED, SHARED_LINK.UPDATED, TASK_ASSIGNMENT.CREATED, TASK_ASSIGNMENT.UPDATED, WEBHOOK.DELETED (this webhook itself was deleted in Box)
Target Type	options	No	—	The type of item to trigger a webhook.
				Options: file, folder
Target ID	string	No	—	The ID of the file or folder to monitor for events. Supports expressions.

Output Data

Each delivered event produces one output item carrying the Box payload exactly as sent — typically id, type, trigger, created_by, created_at, source (the file or folder the event happened on, with its parent), webhook, and additional_info.

Five fields are added to every item:

• _trigger — always box_webhook
• _timestamp — ISO 8601 timestamp of when the request arrived
• _webhookEvent — the Box trigger name, e.g. FILE.UPLOADED
• _sourceType — the source.type, e.g. file or folder
• _sourceId — the source.id

Deliveries whose trigger is not in your Events selection are acknowledged but do not start the workflow.

Reference the payload downstream by expression, e.g. {{ $json.source.name }} or {{ $json._sourceId }}.

Usage Examples

• Start a workflow when a file is uploaded to a Box folder
• Trigger processing when a file is downloaded from Box
• React to new comments on Box files
• Monitor collaboration changes on Box folders
• Detect when files are moved or renamed in Box

Example Configuration

Watch a folder for new files:

{
  "type": "box_trigger",
  "parameters": {
    "events": ["FILE.UPLOADED"],
    "targetType": "folder",
    "targetId": "123456789"
  }
}

Track the full lifecycle of files in a folder:

{
  "type": "box_trigger",
  "parameters": {
    "events": ["FILE.UPLOADED", "FILE.MOVED", "FILE.RENAMED", "FILE.TRASHED"],
    "targetType": "folder",
    "targetId": "0"
  }
}

Monitor sharing and collaboration on a single file:

{
  "type": "box_trigger",
  "parameters": {
    "events": [
      "SHARED_LINK.CREATED",
      "SHARED_LINK.DELETED",
      "COLLABORATION.CREATED",
      "COLLABORATION.REMOVED"
    ],
    "targetType": "file",
    "targetId": "987654321"
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

Configure with your Box credentials, select which events to listen for, choose whether to watch a file or folder, and provide the target ID. Box will send a webhook notification whenever the selected events occur on the target.

• Target Type and Target ID are how Box scopes the subscription. Set both — Box cannot register a webhook without them. The root folder has ID 0.
• Finding an ID. Open the file or folder in Box; the trailing number in the browser URL is its ID.
• Match events to the target. FILE.UPLOADED, for example, fires for files uploaded to or moved into the watched folder — the option descriptions above say what each event covers.
• Box refuses a second webhook on the same target and address. If activation fails, check whether a webhook already exists on that file or folder.
• WEBHOOK.DELETED tells you the subscription itself was removed in Box — useful as a signal that the workflow has stopped receiving events.