Skip to content
MoveWorkflows

Pipedream Box steps in n8n

Updated 2026-10-21 · 3 min read · n8n: Box (Native n8n node)

Box workflows on Pipedream are document pipelines: a new upload is sent for review, a signed contract is archived, a folder event posts to Teams. n8n has a native Box node and a webhook Box Trigger with a long event list, so Pipedream's Instant sources map directly.

The n8n side

Box node (n8n-nodes-base.box):

Resource Operations
File Copy, Delete, Download, Get, Search, Share, Upload
Folder Create, Delete, Get, Search, Share, Update

Box Trigger (webhook, about 36 events), for example:

  • File: Uploaded, Copied, Moved, Renamed, Downloaded, Previewed, Locked, Unlocked, Trashed, Restored, Deleted
  • Folder: Created, Copied, Moved, Renamed, Downloaded, Trashed, Restored, Deleted
  • Comment: Created, Updated, Deleted
  • Collaboration: Created, Accepted, Rejected, Removed, Updated
  • Shared link, metadata instance and task assignment events

The trigger needs a Target Type (file or folder) and Target ID.

What maps where

Pipedream (app box) In n8n Status
Upload a File File → Upload manual
Download File File → Download manual
Create Folder Folder → Create manual
Search Content File → Search / Folder → Search manual
List Folder Items HTTP Request → folder items manual
Create Shared Link File → Share / Folder → Share manual
Get File Text, Create Box Sign Request HTTP Request with the Box credential manual
New File Event (Instant) Box Trigger, Target Type folder, file events manual
New Folder Event (Instant) Box Trigger, folder events manual
New Event (Instant) Box Trigger with the events you used manual

The converter has no Box mapping yet. Each step is a placeholder with its props in a comment, and the trigger a Manual Trigger naming the source.

Box credentials in n8n

Box OAuth2. For self-hosted n8n: Box Developer Console → Create Custom App → User Authentication (OAuth 2.0) → add n8n's redirect URL → copy Client ID and Secret. Grant the scopes your steps need (read/write files, manage webhooks for the trigger).

Typical migration: new contract to signature

Pipedream: Box New File Event (Instant) on /Contracts → Box Create Box Sign Request. n8n: Box Trigger (Folder, Target ID of /Contracts, event File Uploaded) → HTTP Request POST /2.0/sign_requests with the Box credential (signers, source file ID from the trigger).

Box migration pitfalls

  • Rate limits. 1,000 API requests per minute per user, 240 uploads per minute per user; search is capped at 6 per second and 60 per minute per user. A loop that searches per item hits this quickly.
  • Webhook per target. Box webhooks are bound to one file or folder. A Pipedream source on several folders becomes several triggers, or one trigger on a parent folder plus a path filter.
  • Old webhooks. Delete Pipedream's webhooks after the switch (HTTP Request GET /2.0/webhooks, then delete), or both fire.
  • IDs. Box IDs are numeric strings; keep them as text.

How to move your Box workflows

  1. Export from Pipedream.
  2. Upload on /convert; the free report lists every Box step and its props.
  3. Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide. Related: Dropbox, Google Drive, Microsoft OneDrive.

FAQ

Does n8n have a Box trigger?
Yes. The Box Trigger is webhook-based and offers events such as File Uploaded, File Moved, File Trashed, Folder Created, Comment Created and Collaboration events, on a target file or folder ID.
Where do I find the Target ID?
It is the number after folder/ (or file/) in the Box web URL.
What credential does Box need in n8n?
OAuth2 only. Self-hosted n8n needs a Box Custom App with n8n's redirect URL; n8n Cloud connects in the browser.
Do Box steps convert automatically?
No. Each step arrives as a placeholder with its props (folder ID, file name), and the trigger as a Manual Trigger naming the Pipedream source.

Related

Sources