Resources · Make integration

Upload to URL Make integrationAutomate Upload to URL with Make.

Can Make handle your files through Upload to URL without a line of code? The Upload to URL Make integration gives you 4 action modules and no trigger. This page is for people new to Make: connect the account, build a first scenario, then pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Upload to URL Make integration do?

The Upload to URL Make integration lets a Make scenario (the automation you build, a chain of modules) send a file to Upload to URL, fetch it back, delete it, or call the app's API directly. Each module is one brick of that chain. The app has no trigger, so something else starts the scenario: a schedule set in Make or a module from another app.

Hand a file over, then clean up. Put Upload a file after the module of another app that produces a file, and follow it with Delete a file once the next step no longer needs it. Each module run on one item counts as one operation on your Make plan.

Get a stored file back into the flow. Retrieve a file brings a file from Upload to URL into the scenario, so a later module can read it or pass it on.

Cover what the list misses. Make an API call reaches any endpoint of the Upload to URL API with the same connection.

Be aware of one real limit: Make itself states it cannot publish complete documentation for this app, because too little public information exists about it. Expect to discover each module's fields by opening it in the editor. If you are weighing tools, the n8n vs Make comparison lays out the criteria, and the Make training walks through scenario building step by step. When a run fails, start with Make troubleshooting.

Connect

How do you connect Upload to URL to Make?

  1. 01

    Add a module and create the connection

    Drop any Upload to URL module into your scenario and click Create a connection. A connection is your Upload to URL account linked to Make once, then reused by all four modules.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when you run several accounts. Then authorize Make on the Upload to URL page, or paste the key the app gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. Back in the module, the fields become editable. Since the documentation is thin, read each field label carefully before mapping anything into it.

First scenario

Your first scenario with Upload to URL

GoalWhen the scenario runs on its schedule, Make sends a file from another app to Upload to URL.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that holds your file, since Upload to URL cannot start a flow.

  2. 02

    Add Upload a file

    Click the + on the right of that first module, search for Upload to URL and choose Upload a file. Click Create a connection if you have not linked the account yet.

  3. 03

    Map the file

    Fill the module fields and map the file coming from the previous module. Each file travels as a bundle, one item passed from one module to the next.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received and spot a wrong mapping.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. On the Free plan the interval cannot go below 15 minutes.

Modules

What the Upload to URL modules do

Upload to URL gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Upload to URL1

Delete a file

ActionIn the docs only

Removes a file from Upload to URL so that nothing lingers after your scenario has used it. It keeps your storage tidy without a manual pass.

When to use it
as the last step, once the file has been passed to the app that really needed it.
Watch out
the module acts on a real file, so run your first Run once on a throwaway file.
Upload to URL2

Make an API call

ActionIn the docs only

Gives you a direct line to any endpoint of the Upload to URL API, reusing the connection you already created. It fills the gaps the three ready-made modules leave open.

When to use it
when you need an operation that Upload a file, Retrieve a file and Delete a file do not offer.
Watch out
Make publishes little documentation for this app, so check whether Upload to URL publishes its own API reference before you rely on this module.
Upload to URL3

Retrieve a file

ActionIn the docs only

Brings a file stored in Upload to URL back into your scenario, so the next module can read it, attach it or send it elsewhere.

When to use it
when an earlier run uploaded a file and a later step, in another app, now needs its content.
Watch out
on the Free plan Make handles files up to 5 MB, so a larger file may stop the run.
Upload to URL4

Upload a file

ActionIn the docs only

Sends a file from your scenario to Upload to URL. This is usually the module you start with, placed right after the app that produces the file.

When to use it
when a form, an inbox or a storage app hands you a file and Upload to URL is where it should go.
Watch out
the documentation does not list the fields, so open the module and map the file bundle from the previous step explicitly.
Need help

Need help automating Upload to URL with Make?

A person reads every message.

FAQ

Questions about the Upload to URL Make integration

01Is the Upload to URL Make integration free?
Yes, Upload to URL is a standard app, available from the Make Free plan. The Free plan keeps 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 (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, allow unlimited active scenarios and 40 minutes of execution. Usage is counted in operations per month, one per module run on one item.
02What do you need to connect Upload to URL to Make?
An Upload to URL account and a Make account. The documentation lists no prerequisites and no specific steps, so the generic Make flow applies: add a module, click Create a connection, name it if you want, authorize Make on the app page or paste the key the app provides, then click Save. The same connection then serves all four modules, including Make an API call. Test it with Run once before you switch the scenario on.
03Does the Upload to URL Make integration react in real time?
No, because Upload to URL has no trigger at all. Its four modules are actions, so the scenario must be started by something else. Two options: set a schedule on the first module, every 15 minutes by default and 1 minute at best on a paid plan, or open the scenario with a module from another app that watches for new files, then add Upload a file right after it.
04What if an Upload to URL module is missing in Make?
Use Make an API call. It reaches any endpoint of the Upload to URL API with the connection you already have, so you are not limited to uploading, retrieving and deleting files. Keep in mind that Make says it cannot provide complete documentation for this app, because public information about it is scarce. To know which endpoints exist, look for API documentation from Upload to URL itself, if it publishes any. Test each call with Run once before scheduling it.
05Should you use Make or n8n for Upload to URL?
It depends on your criteria rather than on the app. In Make, Upload to URL offers four action modules, including a generic API call module, and works from the Free plan. The same app often has an n8n node too, so check whether it exists there before deciding. Compare how each tool fits your team and your other apps, then test a small flow in the one you pick. Either way, your files stay in Upload to URL.