Resources · Make integration

LEAV Engine Make integrationAutomate LEAV Engine with Make.

Can Make keep your LEAV Engine records up to date while you work in other tools? The LEAV Engine Make integration gives you 5 modules: 4 actions and 1 search. This guide shows how to link your account, build a first scenario and pick the right module.

Try the LEAV Engine integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the LEAV Engine Make integration do?

The LEAV Engine Make integration lets Make read and write records in LEAV Engine without code. You build a scenario, which is the automation itself, out of modules, the bricks of that automation. LEAV Engine brings five of them, and none of them is a trigger, so the scenario starts from another app or from a schedule.

Records created from outside. A lead lands in your form tool or CRM, and Create a Record adds it to LEAV Engine with the data mapped from that first app. Nobody retypes anything.

Values kept in sync. When a status or a price changes somewhere else, Search Records finds the matching entries and Save Values writes the new data into them. A search can return zero, one or several items, which Make calls bundles, so each one is handled in turn.

Clean-up without deleting. Deactivate a Record takes an entry out of use when it closes in another system. For anything the four ready-made modules do not cover, Run a GraphQL Query lets you send your own query.

Know the limits before you start: Make itself says its documentation for LEAV Engine is thin, because little public information exists about the app. Test every module with Run once on sample data. If you are new to the editor, the Make training covers the basics, and the n8n vs Make comparison helps if you are still choosing a tool. The Make pricing page explains what an operation costs.

Connect

How do you connect LEAV Engine to Make?

  1. 01

    Add a LEAV Engine module

    In your scenario, click the +, search for LEAV Engine and pick any of its modules. Then click Create a connection. A connection is your LEAV Engine account linked to Make once, then reused by every LEAV Engine module.

  2. 02

    Name the connection

    This step is optional, but a clear name such as the workspace or the environment it points to saves confusion later, especially if you connect more than one LEAV Engine account to the same Make organization.

  3. 03

    Authorize and save

    Either approve access on the LEAV Engine page that opens, or paste the key LEAV Engine gives you, depending on what the window asks for. Click Save, and the module can now list what your account can read.

First scenario

Build your first scenario with LEAV Engine

GoalWhen a new entry appears in another app, Make creates the matching record in LEAV Engine.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since LEAV Engine has no trigger, the first module comes from the app where your new entries appear, such as a form tool.

  2. 02

    Set up the starting module

    Pick that app's module, click Create a connection to link its account, and fill in its fields. Make lists what it can read once the connection exists, so you choose rather than type.

  3. 03

    Add Create a Record

    Click the + on the right of the first module, search for LEAV Engine and choose Create a Record. Connect your account, then map each value from the first module into the matching field.

  4. 04

    Test with Run once

    Click Run once and create a test entry in the first app. Open the bundles each module received: this is the fastest way to see what LEAV Engine expects, given how short the documentation is.

  5. 05

    Schedule and switch on

    On the first module, open the clock to set the schedule. A new scenario runs every 15 minutes by default. Then switch the scenario on, and each run creates records for the entries found since the last one.

Modules

What each LEAV Engine module does

LEAV Engine gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

LEAV Engine1

Create a Record

ActionIn the docs only

You get a new entry in LEAV Engine built from data that already exists elsewhere, so nobody has to copy it by hand. It is the module to start with when another app is where information first shows up.

When to use it
a request or a contact arrives in another tool and needs its own record in LEAV Engine.
Watch out
it creates a record on every run, so search first with Search Records if the same entry can come back twice.
LEAV Engine2

Deactivate a Record

ActionIn the docs only

This one takes a record out of active use instead of leaving stale entries around. Pick it over Save Values when the goal is to retire an entry, not to change what it contains.

When to use it
a project, a product or a contract closes in another system and should stop showing as current in LEAV Engine.
Watch out
Make's documentation does not say whether a deactivated record can be restored, so try it on a test record first.
LEAV Engine3

Run a GraphQL Query

ActionIn the docs only

Here you write the query yourself in GraphQL, the query language named in the module, and reach what the four other modules leave out. It gives the most freedom and asks the most knowledge of how your LEAV Engine data is organized.

When to use it
only when Create a Record, Save Values, Search Records and Deactivate a Record cannot do the job.
Watch out
test the query with Run once and read the bundle it returns before mapping anything from it.
LEAV Engine4

Save Values

ActionIn the docs only

Save Values writes new data into LEAV Engine, which keeps entries current when information changes in another app. Choose it rather than Create a Record when the entry already exists and only its values need to move.

When to use it
a status, an amount or an owner changes elsewhere and LEAV Engine should reflect it.
Watch out
the documentation does not say how it picks the record to update; placing Search Records before it is the safest way to hand it the right one.
LEAV Engine5

Search Records

SearchIn the docs only

Search Records looks through LEAV Engine and hands back the entries that match, one bundle per record. It is the piece that lets the rest of the scenario act on existing data rather than guessing.

When to use it
before Save Values or Deactivate a Record, to find the record an outside event is about.
Watch out
a search can return zero, one or several bundles, and each following module then runs once per bundle, which uses one operation each time.
Need help

Need help automating LEAV Engine with Make?

A person reads every message.

FAQ

LEAV Engine and Make: frequent questions

01Is the LEAV Engine Make integration free?
Yes, LEAV Engine is a standard app in Make, so its modules are available on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most 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 and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle.
02What do you need to connect LEAV Engine to Make?
You need a LEAV Engine account and a Make account. Make's documentation lists no specific prerequisite and no official connection steps for this app, so the generic flow applies: add a LEAV Engine module, click Create a connection, optionally name it, then approve access on the LEAV Engine page or paste the key it provides, and click Save. If you are not the administrator of your LEAV Engine instance, ask that person which access method is enabled before you start.
03Does the LEAV Engine Make integration work in real time?
Not by itself, because LEAV Engine has no trigger module in Make, neither scheduled nor instant. A scenario still needs a starting point, so it begins either with a trigger from another app, such as a form or a CRM, or with Make's own schedule set on the first module. A new scenario runs every 15 minutes by default, and the Free plan does not allow a shorter interval. Paid plans can go down to 1 minute.
04What if a LEAV Engine module is missing in Make?
It depends on what you need. The LEAV Engine app has no Make an API Call module, but it does have Run a GraphQL Query, which lets you write your own query for cases the other four modules skip. If that is not enough, another app can often cover the missing step, or the team behind this guide can look at your case through the help form. Keep in mind that Make admits its LEAV Engine documentation is limited.
05Should you use Make or n8n for LEAV Engine?
It depends on the tool you already use. On Make, LEAV Engine offers five modules on every plan, including Free, but no trigger, so each scenario starts from another app or a schedule. Many apps also have a node in n8n; check whether LEAV Engine does before deciding. The n8n vs Make comparison on this site sets out the criteria side by side, without declaring a winner, so you can judge against your own setup.
Same platform

Other docs you might need on this stack.

Browse all integrations