Skip to main content

Prerequisites

Before continuing, you should have already completed the following for this connector:
1

Configure the Connector

Enable the connector and set up its connector profile in your project. See Managing Connectors.
https://stackone-logos.com/api/box/filled/png

Connector Profile

Box - OAuth 2.0
2

Link an Account

Connect an account using StackOne Hub or Auth Link.
https://stackone-logos.com/api/box/filled/png

Link Account

Box - OAuth 2.0

Subscribe via the StackOne dashboard

This connector uses Programmatic Webhooks. When you enable webhook events for a connected Box account, StackOne automatically registers a webhook on each configured folder (via POST /2.0/webhooks), subscribed to all the events you selected.

1

Ensure webhook permissions

Your Box Custom App must have the Manage webhooks permission enabled.

  • Sign in to the Box Developer Console.
  • Open your Custom App (e.g., “Falcon1”).
  • Go to the Configuration tab.
  • Under Developer Actions, ensure Manage webhooks is checked.
  • Click Save if you made changes.
2

Find folder IDs to monitor

Identify the Box folders you want to receive webhook events for. Each folder’s ID can be found in the URL when you open it in Box.

  • Open Box and navigate to the folder you want to monitor.
  • The folder ID is the number at the end of the URL. For example, in https://app.box.com/folder/391960849645, the folder ID is 391960849645.
  • To monitor multiple folders, note down each folder ID.
3

Set the Webhook Folder IDs

When linking your Box account in StackOne (or via StackOne Hub), enter the folder IDs in the Webhook Folder IDs field.

  • Enter a single folder ID (e.g., 391960849645) to monitor one folder.
  • Enter multiple folder IDs separated by commas (e.g., 391960849645,392715006683) to monitor multiple folders. A webhook is registered on each folder.
4

Select event subscriptions in the dashboard

In the StackOne dashboard, open the Box connector profile and enable the webhook events you want to receive. See the Available Webhook Events section below for the full list.

5

Connect the Box account

On account connection (or when event subscriptions change), StackOne registers a webhook on each configured folder on your behalf using the connected account’s OAuth 2.0 credentials.

Available Webhook Events

The following Box events can be enabled. Only events selected in StackOne are included in the webhook subscription.

1

File events

Events related to files within monitored folders.

  • File Uploaded (FILE.UPLOADED) — Fired when a file is uploaded
  • File Previewed (FILE.PREVIEWED) — Fired when a file is previewed
  • File Downloaded (FILE.DOWNLOADED) — Fired when a file is downloaded
  • File Trashed (FILE.TRASHED) — Fired when a file is moved to the trash
  • File Deleted (FILE.DELETED) — Fired when a file is permanently deleted
  • File Restored (FILE.RESTORED) — Fired when a file is restored from the trash
  • File Copied (FILE.COPIED) — Fired when a file is copied
  • File Moved (FILE.MOVED) — Fired when a file is moved to a different folder
  • File Locked (FILE.LOCKED) — Fired when a file is locked for editing
  • File Unlocked (FILE.UNLOCKED) — Fired when a file lock is released
  • File Renamed (FILE.RENAMED) — Fired when a file is renamed
2

Folder events

Events related to folders within monitored folders.

  • Folder Created (FOLDER.CREATED) — Fired when a new folder is created
  • Folder Renamed (FOLDER.RENAMED) — Fired when a folder is renamed
  • Folder Downloaded (FOLDER.DOWNLOADED) — Fired when a folder is downloaded
  • Folder Deleted (FOLDER.DELETED) — Fired when a folder is permanently deleted
  • Folder Trashed (FOLDER.TRASHED) — Fired when a folder is moved to the trash
  • Folder Restored (FOLDER.RESTORED) — Fired when a folder is restored from the trash
  • Folder Copied (FOLDER.COPIED) — Fired when a folder is copied
  • Folder Moved (FOLDER.MOVED) — Fired when a folder is moved
3

Comment events

Events related to comments on files.

  • Comment Created (COMMENT.CREATED) — Fired when a comment is added to a file
  • Comment Updated (COMMENT.UPDATED) — Fired when a comment is edited
  • Comment Deleted (COMMENT.DELETED) — Fired when a comment is deleted
4

Collaboration events

Events related to shared access on files and folders.

  • Collaboration Created (COLLABORATION.CREATED) — Fired when a collaboration is created
  • Collaboration Accepted (COLLABORATION.ACCEPTED) — Fired when a collaboration invitation is accepted
  • Collaboration Rejected (COLLABORATION.REJECTED) — Fired when a collaboration invitation is rejected
  • Collaboration Removed (COLLABORATION.REMOVED) — Fired when a collaboration is removed
  • Collaboration Updated (COLLABORATION.UPDATED) — Fired when a collaboration’s role or permissions change
5

Shared Link events

Events related to shared links on files and folders.

  • Shared Link Created (SHARED_LINK.CREATED) — Fired when a shared link is created
  • Shared Link Deleted (SHARED_LINK.DELETED) — Fired when a shared link is removed
  • Shared Link Updated (SHARED_LINK.UPDATED) — Fired when a shared link’s settings change
6

Task Assignment events

Events related to task assignments on files.

  • Task Assignment Created (TASK_ASSIGNMENT.CREATED) — Fired when a task is assigned to a user
  • Task Assignment Updated (TASK_ASSIGNMENT.UPDATED) — Fired when a task assignment is updated (completed, rejected, etc.)
7

Metadata events

Events related to metadata on files and folders.

  • Metadata Instance Created (METADATA_INSTANCE.CREATED) — Fired when metadata is applied to a file or folder
  • Metadata Instance Updated (METADATA_INSTANCE.UPDATED) — Fired when metadata on a file or folder is updated
  • Metadata Instance Deleted (METADATA_INSTANCE.DELETED) — Fired when metadata is removed from a file or folder
8

Webhook lifecycle events

Events related to webhook subscriptions themselves.

  • Webhook Deleted (WEBHOOK.DELETED) — Fired when a webhook subscription is deleted

Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.