Resources · Make integration

Uploadcare Make integrationAutomate Uploadcare with Make.

Every new file in Uploadcare can start a workflow on its own. The Uploadcare Make integration gives you 3 modules: 1 instant trigger and 2 actions. This page shows you how to link your project keys and build a first scenario that pushes files into Uploadcare.

Try the Uploadcare integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Uploadcare Make integration do for you?

The Uploadcare Make integration links your Uploadcare project to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger or an action. Once your keys are connected, Make can react to new uploads and send new files into the project for you.

React the moment a file arrives. Watch File Uploads is an instant trigger: Uploadcare calls Make through a webhook as soon as someone uploads a file to your project. A product team can use it to hand each new asset to the next tool in the chain, with no one checking the dashboard.

Feed your project from other apps. Upload a File adds a new file to your Uploadcare project. Picture an agency collecting attachments from a form tool: the form app starts the scenario, and Upload a File stores each attachment in the right project. The 123FormBuilder Make integration is one example of an app that can sit in front of it.

Reach what the list does not cover. Make an API Call reuses the same connection to call any endpoint of the Uploadcare API. It is the fallback when the two ready-made modules stop short of your need.

The official documentation lists no specific limit for this app, only a note that its content is AI-generated and should be checked against Uploadcare's own documentation. Make's plan limits still apply: on the Free plan, files up to 5 MB and 2 active scenarios. The Make pricing page breaks the plans down. Many apps also have an n8n node, and the n8n vs Make comparison lays out the criteria for choosing.

Connect

How do you connect Uploadcare to Make?

  1. 01

    Copy your two project keys

    In the Uploadcare dashboard, pick your project from the workspace, open its settings and go to the API keys tab. Copy the key labeled Public key, then the one labeled Secret key. Make needs both.

  2. 02

    Open the connection window in Make

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

  3. 03

    Paste the keys and save

    Enter the credentials you copied from Uploadcare, or follow the on-screen instructions, and confirm. From now on, each Uploadcare module in any scenario can pick this connection from the list instead of asking for the keys again.

First scenario

Build your first scenario with Uploadcare

GoalWhen a file shows up in another app, Make stores it in your Uploadcare project.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that produces your files, such as a form or storage tool, as the first module.

  2. 02

    Add Upload a File

    Click the + on the right of that first module, search for Uploadcare and choose Upload a File. Select the connection you created, or click Create a connection to paste your keys.

  3. 03

    Map the file

    Fill the module by mapping the file that comes out of the first module. Each file travels as a bundle, meaning one item passed from one module to the next.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Open the bubble above each module to read the bundles it received, then check that the file landed in your Uploadcare project.

  5. 05

    Schedule and switch on

    Set the schedule on the first module. A new scenario runs every 15 minutes by default, and each module run counts as one operation on your plan. Then switch the scenario on.

Triggers

What starts an Uploadcare scenario?

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

Uploadcare1Watch File Uploads

Watch File Uploads

Instant trigger

In Make“Triggers when a new file is uploaded into your project.”

Your scenario starts on its own each time a new file is uploaded to your Uploadcare project, and the file details become the first bundle of the run. Nothing to poll, nothing to check by hand: the upload itself is the signal.

How it fires
instant, Uploadcare calls Make through a webhook as soon as the upload happens, which the lightning badge on the module shows.
When to use it
when the next step, such as a notification or a record in another app, must follow each upload without waiting for a schedule.
Watch out
click Create a webhook before Create a connection, and avoid pairing it with Upload a File on the same project, since, logically, that upload would count as a new file too.
Modules

What can Make do in Uploadcare?

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

Uploadcare1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Whatever the two ready-made modules skip, you can still reach: this module calls any endpoint of the Uploadcare API from your scenario, with the connection you already set up.

When to use it
when Upload a File and the trigger do not cover the task you have in mind.
Watch out
you describe the request yourself, so keep the Uploadcare API documentation open while you fill it.
Uploadcare2

Upload a File

Action

In Make“Uploads a new file into your project.”

You get a new file stored in your Uploadcare project, taken from whatever the earlier module passed along, whether a form attachment or a document from another tool.

When to use it
when files are born in another app and belong in Uploadcare.
Watch out
on the Free plan, Make handles files up to 5 MB, so larger files call for a paid plan.
Need help

Need help automating Uploadcare with Make?

A person reads every message.

FAQ

Uploadcare and Make: common questions

01Is the Uploadcare Make integration free?
Yes, on the Make side. Uploadcare is a standard app, so its 3 modules are available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in credits, one operation for each module run on one bundle. You still need an active Uploadcare account, whose own pricing sits on the Uploadcare site.
02What do you need to connect Uploadcare to Make?
An active Uploadcare account and the API keys of the project you want to automate. In the Uploadcare dashboard, pick the project, open its settings and go to the API keys tab, then copy the Public key and the Secret key. In Make, add an Uploadcare module, click Create a connection, give it a name if you like and paste the keys. For the Watch File Uploads trigger, click Create a webhook first, then Create a connection. The same connection then serves every Uploadcare module you add later.
03Does the Uploadcare trigger in Make react in real time?
Yes. Watch File Uploads is an instant trigger: Uploadcare calls Make through a webhook as soon as a new file is uploaded to your project, and the scenario starts right away. You do not wait for the schedule that scheduled triggers follow, which defaults to every 15 minutes on a new scenario. The lightning badge on the module confirms the type. Setup order matters: create the webhook first, then the connection, or the trigger has no address to receive the upload notice from Uploadcare.
04What if the Uploadcare module you need is missing in Make?
Use Make an API Call. With this module, any endpoint of the Uploadcare API can be called from your scenario, with the same connection as the other modules, so you do not need a second setup. You write the request based on the Uploadcare API documentation. The official Make documentation lists no app-specific limit, but it states that its content is AI-generated and should be checked against Uploadcare's own documentation. Make's plan limits, such as the 5 MB file size on the Free plan, still apply.
05Should you use Make or n8n for Uploadcare?
It depends on the tool your team already builds with. On Make, Uploadcare offers 3 modules: an instant trigger for new uploads, Upload a File and Make an API Call, all available from the Free plan among 3,000+ standard apps. Many apps also have an n8n node, so check whether one exists for Uploadcare and what it covers before you decide. Compare the modules each tool offers for your exact task, then pick the one where the scenario is easiest for your team to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations