Resources · Make integration

DigitalOcean Spaces Make integrationAutomate DigitalOcean Spaces with Make.

Files land in your buckets, and the rest of your tools never hear about it? The DigitalOcean Spaces Make integration gives you 8 modules, including 2 triggers, to move files in and out of Spaces without code. This guide walks you from the access key to a first working scenario.

Try the DigitalOcean Spaces integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DigitalOcean Spaces Make integration do?

The DigitalOcean Spaces Make integration links your Spaces storage to Make, a visual tool where you build a scenario (the automation itself, a chain of steps) without writing code. Each step is a module: it watches your buckets, reads a file, or sends one in, and Make passes the result to the next step.

Archive what other apps produce. A report, an export or an attachment comes out of another tool, and Upload a File drops it into the right bucket. Nobody has to download it and upload it again by hand.

React to new files. Watch Files notices when a file is uploaded or updated in a bucket, and Download a File fetches its content so the next module can send it, parse it or store it somewhere else.

Keep an eye on your storage. Watch Buckets reports each new bucket, while List Buckets and List Files give you an inventory to log or check.

The eight modules cover watching, listing, uploading and downloading. For any other endpoint, Make an API Call reaches the Spaces API with the same connection. If you are still weighing tools, the n8n vs Make comparison sets out the criteria, the Make pricing page explains the plans, and the Make training helps you build faster.

Connect

How do you connect DigitalOcean Spaces to Make?

  1. 01

    Create an access key in DigitalOcean

    In the DigitalOcean control panel, open the Spaces Access Keys page and click Create Access Key. Choose the scope and permissions, name the key, confirm, then copy both the key and the secret shown in the window.

  2. 02

    Add a Spaces module to your scenario

    In Make, add any DigitalOcean Spaces module and click Create a connection. A connection is your Spaces account linked to Make once, then reused by every Spaces module. The Connection name field is optional.

  3. 03

    Paste the credentials and save

    Paste the access key and the secret you copied, or follow the instructions Make shows on screen. Once saved, the connection appears in the dropdown of every DigitalOcean Spaces module you add later.

First scenario

Your first scenario: send files from another app into a bucket

GoalWhen another app produces a file, Make uploads it to your DigitalOcean Spaces bucket.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. This first module belongs to the app that hands over the file, such as your form tool or mailbox.

  2. 02

    Set up the source

    Pick that app's module, click Create a connection for its account, and fill its fields. Each file it outputs travels as a bundle, one item passed from one module to the next.

  3. 03

    Add Upload a File

    Click the + on the right of the first module, search DigitalOcean Spaces and pick Upload a File. Choose your Spaces connection, then map the file coming from the previous module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Check the bucket in DigitalOcean: the file should be there.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

DigitalOcean Spaces triggers in Make

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

DigitalOcean Spaces1Watch Buckets

Watch Buckets

Scheduled trigger

In Make“Triggers when a new bucket is created in DigitalOcean Space.”

You get a new bundle each time a bucket is created in your DigitalOcean Spaces account, so the scenario can log it, announce it or prepare it for use. A trigger is the module that starts the scenario.

How it fires
scheduled. Make checks your account on the scenario's schedule, so a new bucket shows up at the next check, not the second it exists.
When to use it
several people on your team create buckets and you want each new one recorded in a shared sheet or announced in your chat tool.
Watch out
on the Free plan the shortest interval between two checks is 15 minutes.
DigitalOcean Spaces2Watch Files

Watch Files

Scheduled trigger

In Make“Triggers when a file is uploaded or updated in a bucket space.”

This one starts your scenario whenever a file is uploaded or updated inside a bucket, which turns any upload into a signal for the rest of your tools.

How it fires
scheduled. Make checks the bucket on the scenario's schedule and picks up what changed since the last check.
When to use it
a partner drops deliverables into a shared bucket and you want the project owner notified, or the file copied elsewhere with Download a File.
Watch out
an updated file fires the trigger too, so a scenario that writes back to the same bucket can end up reacting to its own uploads.
Modules

DigitalOcean Spaces modules in Make

DigitalOcean Spaces gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

DigitalOcean Spaces1

Create a Bucket

Action

In Make“Creates a new bucket.”

With this action, a scenario creates a fresh bucket for you, ready to receive files from the next modules, instead of you clicking through the control panel.

When to use it
a new client or project is added in your CRM and you want a dedicated storage space created at the same moment.
Watch out
the access key behind your connection only does what its scope and permissions allow, so check them when you create the key.
DigitalOcean Spaces2

Download a File

Action

In Make“Downloads a file from a bucket.”

Grab the content of a file stored in a bucket so the next module can attach it to an email, send it to another storage or read it.

When to use it
right after Watch Files or List Files, when knowing the file exists is not enough and you need the file itself.
Watch out
on the Free plan Make handles files up to 5 MB, so check the size of your archives before you build on them.
DigitalOcean Spaces3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Your way out when the listed modules stop short: it sends any request to the DigitalOcean Spaces API while reusing the connection you already set up.

When to use it
you need an endpoint of the Spaces API that none of the other Spaces modules covers, and you would rather not leave Make for it.
Watch out
you write the request yourself, so keep the Spaces API documentation open while you fill the module.
DigitalOcean Spaces4

Upload a File

Action

In Make“Uploads a file to a bucket.”

Send a file produced earlier in the scenario into a bucket, where it stays stored with the rest of your Spaces content.

When to use it
invoices, exports or form attachments come out of another app and you want a copy archived automatically.
Watch out
map the file from the previous module, not just its name, and remember the 5 MB file ceiling of the Free plan.
DigitalOcean Spaces5

List Buckets

Search

In Make“Lists all buckets in DigitalOcean Space.”

Get the full list of buckets in your account, each one returned as its own bundle, which gives you an inventory you can log or filter.

When to use it
you want to check which buckets exist before creating a new one, or keep a register of your storage up to date.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bucket.
DigitalOcean Spaces6

List Files

Search

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

Browse a path inside a bucket and receive every file found there, one bundle per file, ready to be downloaded, copied or recorded.

When to use it
you need to process files already sitting in a folder, not only the new ones Watch Files reports.
Watch out
each file returned makes the following modules run again, so a crowded folder uses operations quickly.
Need help

Need help automating DigitalOcean Spaces with Make?

A person reads every message.

FAQ

DigitalOcean Spaces and Make: frequently asked questions

01Is the DigitalOcean Spaces Make integration free?
Yes, on the Make side. DigitalOcean Spaces is a standard app, available on the Free plan along with more than 3,000 others. The Free plan allows 2 active scenarios, a minimum interval 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 DigitalOcean subscription is a separate matter, covered by DigitalOcean's own pricing page.
02What is needed to connect DigitalOcean Spaces to Make?
An active DigitalOcean account and a Spaces access key with its secret key. You create the key on the Spaces Access Keys page of the control panel by clicking Create Access Key, choosing the scope and permissions, and naming it. Copy the key and the secret from the window that follows. In Make, add a DigitalOcean Spaces module, click Create a connection and paste both values. The connection then serves every Spaces module in your scenarios.
03Do the DigitalOcean Spaces triggers in Make fire in real time?
No. Watch Buckets and Watch Files are both scheduled triggers: Make checks your account on the scenario's schedule instead of being called by DigitalOcean. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans let you check as often as every minute. In practice, a file uploaded right after a check waits for the next one before the scenario picks it up, so plan your workflow around that delay rather than expecting an instant reaction from Watch Files or Watch Buckets.
04What if a DigitalOcean Spaces action is missing in Make?
Use the Make an API Call module. It sends any request to the DigitalOcean Spaces API with the connection you already have, so any endpoint of that API stays within reach even without a dedicated module. You write the request yourself, which means reading the Spaces API documentation first. Also keep in mind that the Make help page for this app is AI-generated from DigitalOcean's documentation and asks you to verify important details with DigitalOcean.
05Make or n8n for DigitalOcean Spaces?
It depends on the tool your team already works with. On Make, DigitalOcean Spaces comes with 8 modules: 2 scheduled triggers, 4 actions and 2 searches, plus Make an API Call for the rest. The same app often has an n8n node too, so check that side before choosing. Compare the modules each tool offers for the job you have in mind, and where your other automations already run, rather than picking on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations