Resources · Make integration

Couchdrop Make integrationAutomate Couchdrop with Make.

Need files from your other tools to land in Couchdrop on their own? The Couchdrop Make integration gives you 3 action modules: one upload and two open API calls. This page is for teams that store files in Couchdrop, and it walks you from the API token to a working first scenario.

Try the Couchdrop integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Couchdrop Make integration do for you?

The Couchdrop Make integration links your Couchdrop account to Make so a scenario (the automation you build in Make, a chain of bricks called modules) can push files into Couchdrop without you touching them. It has no trigger of its own, so something else starts the scenario: another app or the clock in Make.

Collect attachments in one place. A form tool or an inbox app hands a file to Make, and Upload to Couchdrop writes it into your storage. Each file travels as a bundle, the single item that flows from one module to the next. If your files come from a form, the 123FormBuilder Make integration page shows how a form app plugs into Make.

Reach the parts of Couchdrop the upload module does not cover. Make a Filesystem API Call talks to the Couchdrop Filesystem API, and Make a Management API Call talks to the management API. Both reuse the same connection, so you skip the token handling and only describe the request.

Run a routine on a timer. Because Couchdrop never starts a scenario itself, you can let the schedule in Make run it, every 15 minutes by default on a new scenario, and chain the modules you need.

What the integration does not give you: a way to react when a file appears in Couchdrop, since there is no trigger, and no search module. The same app often has an n8n node too; the n8n vs Make comparison helps you pick by criteria. If you are new to the editor, the Make training covers the basics.

Connect

How do you connect Couchdrop to Make?

  1. 01

    Copy your API token in Couchdrop

    Log in to Couchdrop with an active account, open the Admin section, then click API Tokens. Copy the token shown on screen. This token is what Make will use to act on your behalf.

  2. 02

    Add a Couchdrop module in Make

    In your scenario, add any Couchdrop module and click Create a connection. A connection is your Couchdrop account linked to Make once; every Couchdrop module reuses it. You can type a label in Connection name if you like.

  3. 03

    Paste the token and save

    Paste the token you copied into the credentials field, or follow the instructions Make shows on screen, then save. The module can now reach your Couchdrop account.

First scenario

Your first scenario with Couchdrop

GoalWhen another app hands a file to Make, Make uploads it to Couchdrop.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that produces your files, since Couchdrop has no trigger.

  2. 02

    Set up the file source

    Connect that first app and fill its fields. Once the connection exists, Make lists the folders or objects it can read, so you choose instead of typing.

  3. 03

    Add Upload to Couchdrop

    Click the + on the right of the first module, search Couchdrop and pick Upload to Couchdrop. Select your connection, then map the file coming from the previous module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received, then check the file in Couchdrop.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the Couchdrop modules do

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

Couchdrop1

Make a Filesystem API Call

Action

In Make“Performs an arbitrary authorized API call to the Filesystem API.”

Sends a request of your choice to the Couchdrop Filesystem API, already signed with your connection, and returns the answer to the next module. You write the request; Make handles the authentication.

When to use it
a file operation you need is not covered by Upload to Couchdrop, and you know which Filesystem API request does it.
Watch out
Make gives no ready-made fields here, so keep the Couchdrop API reference open while you build the request.
Couchdrop2

Make a Management API Call

Action

In Make“Performs an arbitrary authorized API call to the management API.”

Lets you reach the Couchdrop management API from a scenario, with the same connection as your file modules, so account-level tasks can sit in the same flow as your uploads.

When to use it
the step you want to automate concerns how Couchdrop is administered rather than a file itself.
Watch out
this is a different API from the Filesystem one; pick this module only when the request belongs to management.
Couchdrop3

Upload to Couchdrop

Action

In Make“Uploads a File to Couchdrop.”

Puts a file into Couchdrop for you: the file that arrives from the previous module is written to your storage, with no manual download and upload in between.

When to use it
a form, an email or another app produces a document that should end up in Couchdrop once your scenario receives it.
Watch out
the module needs a real file from the module before it; run the scenario once and check the bundle carries one.
Need help

Need help automating Couchdrop with Make?

A person reads every message.

FAQ

Couchdrop and Make: frequent questions

01Is the Couchdrop Make integration free?
Yes, on the Make side. Couchdrop is a standard app, so it works from the Free plan onward. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. You still need an active Couchdrop account, which follows its own pricing.
02What do you need to connect Couchdrop to Make?
Two things: an active Couchdrop account and its API token. In Couchdrop, open the Admin section, click API Tokens and copy the token on screen. In Make, add a Couchdrop module, click Create a connection, optionally give it a name, paste the token and save. That single connection then serves all three Couchdrop modules, so you only do it once per account. If the save fails, check the token was copied in full and that the Couchdrop account is still active.
03Does Couchdrop trigger Make scenarios in real time?
No, because the Couchdrop app in Make has no trigger at all. The scenario has to start elsewhere. The usual way is a trigger from another app that produces the file, such as a form or an inbox. The other way is the schedule on the first module, which runs every 15 minutes by default on a new scenario and can go down to 1 minute on a paid plan. Couchdrop modules then act as steps in that flow.
04What if the Couchdrop module you need is missing in Make?
It depends on what is missing. The app has no generic Make an API Call module, but it offers two of its own: Make a Filesystem API Call for file operations and Make a Management API Call for administration, both using your existing connection. If neither covers the case, another app may, or the team can look at it with you. Also note that the Couchdrop documentation in Make is AI-generated and may contain mistakes, so check anything important with Couchdrop.
05Should you use Make or n8n for Couchdrop?
It depends on your criteria rather than on a winner. In Make, Couchdrop brings 3 action modules: an upload and two open API calls, with no trigger and no search. The same app often exists as an n8n node too, so compare what each tool offers for your exact task, where your other automations already live, and which editor your team is comfortable with. Choose the one where the whole flow, not only the Couchdrop step, is easiest to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations