Resources · Make integration

Wasabi Make integrationAutomate Wasabi with Make.

Want files from your other apps to land in Wasabi storage on their own? The Wasabi Make integration gives you 5 modules: 4 actions and 1 search. This guide shows how to link your account, build a first backup scenario and pick the right module for each job.

Try the Wasabi integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Wasabi Make integration automate?

The Wasabi Make integration lets a Make scenario, the automation you build as a chain of bricks, store files in your Wasabi buckets and read them back without you opening Wasabi. Each brick is called a module, and Wasabi brings five of them: upload, download, list, create a bucket, plus a free-form API call.

Keep a copy of every incoming file. An online store receives invoices, signed forms or product photos in another tool. That tool's module starts the scenario, and Upload a File drops each file into the bucket you chose, so the archive grows without anyone dragging files around.

Give each new client its own storage. When a deal is marked as won in your CRM, or a new record appears in a base covered by the Airtable Make integration, Create a Bucket opens a fresh bucket for that account, ready to receive deliverables.

Send stored files where people work. List Files returns what sits in a path, then Get a File downloads each item so the next module can attach it to an email or post it to a shared drive.

Know the edges before you start. Wasabi has no trigger module, so it cannot start a scenario on its own: another app or the scenario's schedule does that. Anything the five modules leave out goes through Make an API Call. Many apps also exist as n8n nodes; if you are weighing both tools, the n8n vs Make comparison lays out the criteria, and the Make training walks through the editor step by step.

Connect

How do you connect your Wasabi account to Make?

  1. 01

    Create an access key in Wasabi

    In your Wasabi account, open Access Keys in the left menu and click Create Access Key. Choose Root User or Sub-User depending on your needs, click Create, copy the API key, then click Show to reveal and copy the Secret Key.

  2. 02

    Open the connection window in Make

    Add any Wasabi module to your scenario and click Create a connection. A connection is your Wasabi account linked to Make once and reused by every Wasabi module. The Connection name field is optional, but a clear name helps when you run several accounts.

  3. 03

    Paste both keys and save

    Enter the API key and the Secret Key you copied from Wasabi, or follow the instructions Make shows on screen. Once saved, the connection appears in the module's dropdown, and Make can start reading what your account holds.

First scenario

Your first scenario: back up incoming files to Wasabi

GoalWhen a new file shows up in another app, Make uploads a copy of it into your Wasabi bucket.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big +. The first module you place here decides when the scenario starts, so pick the app where your files arrive.

  2. 02

    Set the starting module

    Search for that app, choose the module that watches for new files and link your account with Create a connection. Each file it finds becomes a bundle, one item passed along to the next module.

  3. 03

    Add Upload a File

    Click the + on the right of the first module, search for Wasabi and pick Upload a File. Pick your Wasabi connection. Once it works, Make lists your buckets and you choose one.

  4. 04

    Map the file

    In the file field, map the file coming from the first module instead of typing anything. Make shows the previous module's data in a panel, so you just click the item you need.

  5. 05

    Test with Run once

    Click Run once, drop a test file in the source app and watch the run. Open the bubble above each module to read the bundles it received, then check that the file sits in your bucket.

  6. 06

    Schedule and switch on

    Open the clock on the first module to set the schedule, which is every 15 minutes by default, then switch the scenario on. From now on, each new file gets its copy in Wasabi.

Modules

What the Wasabi modules do

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

Wasabi1

Create a Bucket

Action

In Make“Creates a new bucket.”

You get a brand new Wasabi bucket, created from inside the scenario, so storage for a new project or client exists before the first file needs it.

When to use it
right after a signed quote or a new customer record, so the matching bucket opens without a trip to the Wasabi console.
Watch out
each run makes a new bucket, so place this module behind a step that fires once per client, never inside a loop over files.
Wasabi2

Get a File

Action

In Make“Downloads a file from a bucket.”

Pulls one file out of a bucket and hands it to the next module, which can then attach it to a message or pass it to another storage tool.

When to use it
a colleague asks for an older report stored in Wasabi and you want the scenario to fetch and forward it.
Watch out
on the Free plan Make handles files up to 5 MB and 512 MB of transfer, so check the size of big archives before you count on this module.
Wasabi3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the Wasabi API from your scenario, reusing the same connection, for the jobs the four other modules do not cover.

When to use it
you need a Wasabi feature that has no dedicated module and you have the API reference open next to Make.
Watch out
you write the request yourself, so read Wasabi's API documentation first; Make fills in nothing for you here beyond the authorization.
Wasabi4

Upload a File

Action

In Make“Uploads a file to a bucket.”

Stores a file in the bucket you choose, which turns any tool that produces files into a source for your Wasabi archive.

When to use it
invoices, contracts or exports generated elsewhere should end up in one place, in a copy nobody has to make by hand.
Watch out
the module needs a real file from an earlier module; map it from the data panel, and remember the 5 MB file ceiling on the Free plan.
Wasabi5

List Files

Search

In Make“Lists all files in the specified path.”

Shows you what sits in a given path of a bucket, returning each file as its own bundle so later modules can act on them one by one.

When to use it
before Get a File, when you need every file of a client folder rather than a single name you already know.
Watch out
a search can return zero, one or many bundles, and each module after it runs once per bundle, which counts one operation each time.
Need help

Need help automating Wasabi with Make?

A person reads every message.

FAQ

Wasabi and Make: common questions

01Is the Wasabi Make integration free?
Yes, on Make's side. Wasabi is a standard app, so its modules are available from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Your Wasabi account is billed separately by Wasabi, so check their own pricing page for storage costs.
02What do you need to connect Wasabi to Make?
You need an active Wasabi account and API credentials from it. In Wasabi, open Access Keys, click Create Access Key, pick Root User or Sub-User, then copy the API key and the Secret Key revealed by the Show link. In Make, add a Wasabi module, click Create a connection, give it a name if you like and paste both keys. That single connection then serves all five Wasabi modules in any scenario you build.
03Can Wasabi trigger a Make scenario in real time?
No. Wasabi has no trigger module in Make, so nothing in Wasabi can start a scenario by itself. You have two ways around it. Start the scenario with a module from another app, the one where files or records first appear, and let Wasabi act second. Or start it with List Files and let the scenario's schedule decide when it runs, every 15 minutes by default on a new scenario and never under 15 minutes on the Free plan.
04What if the Wasabi module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Wasabi API with the connection you already set up, so a feature without a dedicated module stays within reach. You write the request yourself, which means keeping Wasabi's API reference at hand. Also note that Make's help page for Wasabi is flagged as AI-generated and may contain mistakes, so when a detail looks off, confirm it with Wasabi before building around it.
05Should you use Make or n8n for Wasabi?
It depends on the tool your team already knows. In Make, Wasabi comes with 5 modules and Make an API Call for anything beyond them, all built visually with a connection you create once. Many apps also have an n8n node, so check whether Wasabi has one that covers your case. Neither choice is ranked here: compare the modules each tool offers for your storage workflow, then build where your scenarios already live.
Same platform

Other docs you might need on this stack.

Browse all integrations