Resources · Make integration

Box Make integrationAutomate Box with Make.

Can Make handle your Box files without anyone dragging them around? The Box Make integration gives you 32 modules: 3 triggers, 25 actions and 4 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Box integration on MakeSee the 32 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Box Make integration let you automate?

The Box Make integration links your Box account to Make, a no-code tool where you chain steps into a scenario (the automation you build). Each step is a module: something that watches Box, acts on a file or folder, or looks something up. Once it runs, files get filed, shared and tagged without you opening Box.

Contracts that go out for signature on their own. A file lands in a folder, New File Event tells Make, and Create a Sign Request sends it off. Later, List Sign Requests shows which ones are still waiting.

A tidy client space from day one. When a deal closes in your CRM, Create a Folder builds the client folder, Add a Shared Link to a Folder produces the link to send, and Create Folder Metadata Instance stamps it with the fields your team filters on.

Files that reach the right people. Watch Files spots new or updated documents in a folder, Download a File pulls the content into the scenario, and the next module in another app mails it or stores it.

What Make does not give you: a module for every corner of the Box API. When the list falls short, Make an API Call reuses your connection for any endpoint. Box also has a node in n8n, covered on the Box n8n integration page, and the n8n vs Make comparison helps you choose. New to the editor? The Make training starts from zero.

Connect

How do you connect your Box account to Make?

  1. 01

    Prepare your Box developer app

    Make talks to Box through OAuth, so you need a Box developer account. Open the Box Developer Console, click your application, go to the Configuration tab and copy the Client ID and Client secret.

  2. 02

    Add a Box module and create the connection

    In your scenario, add any Box module and click Create a connection. A connection is your Box account linked to Make once, then reused by every Box module. Give it a clear name in Connection name if you manage several accounts.

  3. 03

    Paste the credentials and approve

    Enter the Client ID and Client secret you copied, or follow the on-screen instructions, then approve access in the Box window. Once it closes, Make can list your folders in every Box module.

First scenario

Your first scenario: share every new file in a Box folder

GoalWhen a file is added or updated in a watched Box folder, Make creates a shared link to it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. That empty canvas is where every module of your automation will sit, left to right.

  2. 02

    Add Watch Files and connect Box

    Search for Box, pick Watch Files, then click Create a connection and follow the three steps above. Make now lists the folders it can read, so choose the one to keep an eye on.

  3. 03

    Add the shared link action

    Click the + to the right of Watch Files and add Add a Shared Link to a File. Map the file coming from the trigger, so each new document gets its own link.

  4. 04

    Test with Run once

    Drop a test file in the folder and click Run once. Each module shows the bundles it received (a bundle is one item passing through, here one file), so you can check the link was created.

  5. 05

    Schedule it and switch it on

    Open the clock on Watch Files. A new scenario checks every 15 minutes by default; paid plans can go down to 1 minute. Save, then turn the scenario on.

Triggers

What can start a Box scenario?

3 modules start a scenario when something happens in Box. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Box as soon as it happens.

Box1New File Event

New File Event

Instant trigger

In Make“Triggers when selected actions occurs on a file.”

This trigger starts your scenario the moment something you selected happens to a file in Box. You decide which actions count, so the scenario reacts to exactly the file events you care about and ignores the rest.

How it fires
instant. Box calls Make through a webhook as soon as it happens, which is why this module wears the lightning badge.
When to use it
a contract dropped by a client should trigger a signature request or an alert without waiting for the next check.
Watch out
click Create a webhook first, then Create a connection: that is the order Make expects for instant modules.
Box2New Folder Event

New Folder Event

Instant trigger

In Make“Triggers when selected actions occurs on a folder.”

Here the watch moves up a level: Make hears about the actions you picked on folders rather than on single files. Handy when your team works folder by folder, one per client, project or deal.

How it fires
instant. Box notifies Make through a webhook as soon as the folder event occurs.
When to use it
someone creates a project folder and you want Create Folder Metadata Instance to tag it straight away, so nobody has to remember.
Watch out
it sees folder activity only; for changes to the documents inside, pair it with New File Event or Watch Files.
Box3Watch Files

Watch Files

Scheduled trigger

In Make“Triggers when a new file is added or an existing file is updated in a folder being watched.”

Watch Files keeps an eye on one folder and hands Make every file that is new or updated there since the last check. Each file becomes a bundle, so the next modules run once per document.

How it fires
scheduled. Make checks Box on the scenario's schedule, every 15 minutes by default, with the clock badge on the module.
When to use it
an inbox folder where suppliers leave invoices and a short delay costs nothing.
Watch out
on the Free plan the shortest interval is 15 minutes, so a file can wait until the next run. If that matters, switch to New File Event.
Modules

What can Make do in Box?

Box gives you 29 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Box1

Add a Shared Link to a File

Action

In Make“Adds a shared link to a file”

Turns any file into a link you can paste in an email, a CRM record or a Slack message. The scenario gets the link back and passes it to the next module.

When to use it
a quote PDF is ready and the client needs to read it without a Box account.
Watch out
the link exposes the file to whoever holds it, so keep this module away from folders with sensitive documents.
Box2

Add a Shared Link to a Folder

Action

In Make“Adds a new shared link to a folder.”

Same idea one level up: the whole folder gets a link, and everything you add later travels with it. One link per client space is easier to manage than one per document.

When to use it
right after Create a Folder, to send a new client one address for all their deliverables.
Watch out
anything saved to that folder later becomes visible through the same link.
Box3

Cancel a Sign Request

Action

In Make“Cancels a sign request by its ID.”

Stops a signature request that is still open, using its ID. The signers no longer have anything to sign, which avoids someone approving an outdated version.

When to use it
a deal is lost or the contract was replaced, and the old request should vanish before anyone signs it.
Watch out
the module needs the request ID; get it from Create a Sign Request or List Sign Requests earlier in the scenario.
Box4

Copy a Folder

Action

In Make“Copies the selected folder.”

Duplicates the folder you point to, contents included, so a model structure can be reused as many times as needed. Your template folder stays untouched.

When to use it
every new project starts with the same subfolders (brief, drafts, final), and you keep one master copy in Box.
Watch out
point the module at the template, not at a live client folder, or you will clone someone's documents into the new project.
Box5

Create a Comment

Action

In Make“Creates a new comment to a file.”

Writes a comment on a file, as if a teammate had left a note in the Box sidebar. People who open the document see it right away, no separate message needed.

When to use it
a review step in another tool finishes, and you want the verdict posted where the file lives.
Watch out
the comment is posted with your connected account, so readers see your name on it.
Box6

Create a Folder

Action

In Make“Creates a new empty folder within the specified parent folder.”

Builds an empty folder inside the parent you choose. The scenario gets the new folder's details back, ready for sharing, tagging or uploads in the next modules.

When to use it
a form is submitted or a deal is won, and each new client needs a home in Box named after them.
Watch out
run a Search for Content first if the same event can fire twice, or you will end up with duplicate folders.
Box7

Create a Sign Request

Action

In Make“Creates a sign request.”

Sends a document out for signature straight from the scenario. The request lives in Box, and its ID comes back so later modules can track or cancel it.

When to use it
a contract is generated and saved to Box, and the next move is always the same: get it signed.
Watch out
store the returned ID somewhere, such as a spreadsheet row, so Get a Sign Request can find it again.
Box8

Create File Metadata Instance

Action

In Make“Applies an instance of a metadata template to a file.”

Applies one of your Box metadata templates to a file and fills it in. The document becomes searchable and filterable by values like client, status or amount.

When to use it
an uploaded invoice should carry the supplier and due date your finance team filters on.
Watch out
the template has to exist in Box before the scenario runs. If the file already has that template, reach for Update File Metadata instead.
Box9

Create Folder Metadata Instance

Action

In Make“Applies an instance of a metadata template to a folder.”

Stamps a folder with a metadata template, so the whole space carries labels your team can sort on. Useful when the folder, not the file, is the unit you manage.

When to use it
a client folder was just created, and you want the account manager and contract type recorded on it.
Watch out
this module creates the first set of values. Once the template sits on the folder, later changes go through Update Folder Metadata.
Box10

Delete a File

Action

In Make“Deletes a file or moves it to trash.”

Removes a file, either for good or by sending it to the trash. It is the cleanup step at the end of a scenario that has already copied or processed the document.

When to use it
a draft was converted and archived elsewhere, and the original only clutters the working folder.
Watch out
test with Run once on a dummy file first. A permanent delete cannot be undone from Make.
Box11

Delete a Folder

Action

In Make“Deletes a folder, either permanently or by moving it to trash.”

Gets rid of an entire folder, with the choice between permanent deletion and the trash. Everything inside goes with it.

When to use it
a project is closed and archived, and its working folder should disappear from everyone's view.
Watch out
prefer the trash option while you build the scenario. One wrong mapping and a whole client space is gone, so check the folder ID in the bundle before activating.
Box12

Download a File

Action

In Make“Downloads a file.”

Pulls the actual content of a file into the scenario, not just its details. After this step, another app can attach, convert or store the document.

When to use it
a PDF arrives in Box and must be emailed as an attachment or pushed to an accounting tool.
Watch out
on the Free plan Make handles files up to 5 MB, and every download counts toward the 512 MB of data transfer.
Box13

Get a File

Action

In Make“Retrieves information about a file.”

Reads the information Box keeps about a file without touching the content. Think of it as a quick look before deciding what to do next.

When to use it
a trigger gives you only an ID and the next step needs the file's name to decide what happens.
Watch out
no content comes back here. If the next app needs the document itself, use Download a File.
Box15

Get a Folder

Action

In Make“Retrieves information about a folder, including the first 100 entries in that folder.”

Returns a folder's information along with the first one hundred entries it holds. Enough to check what is inside before a scenario copies, renames or deletes anything.

When to use it
you want to know whether a client folder already has a signed contract before sending a new one.
Watch out
only the first one hundred entries come back. For a full listing of a busy folder, Get Folder Items is the better choice.
Box16

Get a Sign Request

Action

In Make“Retrieves a sign request by its ID.”

Looks up one signature request by its ID and brings back what Box knows about it. The scenario can then decide whether to wait, remind someone or move on.

When to use it
a deal record in your CRM should flip to signed once the contract request is complete.
Watch out
without the ID, this module cannot find the request; List Sign Requests is the way to recover it.
Box17

Get Folder Metadata

Action

In Make“Retrieves a folder metadata by its ID.”

Reads the metadata stored on a folder, so the values your team entered become data for the rest of the scenario. Status, owner or region can then steer what happens next.

When to use it
before sending a report, the scenario checks which account manager is recorded on the client folder.
Watch out
a folder without that template returns nothing useful; plan a fallback route.
Box18

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Your way out when no listed module does the job. It sends a request of your choice to the Box API, reusing the connection you already created.

When to use it
you need a Box feature that none of the other listed modules covers, and you have the Box API reference open.
Watch out
you build the request yourself, so reading the API reference is part of the job.
Box19

Rename a File

Action

In Make“Renames a file.”

Gives a file a new name built from data in the scenario: a client name, an invoice number, a date from another app. Naming rules stop depending on who uploaded the file.

When to use it
scans arrive as random strings, and your team searches Box by client and invoice number.
Watch out
map the new name from the scenario data, not typed by hand, or every file ends up with the same name.
Box20

Rename a Folder

Action

In Make“Renames a folder.”

Changes a folder's name without moving it or touching its contents. Shared links and metadata stay in place, only the label changes.

When to use it
a prospect becomes a client, and the folder name should switch from the prospect label to the final account name.
Watch out
anyone who searches for the old name will not find it anymore, so let the team know about the convention.
Box21

Update a File

Action

In Make“Updates file attributes.”

Edits the attributes Box stores on a file without replacing what is inside. The file keeps its ID and history.

When to use it
a document is approved in another tool, and its attributes in Box should reflect that.
Watch out
this changes attributes, not content. To push a new version of the document itself, use Upload a File.
Box22

Update a Folder

Action

In Make“Updates folder attributes.”

Adjusts the attributes Box stores on a folder in one step. The folder stays the same object, so links pointing to it keep working.

When to use it
a project closes in your project tool, and the matching Box folder should carry the change.
Watch out
for a plain name change, Rename a Folder is simpler and harder to misconfigure.
Box23

Update File Metadata

Action

In Make“Creates or Updates Metadata of a File.”

Creates or changes the metadata values on a file, so a label follows the document's life: received, checked, paid. Box filters stay accurate without manual edits.

When to use it
an invoice gets paid in your accounting app and its status in Box should say so.
Watch out
match the exact template and field keys set up in Box, or the update will miss its target.
Box24

Update Folder Metadata

Action

In Make“Updates folder's metadata.”

Refreshes the metadata already stored on a folder. The folder-level labels your team relies on stay in step with what happens in other tools.

When to use it
a project moves from active to closed in your project tool, and the Box folder should reflect it.
Watch out
it edits existing metadata; a folder without the template needs Create Folder Metadata Instance first.
Box25

Upload a File

Action

In Make“Uploads a new file.”

Drops a new file into the Box folder you choose, using a file produced earlier in the scenario: an email attachment, a generated PDF, an export.

When to use it
invoices arrive by email and belong in a finance folder instead of someone's inbox.
Watch out
the module needs real file data from a previous step, not just a link. On the Free plan, keep each file under 5 MB.
Box26

Get File Metadata

Search

In Make“Retrieves a file metadata by its ID.”

Fetches the metadata attached to a file by its ID, so the labels stored in Box can drive decisions in the scenario. It works as a search: expect zero, one or several results.

When to use it
a file changes and you want to read its client or amount before notifying the right person.
Watch out
an empty result is normal for untagged files; add a filter so the next modules do not run on nothing.
Box27

Get Folder Items

Search

In Make“Retrieves files, folders, and web links in a folder.”

Lists what a folder contains: files, subfolders and web links. Each item comes out as its own bundle, so every following module runs once per item.

When to use it
a folder should be swept, and each document inside renamed, tagged or copied.
Watch out
a busy folder means many bundles, and each module run on each bundle is one operation on your plan.
Box28

List Sign Requests

Search

In Make“Retrieves all sign requests.”

Brings back every signature request on the account, which gives you the full picture without opening Box. Each request becomes a bundle you can filter.

When to use it
you want a recap of contracts still waiting for a signature, sent to the sales team.
Watch out
add a filter right after this module, or every following step runs on every request, signed or not.
Box29

Search for Content

Search

In Make“Searches for items that are available to the user or an entire enterprise.”

Finds files and folders the connected user can see, or across a whole enterprise account. Use it when you know what you want but not where it sits.

When to use it
before creating a client folder, check whether one with that name already exists.
Watch out
a search can return several matches; add a filter or limit before acting on the results. Stuck on odd outputs? See Make troubleshooting.
Need help

Need help automating Box with Make?

A person reads every message.

FAQ

Box and Make: common questions

01Is the Box Make integration free?
Yes, Box is a standard app in Make, so it works on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Your Box subscription is a separate matter, handled on the Box side.
02What do you need to connect Box to Make?
You need a Box developer account and OAuth 2.0 credentials. In the Box Developer Console, open your application, go to the Configuration tab and copy the Client ID and Client secret. If a callback URI is requested, the Make documentation gives the exact address to enter. In Make, add a Box module, click Create a connection, optionally name it, then paste the credentials or follow the on-screen steps. For an instant trigger, click Create a webhook first.
03Does the Box trigger in Make react in real time?
It depends on the trigger you pick. New File Event and New Folder Event are instant: Box calls Make through a webhook as soon as the selected action happens. Watch Files is scheduled: Make checks the folder on the scenario's schedule, every 15 minutes by default. On the Free plan that interval cannot go below 15 minutes; paid plans go down to 1 minute. If a few minutes of delay is a problem, choose one of the two instant triggers.
04What if the Box module you need is missing in Make?
Use Make an API Call. It sends any request to the Box API with the connection you already set up, so you can reach endpoints the listed modules leave out. You write the request yourself, which means keeping the Box API reference nearby. The Make documentation for Box lists no specific limits for these modules, so check the Box side when a call fails. If the scenario keeps breaking, a dedicated troubleshooting guide for Make helps sort the cause.
05Make or n8n: which one should run your Box automations?
It depends on where your other automations already run. Box has a node in n8n as well, so neither tool locks you out. In Make you get 32 ready modules covering triggers, files, folders, metadata and sign requests, plus Make an API Call for the rest. Compare the modules you actually need on both sides, and pick the tool your team already maintains. In Make, your Box account is linked once as a connection, and every Box module in your scenarios reuses it.
Same platform

Other docs you might need on this stack.

Browse all integrations