Resources · Make integration

Boxflow Make integrationAutomate Boxflow with Make.

Can Make pick up your Boxflow messages and their files without any code? Yes. The Boxflow Make integration gives you 5 modules: one trigger, three actions and one search. This page shows how to link your account and build a first working scenario.

Try the Boxflow integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Boxflow Make integration do for you?

The Boxflow Make integration links your Boxflow account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Boxflow brings 5 of those bricks, built around messages, attachments, files and workspaces.

Files that leave the inbox on their own. Start with Watch Messages, add Get Message Attachments, then Download a File. Each attachment of a new message becomes a file that the next module, from another app, can store or share.

A message history you can reuse. Get Messages pulls messages when another app asks for them, for example when a support agent opens a ticket and needs the conversation behind it.

The right workspace every time. List Workspaces returns the workspaces your account can see, so a scenario can loop over them instead of relying on one hardcoded choice.

Keep one limit in mind: the official Make documentation for Boxflow is flagged as AI-generated and gives no description of these modules. Test each one with Run once before you rely on it. If you get stuck, the Make troubleshooting guide covers common errors, and n8n vs Make helps if you are still choosing a tool. The Make training goes further on scenario design.

Connect

How do you connect Boxflow to Make?

  1. 01

    Generate an API token in Boxflow

    Open your user profile settings in Boxflow, choose the option that generates a new API token, and copy the key shown on screen. You need an active Boxflow account for this.

  2. 02

    Add a Boxflow module in Make

    In your scenario, add any Boxflow module and click Create a connection. A connection is your Boxflow account linked to Make once, then reused by every Boxflow module.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like, then paste the API key you copied and confirm. Make can now read Boxflow on your behalf.

First scenario

Your first scenario with Boxflow

GoalWhen a new message shows up in Boxflow, Make fetches its attachments and downloads the file.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the large + to place the first module on the canvas.

  2. 02

    Pick the trigger

    Search for Boxflow, choose Watch Messages, and select your connection or create it with the API key. Fill the fields Make offers once the connection exists.

  3. 03

    Chain the attachments and the download

    Click the + to the right of the trigger, add Get Message Attachments, and map the message from the previous module. Add Download a File after it and map what the attachments step returned.

  4. 04

    Test with Run once

    Click Run once, then open the bubble above each module to read the bundles it received. A bundle is one item passed along, here one message or one file.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; adjust it within your plan, then turn the scenario on.

Triggers

What starts a Boxflow scenario

1 module starts a scenario when something happens in Boxflow. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Boxflow as soon as it happens.

Boxflow1Watch Messages

Watch Messages

triggerIn the docs only

This trigger hands your scenario each new Boxflow message, so everything after it runs without you opening Boxflow. It is the only trigger in the app, which makes it the natural first module for most Boxflow scenarios.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and at 15 minutes at the shortest on the Free plan. Nothing reaches Make between two checks.
When to use it
whenever a fresh message should kick off work elsewhere, such as saving its files or notifying a colleague.
Watch out
the documentation lists this module without describing it; read the bundles after Run once to see which data it really returns.
Modules

The Boxflow modules and when to use each

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

Boxflow1

Download a File

ActionIn the docs only

Turns a Boxflow file reference into actual file data that a storage or email module from another app can take over. Judging by its name, it is usually the last Boxflow step before the file leaves the app.

When to use it
right after Get Message Attachments, when the goal is a real copy of the document somewhere else.
Watch out
on the Free plan, Make handles files up to 5 MB.
Boxflow2

Get Message Attachments

ActionIn the docs only

Gives you the attachments of one specific message, which saves you from guessing where the files are. Feed it a message coming from Watch Messages or Get Messages.

When to use it
in any scenario that cares about the files rather than the text of a message.
Watch out
the docs say nothing about how several attachments come back, so check the bundles after a first Run once.
Boxflow3

Get Messages

ActionIn the docs only

Lets a scenario read Boxflow messages on demand, in the middle of a flow, instead of waiting for a new one to arrive. Each call counts as an operation, one module run that Make adds to your plan usage.

When to use it
when another app starts the scenario and you need the Boxflow conversation linked to it.
Watch out
the official documentation gives no field list, so confirm the output in the editor.
Boxflow4

List Workspaces

SearchIn the docs only

Shows you which workspaces your Boxflow connection can reach, as a search that can return zero, one or several bundles. It keeps a scenario from breaking when someone adds a workspace.

When to use it
at the start of a flow that should cover every workspace, not just one picked by hand.
Watch out
every returned workspace runs the following modules once, which adds operations.
Need help

Need help automating Boxflow with Make?

A person reads every message.

FAQ

Boxflow and Make: common questions

01Is the Boxflow Make integration free?
Yes, on the Make side. Boxflow is a standard app, so it is available from the Free plan. That plan lets you keep 2 active scenarios, runs scheduled scenarios at 15 minutes at the shortest, stops a run after 5 minutes, handles files up to 5 MB and allows 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need your own active Boxflow account, whose pricing is set by Boxflow.
02What do you need to connect Boxflow to Make?
Two things: an active Boxflow account and an API token generated from it. In Boxflow, open your user profile settings, generate a new API token and copy the key shown on screen. In Make, add any Boxflow module, click Create a connection, optionally name it, and paste the key. That single connection then serves all 5 Boxflow modules, so you only do this once per account. The key is the only credential Make asks for.
03Does the Boxflow trigger in Make work in real time?
No. Watch Messages is a scheduled trigger: Make checks Boxflow on the scenario's schedule rather than being alerted the moment a message arrives. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest interval, while paid plans can go down to 1 minute. Keep in mind that each module run on a bundle counts as one operation on your plan, so a busy scenario uses more of it. Pick the schedule that matches how quickly you need to react.
04What if a Boxflow module you need is missing in Make?
It depends on the need. The Boxflow app in Make has 5 modules and no Make an API Call module, so you cannot send a custom request to Boxflow from inside this app. You can often reach the result by combining the existing modules with other apps. If that is not enough, the agency team can review the case with you and look for a workable route. Test any combination with Run once before you switch it on.
05Should you use Make or n8n for Boxflow?
It depends on what each tool offers for Boxflow. In Make, you get 5 ready modules today, including a scheduled trigger on new messages, and you can start on the Free plan. Many apps also have an n8n node, so check whether Boxflow has one and which operations it covers before you choose. Compare the two on the modules available for your exact use case, not on the brand. Both can coexist while you test.
Same platform

Other docs you might need on this stack.

Browse all integrations