Resources · Make integration

legacy-use Make integrationAutomate legacy-use with Make.

Can Make launch your legacy-use jobs for you? The legacy-use Make integration gives you 4 action modules and no trigger, so another app or a schedule starts the flow. This page shows how to connect your account, build a first scenario and pick the right module.

Try the legacy-use integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the legacy-use Make integration do?

The legacy-use Make integration lets a Make scenario, the automation you build in Make, send work to legacy-use without any code. Each scenario is a chain of modules, and legacy-use brings four of them: three that handle jobs and one universal call to its API. Nothing in legacy-use starts the scenario on its own.

Kick off a job from an event elsewhere. Since legacy-use has no trigger, the first module comes from another app, such as a form tool, or from Make's own schedule. Place Run a job right after it and the event you already track becomes the start of a legacy-use job.

Split launch and follow-up. When you want control over each stage, Start a job and Wait for a job sit one after the other. Going by their names, the first sends the job and the second holds the scenario until it is ready, so the modules you add next act on a finished stage.

Reach anything the list leaves out. Make an API call uses your existing connection to call any endpoint of the legacy-use API, which is your route when the three job modules are not enough.

Be aware of one real limit: Make states that its documentation for legacy-use is incomplete, because little public information exists about the app. The modules come without official descriptions, so test every step with Run once before relying on it. The Make troubleshooting guide helps when a run fails, and the Make training covers the editor from the ground up. If you are weighing tools, the n8n vs Make comparison lays out both options.

Connect

How do you connect legacy-use to Make?

  1. 01

    Open the connection window

    Add any legacy-use module to your scenario, then click Create a connection. A connection is your legacy-use account linked to Make once and reused by every legacy-use module after that.

  2. 02

    Name it so you can find it later

    Giving the connection a name is optional, but it pays off when you run several accounts or environments. Pick something your teammates will recognize at a glance in the dropdown.

  3. 03

    Authorize Make and save

    Depending on what legacy-use asks for, either approve Make on the legacy-use page that opens or paste the key legacy-use gives you. Then click Save and the module is ready to fill.

First scenario

Build your first scenario with legacy-use

GoalWhen something happens in another app, Make starts a legacy-use job and waits for it before moving on.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app whose event should launch the job, since legacy-use has no trigger of its own.

  2. 02

    Add Start a job

    Click the + on the right of the first module, search for legacy-use and choose Start a job. Click Create a connection to link your account, then fill the fields Make shows you.

  3. 03

    Chain Wait for a job

    Add Wait for a job after it and map the data coming out of Start a job, so the scenario follows the job it just launched rather than another one.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open each module and read the bundles it received: a bundle is one item passed from one module to the next.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which is every 15 minutes by default, then switch the scenario on. From then on it runs without you.

Modules

What can the legacy-use modules do?

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

legacy-use1

Make an API call

ActionIn the docs only

Reaches any endpoint of the legacy-use API from inside your scenario, with the connection you already set up, so you are never stuck with only the three job modules.

When to use it
a request you need has no dedicated module in the list.
Watch out
Make publishes almost nothing on the legacy-use API, so you rely on legacy-use's own reference for the endpoint and body.
legacy-use2

Run a job

ActionIn the docs only

Gives you the shortest path to getting a legacy-use job done from a scenario: one module where the other route takes two. Judging by its name, it covers the whole run in a single step.

When to use it
you just want the job executed and nothing else happens between launch and result.
Watch out
the documentation gives no description of this module, so confirm with Run once what it returns before you map its output.
legacy-use3

Start a job

ActionIn the docs only

Judging by its name, it sends a job to legacy-use and hands the scenario back right away, which leaves room to add other modules before you check on that job.

When to use it
you want to launch now and follow up later in the flow, typically paired with Wait for a job.
Watch out
nothing says it reports the end of the job, and Make documents nothing more, so check its output with Run once.
legacy-use4

Wait for a job

ActionIn the docs only

As its name suggests, it holds your scenario until a legacy-use job launched earlier is ready, so the next modules act on a finished stage.

When to use it
right after Start a job, mapping its output so both modules point at the same job.
Watch out
a scenario on the Free plan can execute for 5 minutes at most, so a long wait may hit that ceiling.
Need help

Need help automating legacy-use with Make?

A person reads every message.

FAQ

legacy-use and Make: common questions

01Is the legacy-use Make integration free?
Yes, legacy-use is a standard app in Make, so you can use it from the Free plan onward. The Free plan comes with limits: 2 active scenarios, at least 15 minutes between two 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) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle.
02What do you need to connect legacy-use to Make?
A legacy-use account and a Make account. Make's documentation for legacy-use lists no prerequisite and no dedicated connection steps, so the generic flow applies: add a legacy-use module, click Create a connection, optionally name it, then either authorize Make on the legacy-use page or paste the key legacy-use provides, and click Save. The connection is created once and every legacy-use module in your scenarios reuses it, so you never repeat these steps when you add Run a job or Wait for a job later.
03Does legacy-use trigger a Make scenario in real time?
No, because legacy-use has no trigger module in Make at all. Its 4 modules are actions, so something else has to start the scenario. You have two options: open the flow with a trigger from another app, whose own type decides how fast it reacts, or rely on the scheduling clock of the first module, which checks every 15 minutes by default and down to 1 minute on paid plans (15 minutes minimum on Free).
04What if the legacy-use module you need is missing in Make?
Use Make an API call. It calls any endpoint of the legacy-use API with the connection you already have, so it covers whatever Run a job, Start a job and Wait for a job leave out. Keep in mind that Make says its legacy-use documentation is limited because little public information exists about the app, so you will need legacy-use's own API reference to fill the request. Test it with Run once before switching the scenario on.
05Should you use Make or n8n for legacy-use?
It depends on the tool your team already works in. The same app often has an n8n node too, so check whether one exists for legacy-use before choosing. On the Make side, you get 4 action modules, including Make an API call for anything they miss, with a Free plan to try it. Neither tool is ranked here: compare the modules each tool offers for legacy-use and pick the one where your other apps already live.
Same platform

Other docs you might need on this stack.

Browse all integrations