Resources · n8n integration

Box n8n integrationAutomate Box with n8n.

Box stores the documents, n8n decides what happens to them. The Box n8n integration covers 13 operations across 2 resources, files and folders, from upload and search to sharing and folder updates. The Box Trigger listens to 36 events sorted into 8 families. Useful the day filing by hand stops scaling.

Try the Box integration on n8nSee the 13 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Box n8n integration actually do?

The Box n8n integration is made of two nodes. The Box node acts on your Box account: it uploads, copies, downloads, searches, shares and deletes files, and creates, reads, searches, shares, updates and deletes folders. That is 13 operations over 2 resources. The Box Trigger works the other way around: it starts a workflow when something happens in Box, across 36 events grouped in 8 families, and it works by webhook, which means Box calls an n8n URL and the event lands in seconds.

Start with the case most teams hit first. A supplier emails an invoice, a form collects a signed document, a scraper produces a report. The workflow ends with file.upload into the right folder, and folder.create builds that folder first when the client is new. From there a row in Google Sheets keeps a plain index of what was filed and when, so nobody has to browse Box to answer a simple question.

The second case runs on the trigger. Turn on the Box Trigger, tick the events you care about, and Box becomes the thing that starts your workflows. A file dropped in a watched folder fires FILE.UPLOADED, a renamed document fires FILE.RENAMED, a collaborator invited to a folder fires COLLABORATION.CREATED. Route those into Slack and the people who need to know find out without anyone forwarding a link.

The third case is access. file.share and folder.share create a collaboration with a user or a group, with a Role that decides how much they can do, from Viewer to Co-Owner. Expires At in the Options collection removes that collaboration automatically on a date you set, which is exactly what a project that ends on a known day needs. Pair it with folder.update to rename or move the folder once the project closes.

Two things are worth knowing before you build. Search results are paginated: leave Return All off and the node stops at the number set in Limit, turn it on and n8n walks the pages until everything is back. And anything outside the 13 catalog operations goes through the HTTP Request node, which calls any Box API endpoint while reusing the same credential through predefined authentication.

If you are weighing Box against another cloud drive in the same workflow, the Google Drive node follows the same shape and both can live side by side in one flow. Newer to the platform itself, the n8n review goes through what the tool is good at and where it gets in the way.

Connect

How do you connect Box to n8n?

  1. 01

    Create your Box account and a Custom App

    A Box account is the only prerequisite. The Box credential authenticates with OAuth2, the flow where you approve access in a browser instead of pasting a key around. If you want to configure that flow yourself, Box asks you to create a Custom App first, and its OAuth2 setup guide walks through what happens at each redirect. Keep that app open in a tab, you will come back to it.

  2. 02

    Add the Box credential in n8n

    In n8n, open the Credentials menu and create a Box credential. A credential is created once and reused everywhere: the same one authenticates both the Box node and the Box Trigger, and every workflow you build afterwards picks it from a dropdown. You do not create a second credential for the trigger, and you do not paste anything into the node itself.

  3. 03

    Drop a node in and pick a resource

    Add the Box node to a canvas, choose the credential, then pick the resource: File or Folder. The operation list changes with it, seven operations under File and six under Folder. For the trigger side, add the Box Trigger instead, select the events you want under Events, and activate the workflow. n8n registers the webhook URL with Box at activation.

Triggers

What starts a workflow from Box ?

Box Trigger is the node that starts a workflow when something happens in Box. It listens to 36 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Box account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

FILE.*11
  • FILE.
    • COPIED
    • DELETED
    • DOWNLOADED
    • LOCKED
    • MOVED
    • PREVIEWED
    • RENAMED
    • RESTORED
    • TRASHED
    • UNLOCKED
    • UPLOADED
FOLDER.*8
  • FOLDER.
    • COPIED
    • CREATED
    • DELETED
    • DOWNLOADED
    • MOVED
    • RENAMED
    • RESTORED
    • TRASHED
COLLABORATION.*5
  • COLLABORATION.
    • ACCEPTED
    • CREATED
    • REJECTED
    • REMOVED
    • UPDATED
COMMENT.*3
  • COMMENT.
    • CREATED
    • DELETED
    • UPDATED
METADATA_INSTANCE.*3
  • METADATA_INSTANCE.
    • CREATED
    • DELETED
    • UPDATED
SHARED_LINK.*3
  • SHARED_LINK.
    • CREATED
    • DELETED
    • UPDATED
TASK_ASSIGNMENT.*2
  • TASK_ASSIGNMENT.
    • CREATED
    • UPDATED
WEBHOOK.*1
  • WEBHOOK.
    • DELETED

Configuration notes

01Configure the Box TriggerThe Box Trigger starts a workflow when Box events occur. It runs on a webhook, an URL that Box calls the moment something happens, so events arrive within seconds and nothing is polled on a schedule. n8n registers that URL with Box when you activate the workflow.

The Box Trigger starts a workflow when Box events occur. It runs on a webhook, an URL that Box calls the moment something happens, so events arrive within seconds and nothing is polled on a schedule. n8n registers that URL with Box when you activate the workflow.

Key parameters

  • Events: the list of events to listen to. Tick one, tick a family, or tick all 36. There is no catch-all wildcard here, so an event you did not tick simply never starts the workflow.
  • Target Type: whether the item being watched is a file or a folder.
  • Target ID: the Box ID of that item, which scopes the trigger to one file or one folder instead of the whole account.
When to use it
any time Box is the place where work appears first, a client folder, an upload inbox, a shared deliverables tree.
02File eventsThe biggest family, 11 events, covers the full life of a document. FILE.UPLOADED fires when a file is uploaded to or moved into the watched folder, which makes it the natural entry point for an intake workflow. FILE.COPIED, FILE.MOVED and FILE.RENAMED track a document changing place or name. FILE.TRASHED and FILE.DELETED both fire when a file goes to the trash, and FILE.RESTORED when it comes back out.

The biggest family, 11 events, covers the full life of a document. FILE.UPLOADED fires when a file is uploaded to or moved into the watched folder, which makes it the natural entry point for an intake workflow. FILE.COPIED, FILE.MOVED and FILE.RENAMED track a document changing place or name. FILE.TRASHED and FILE.DELETED both fire when a file goes to the trash, and FILE.RESTORED when it comes back out.

Three more are about people rather than storage. FILE.PREVIEWED and FILE.DOWNLOADED say a document was actually opened or taken away. FILE.LOCKED and FILE.UNLOCKED say someone claimed or released editing rights on it.

When to use it
intake pipelines, audit trails on sensitive documents, and any process where a file arriving is the signal to do the next thing.
03Folder eventsEight events mirror the file family one level up. FOLDER.CREATED fires when a folder is created, which is often the first sign that a new client, project or case has started. FOLDER.COPIED, FOLDER.MOVED and FOLDER.RENAMED follow reorganizations, the kind that quietly break every link someone saved last quarter.

Eight events mirror the file family one level up. FOLDER.CREATED fires when a folder is created, which is often the first sign that a new client, project or case has started. FOLDER.COPIED, FOLDER.MOVED and FOLDER.RENAMED follow reorganizations, the kind that quietly break every link someone saved last quarter.

FOLDER.TRASHED, FOLDER.DELETED and FOLDER.RESTORED separate three different things: moved to the trash, permanently removed, and pulled back out. That distinction matters when the workflow on the other end has to decide between warning someone and undoing something. FOLDER.DOWNLOADED completes the set, and fires when a whole folder is pulled down.

When to use it
keeping a project tracker in step with the folder tree, and noticing structural changes before people start reporting broken links.
04Collaboration and shared link eventsThese two families, 5 and 3 events, are the access side of Box. On the collaboration side, COLLABORATION.CREATED fires when an invitation goes out, COLLABORATION.ACCEPTED and COLLABORATION.REJECTED when the invited person answers, COLLABORATION.UPDATED when their level of access changes, and COLLABORATION.REMOVED when it is taken away.

These two families, 5 and 3 events, are the access side of Box. On the collaboration side, COLLABORATION.CREATED fires when an invitation goes out, COLLABORATION.ACCEPTED and COLLABORATION.REJECTED when the invited person answers, COLLABORATION.UPDATED when their level of access changes, and COLLABORATION.REMOVED when it is taken away.

Shared links behave the same way with a wider blast radius: SHARED_LINK.CREATED, SHARED_LINK.UPDATED and SHARED_LINK.DELETED fire when a link to a document is created, changed or removed. A shared link reaches further than a collaboration, so it is usually the one worth watching first.

When to use it
access reviews that do not depend on someone remembering. Every one of these eight events lands in a workflow that can log it, post it to a channel, or ask a human to confirm that the access was intended, and the answer arrives while the access is still fresh rather than at the next quarterly review.
05Comment, metadata, task and webhook eventsFour smaller families close the list, 9 events between them. Comments give you 3: COMMENT.CREATED, COMMENT.UPDATED and COMMENT.DELETED, useful when review happens inside Box rather than in email.

Four smaller families close the list, 9 events between them. Comments give you 3: COMMENT.CREATED, COMMENT.UPDATED and COMMENT.DELETED, useful when review happens inside Box rather than in email.

Metadata instances give you 3 more. METADATA_INSTANCE.CREATED fires when a metadata template instance is attached to a file or folder, METADATA_INSTANCE.UPDATED when one of its values changes, METADATA_INSTANCE.DELETED when the instance goes away. If your team classifies documents with templates, this is the family that carries that signal.

Task assignments give you 2, TASK_ASSIGNMENT.CREATED and TASK_ASSIGNMENT.UPDATED. And WEBHOOK.DELETED stands alone: it fires when a webhook is deleted, which is the one event worth watching to know your own plumbing went missing.

When to use it
whenever the interesting part of a document is not the file itself but what people wrote on it, how it was classified, or who was asked to act on it. Counting all eight families back together, 11 plus 8 plus 5 plus 3 plus 3 plus 3 plus 2 plus 1, you get the 36 events the trigger can listen to.
Actions

What can the Box node do?

The Box node exposes 13 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetUpdateDeleteCopyDownloadSearchShareUpload
File✓✓✓✓✓✓✓
Folder✓✓✓✓✓✓

File

7 operations
01

Copy a file

file.copy

What you see in n8n

Notes & use cases

Duplicates a file into another folder and returns the new copy. The original stays exactly where it was.

Key parameters

  • File ID: required, the Box identifier of the file to duplicate.
  • Parent ID: the destination folder. Leave it empty and the copy lands in the root folder, which is rarely what you want.
  • Name: in Additional Fields, a new name for the copy, the clean way to avoid two identical names in one tree.
  • Version: in Additional Fields, the ID of a specific file version to copy instead of the current one.
Use cases
a signed contract stays in the deal folder while a renamed copy goes to the accounting folder, so finance never opens the draft by mistake.
02

Delete a file

file.delete

What you see in n8n

Notes & use cases

Removes a file from Box as a workflow step, which is how a cleanup stops being a Friday chore.

Key parameters

  • File ID: the file to remove. It expects the Box identifier, not the file name, so read it from a Get or Search step earlier in the flow.
Use cases
a nightly workflow clears the temporary exports a reporting job drops into Box, keeping the shared folder readable for the people who work in it every morning.
03

Download a file

file.download

What you see in n8n

Notes & use cases

Pulls the file content into the workflow as binary data, so the next node can send it, parse it or push it somewhere else.

Key parameters

  • Put Output File in Field: required, the name of the output binary field the file is placed in. Whatever you type here is what the next node has to point at.
  • File ID: which file to fetch.
Use cases
a monthly statement stored in Box is downloaded, attached to an email and sent to the client, without a person opening Box at all.
04

Get a file

file.get

What you see in n8n

Notes & use cases

Reads a single file's information and returns it as workflow data. This is the lookup step, not the content step.

Key parameters

  • File ID: the file to read.
  • Fields: in Additional Fields, a comma-separated list of attributes to include in the response. It also pulls attributes that a standard response does not return, so it is worth filling when the default payload is missing what you need.
Use cases
after a trigger fires on a document, this step gathers its details before an IF node decides whether the workflow should continue.
06

Share a file

file.share

What you see in n8n

Notes & use cases

Grants someone access to one file by creating a collaboration on it.

Key parameters

  • File ID: the file to share.
  • Accessible By: whether you are sharing with a User or a Group.
  • Use Email: on, you identify the person by Email; off, by User ID. Groups use Group ID.
  • Role: the level granted, from Viewer or Previewer up to Editor and Co-Owner, with Uploader variants for write-only access.
  • Expires At: in Options, a date at which the collaboration is removed automatically.
  • Notify: whether the person gets an email about it.
Use cases
a freelance reviewer gets Previewer access to one brief, ending the day the sprint ends.
07

Upload a file

file.upload

What you see in n8n

Notes & use cases

Puts a new file into Box, either from binary data carried by the workflow or from text you build in a previous node.

Key parameters

  • Binary File: required, tells the node whether the data comes from a binary field or from text.
  • Input Binary Field: required when Binary File is on, the name of the input binary field holding the file.
  • File Content: required when Binary File is off, the text content of the file.
  • File Name: the name the file is saved as, like photo.png.
  • Parent ID: the folder it goes into. Without it, the root folder.
Use cases
an invoice pulled from an inbox lands in that month's folder.

Folder

6 operations
08

Create a folder

folder.create

What you see in n8n

Notes & use cases

Creates a folder and returns it, which is how a workflow builds its own filing structure as it goes.

Key parameters

  • Name: required, the folder's name.
  • Parent ID: the folder it is created in. Left empty, it is created at the root.
  • Access: in Options, Collaborators accepts only registered collaborator addresses, Open accepts any address.
  • Fields: in Options, extra attributes to include in the response.
Use cases
a new deal in the CRM creates its folder tree in Box the same minute, named from the deal, so the first document has somewhere to go.
09

Delete a folder

folder.delete

What you see in n8n

Notes & use cases

Removes a folder from Box. Whether it takes its contents along is a choice you make in the node.

Key parameters

  • Folder ID: the folder to remove.
  • Recursive: off, a folder that still holds content is not deleted; on, the folder and everything inside it go. Read that switch twice before activating the workflow.
Use cases
a sandbox tree created for a test run is torn down at the end of the run, recursively, so nothing is left behind for the next person to wonder about.
10

Get a folder

folder.get

What you see in n8n

Notes & use cases

Reads one folder's information and hands it to the rest of the workflow.

Key parameters

  • Folder ID: the folder to read. This is the digits Box shows in the URL, not the label people call it by.
Use cases
before uploading, a workflow reads the target folder to confirm it still exists, then branches to Create a folder when it does not. It is also the quickest way to check that a credential really has access to the tree you think it does.
12

Share a folder

folder.share

What you see in n8n

Notes & use cases

Opens a whole folder to a person or a group, and everything inside it follows.

Key parameters

  • Folder ID: the folder to share.
  • Accessible By: User or Group, with Email, User ID or Group ID depending on Use Email.
  • Role: Viewer for read access, Uploader for write-only, Editor for full read and write, Co-Owner above that.
  • Can View Path: in Options, whether the invited person sees the parent path above the folder. It grants no rights up there, only visibility.
Use cases
onboarding a new contractor by giving their group Viewer access to the documentation folder on day one.
13

Update a folder

folder.update

What you see in n8n

Notes & use cases

Changes a folder's settings, name or place in the tree without touching what it contains.

Key parameters

  • Folder ID: required, the folder to update.
  • Name and Description: in Update Fields, the new name and the optional description.
  • Parent ID: in Update Fields, a new parent, which moves the folder or pulls it back out of the trash.
  • Is Collaboration Restricted To Enterprise: restricts new invitations to people inside the enterprise, leaving existing collaborations alone.
Use cases
a closed project folder is renamed with its end date and moved under an archive parent, in one step.
Need help

Need help automating Box with n8n?

A person reads every message.

FAQ

Box and n8n, the usual questions

01Is the Box n8n integration free?
Yes on the n8n side. The Box node and the Box Trigger ship with n8n, so there is nothing to install and nothing extra to pay for the connector itself. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both places, so you can build on one and move it to the other. What a Box account costs is a separate question and depends on your plan with Box, which this page does not cover.
02What credentials do you need to connect Box to n8n?
A Box account and a Box credential in n8n, authenticated with OAuth2. OAuth2 is the only supported method here, so there is no API key field to fill: you approve access through Box in a browser and n8n keeps the connection. If you want to set that flow up from scratch, Box asks you to create a Custom App and documents each step of the OAuth web flow. One credential covers both nodes, the Box node and the Box Trigger, and every workflow you build later selects it from a dropdown instead of repeating the setup.
03What are the limits of the Box node in n8n?
Two things shape what you get back. First, search results are paginated: with Return All off the node stops at the number you set in Limit, and with Return All on n8n keeps requesting pages until everything is returned, which is what you want for a full export and not what you want inside a loop. Second, the node exposes 13 operations across files and folders. Anything beyond those goes through the HTTP Request node, which calls any Box API endpoint and reuses the same credential through predefined authentication, so you stay in one workflow.
04Does the Box Trigger react in real time?
Yes, it works by webhook. Box calls an n8n URL the moment an event happens, and the workflow starts within seconds. n8n registers that URL with Box when you activate the workflow, so there is no schedule to configure and no interval to tune. You pick which of the 36 events you want under Events, and you can narrow the scope to a single item with Target Type and Target ID. There is no catch-all wildcard, so an event you did not tick will never start the workflow, which is worth remembering when something you expected does not fire.
05n8n or Make for Box automation?
It depends on where you want the workflow to run and how you want to pay for it. Make is a hosted platform with no self-hosting option, billed per operation, so cost tracks volume. n8n runs on Cloud or on your own server through Docker or npm, and the workflow is identical either way, which matters when documents carry client data you would rather keep on infrastructure you control. Both give you a visual canvas. If your Box volume is low and predictable, per-operation billing is simple. If it grows or the data is sensitive, self-hosting changes the math.
Same platform

Other docs you might need on this stack.

Browse all integrations