Resources · Make integration

CSV Box Make integrationAutomate CSV Box with Make.

Can Make move your CSV files into CSV Box without a line of code? The CSV Box Make integration gives you 3 action modules and no trigger. This guide shows ops teams how to link the account, start a scenario from another app, and test it safely.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the CSV Box Make integration do?

The CSV Box Make integration gives a Make scenario, the automation you build as a chain of bricks called modules, a way to send CSV files to your CSV Box account and call its API. It offers 3 actions and nothing that starts a scenario by itself, so another app or a schedule has to kick things off.

Files that land in CSV Box without a manual upload. Say a partner drops a spreadsheet export in a shared folder. A module from that folder app starts the scenario, and Upload CSV file hands the file to CSV Box. The team stops dragging files by hand.

An import step you can chain. Import CSV file sits next to the upload module, so an order-processing flow can pass a file along and let CSV Box take over from there. The module names tell you what each does; the official directory gives no longer description, so test each one with your own file before relying on it.

Anything else the API allows. Make an API call reuses the same connection to reach any endpoint of the CSV Box API. That is your fallback when the two file modules stop short of what you need.

What Make does not do here: there is no trigger, so CSV Box cannot tell Make that something happened on its side. The Make doc page for CSV Box also carries a warning that it was generated with AI help and should be checked against the vendor documentation. If you are weighing platforms, read n8n vs Make; for plan limits, see Make pricing, and if you would rather have the flow built for you, the Make agency page explains how the team works.

Connect

How do you connect CSV Box to Make?

  1. 01

    Copy your API keys from CSV Box

    In CSV Box, click your profile name in the navigation menu, open Profile, then the API Keys tab. You need both the API Key and the Secret API Key, so keep that tab open while you switch to Make.

  2. 02

    Add a CSV Box module in Make

    In your Make scenario, add any CSV Box module and click Create a connection. A connection is your CSV Box account linked to Make once, then reused by all three modules. The Connection name field is optional; a clear name helps later.

  3. 03

    Paste the keys and save

    Enter the credentials you copied from CSV Box, or follow the on-screen instructions Make shows. Once saved, the connection appears in the module and every other CSV Box module can pick it from the list without asking again.

First scenario

Your first scenario with CSV Box

GoalWhen a new CSV file shows up in another app, Make uploads it to CSV Box.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since CSV Box has no trigger, this first bubble belongs to the app where your file starts.

  2. 02

    Pick the starting module

    Search the app that holds the file, choose its module, and click Create a connection for that account. Fill its fields; Make lists the folders or objects it can read once connected.

  3. 03

    Add Upload CSV file

    Click the + on the right of the first module, search CSV Box, and pick Upload CSV file. Select your CSV Box connection, then map the file coming from the previous module into it.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open each module to read the bundles it received, a bundle being one item passed along, here your file.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which defaults to every 15 minutes, and switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What the CSV Box modules do

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

CSV Box1

Import CSV file

ActionIn the docs only

Judging by its name, it starts a CSV import in CSV Box from inside a scenario, so the file no longer waits for someone to push it through by hand. No official description goes further, so read the fields Make shows once your connection is set.

When to use it
when your flow is about bringing a file into CSV Box rather than just storing it there.
Watch out
test it with Run once on a sample file and read the output bundle before you trust it on real data.
CSV Box2

Make an API call

ActionIn the docs only

This one opens the whole CSV Box API to your scenario while keeping the connection you already set up. Whatever the two file modules do not cover, you can still reach through a direct request to an endpoint of the API.

When to use it
when neither Import CSV file nor Upload CSV file matches the step you need.
Watch out
you write the request yourself, so keep the CSV Box API reference open to get the endpoint right.
CSV Box3

Upload CSV file

ActionIn the docs only

As the name says, it hands a file to CSV Box straight from the previous module, so you skip the manual upload. It is the natural first action after a module from another app has picked up a spreadsheet export, a partner file or a download.

When to use it
when a file reaches you somewhere else and belongs in CSV Box.
Watch out
on the Free plan Make handles files up to 5 MB, so a large export may need a paid plan.
Need help

Need help automating CSV Box with Make?

A person reads every message.

FAQ

CSV Box and Make: common questions

01Is the CSV Box Make integration free?
Yes, on the Make side. CSV Box is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and allow 40 minutes per run. Your CSV Box subscription is separate, and its own pricing page covers it.
02What do you need to connect CSV Box to Make?
An active CSV Box account and two keys: the API Key and the Secret API Key. You find them in CSV Box by clicking your profile name, then Profile, then the API Keys tab. In Make, add a CSV Box module, click Create a connection, optionally give it a name, and paste the credentials. That single connection is then reused by all three CSV Box modules in any scenario you build.
03Does the CSV Box Make integration react in real time?
No, because it has no trigger at all. A CSV Box scenario has to start from something else: a trigger from another app, such as a module that watches the place where your files arrive, or the schedule on the first module, which runs every 15 minutes by default. On the Free plan the shortest gap between scheduled runs is 15 minutes; paid plans go down to 1 minute. Pick the starting app with that in mind.
04What if the CSV Box module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the CSV Box API with the connection you already created, so you are not limited to Import CSV file and Upload CSV file. You write the request yourself from the vendor's API reference. Since the Make doc page for this app notes that it was produced with AI help, check important details against the CSV Box documentation or ask CSV Box directly.
05Should you use Make or n8n for CSV Box?
It depends on the tool you already run, not on a verdict about either one. Make gives you 3 CSV Box modules, a connection built on your two API keys, and a visual editor where you test with Run once. The same app often has an n8n node too, so check what is available there for your case. Compare the two on the modules you actually need and on the platform your team already knows.