Resources · Make integration

Legito Make integrationAutomate Legito with Make.

Can Make handle the paperwork around your Legito documents? The Legito Make integration gives you 29 modules: 21 actions and 8 searches. This guide is for legal and ops teams, and it walks you from the connection to a first working scenario.

Try the Legito integration on MakeSee the 29 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Legito Make integration do?

The Legito Make integration links your Legito account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that acts on one app. Legito brings 29 of those bricks, so documents, files, users and object data can move between Legito and your other tools without anyone copying them by hand.

Signed contracts land in the right place. When your e-signature or storage tool reports a finished agreement, Update a Document Record can set its Signing Date, and Upload a File attaches the signed copy to that same record. Nobody has to open Legito to tidy up.

Reviewers get documents without a reminder email. A request typed into a form can become a Legito draft through Create a Document Record, and Share a Document sends it to the Legito user whose email you map. For someone outside your team, Create an External Link opens access with the privileges you choose, and Delete an External Link closes it again.

Document data feeds your other tools. Get a Document Version Data reads the Elements of a document and hands them to a spreadsheet or a CRM, while Download a Document Version exports the file itself as base64.

Two limits to know. Legito has no trigger in Make, so a scenario starts from another app or from the schedule. And Make says its own documentation for Legito is limited, so field details appear only inside each module once your account is connected. If you are still weighing tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains what a plan includes, and Make training gets a team started.

Connect

How do you connect Legito to Make?

  1. 01

    Add a Legito module

    In a new scenario, click the +, search for Legito and pick any module, for example Search Document Records. The module asks for a connection: your Legito account linked to Make once and reused by every Legito module.

  2. 02

    Create the connection

    Click Create a connection. Giving it a name is optional, but a clear one such as the workspace or team name helps when several people build scenarios in the same Make organization.

  3. 03

    Authorize and save

    Follow what Legito asks for: authorize Make on the Legito page that opens, or paste the key Legito gives you. Then click Save. The module is ready and the fields it can fill appear.

First scenario

Build your first scenario with Legito

GoalWhen a new request comes in through another app, Make creates a Legito Document Record and shares it with the right reviewer.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the +. Legito has no trigger, so the first module belongs to the app where requests arrive, such as your form tool.

  2. 02

    Set up the starting app

    Pick that app's trigger, click Create a connection to link your account, and fill its fields. Each new request becomes one bundle: an item passed from one module to the next.

  3. 03

    Add Create a Document Record

    Click the + on the right, search Legito and choose Create a Document Record. Connect your Legito account, then map the request data from the first module into the fields Make lists.

  4. 04

    Share it with a reviewer

    Add Share a Document after it. Map the record from the previous module, then the reviewer's email, taken from the request or typed once. That person must be a Legito user.

  5. 05

    Test with Run once

    Send one test request, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can open Legito and check the draft and the share.

  6. 06

    Schedule and switch on

    Open Scheduling on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Switch the scenario on and it keeps going.

Modules

What can Legito do in Make?

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

Legito1

Create a Document Record

Action

In Make“Creates new External Document Record in Legito.”

Registers a new External Document Record in Legito, so a document handled elsewhere still gets its own entry next to the drafts your team builds in Legito.

When to use it
a signed agreement arrives from another tool and the legal team wants it tracked in Legito too.
Watch out
pair it with Upload a File when the file itself should sit on the new record.
Legito2

Create a Document Version

Action

In Make“Creates new Document Record with Document Version.”

Produces a Document Record and a Document Version in a single module, which saves you chaining two steps when a request should turn straight into a draft.

When to use it
a new client request should give you a working document right away.
Watch out
if the record already exists, choose Update a Document Version instead, or you end up with a duplicate record.
Legito3

Create a Label

Action

In Make“Creates a new label.”

Adds a new label to your Legito account, ready to organize documents under a name that comes from another tool.

When to use it
a new client or project appears in your CRM and you want the matching label waiting in Legito.
Watch out
no module in the list searches labels, so feed the name from one single source to avoid creating the same label twice.
Legito5

Create an Object Record

Action

In Make“Creates a new Object Record for a given Object type by its ID.”

Writes a new Object Record into one of your Legito Object types, picked by its ID, so structured data your documents rely on lives in Legito.

When to use it
a new entry created in your CRM or spreadsheet should exist in Legito as well.
Watch out
you need the ID of the Object type. Run Search Objects once to find it before building the rest.
Legito6

Create an User

Action

In Make“Creates new User with default permissions.”

Gives a newcomer a Legito account from inside a scenario. The user starts with default permissions.

When to use it
your HR or IT tool records a new hire in the legal or sales team who will work on Legito documents.
Watch out
default permissions may not match the role. Check them with Get a User Permissions and adjust them in Legito if needed.
Legito7

Create a Push Connection

Action

In Make“Creates new Push Connection from the Legito.”

Sets up a new Push Connection in Legito. Make's documentation says nothing more about what a Push Connection sends or where, so rely on Legito's own settings to understand it.

When to use it
your team already uses Push Connections and wants to create them from a scenario instead of by hand.
Watch out
after Run once, open Legito and confirm the connection looks the way you expected.
Legito8

Delete a Document Record

Action

In Make“Deletes a document record.”

Removes a Document Record from Legito when the scenario reaches this module, which keeps abandoned drafts from piling up.

When to use it
a deal is marked as lost in your CRM and its draft contract should disappear.
Watch out
a delete cannot be undone from Make. Test with Run once on a throwaway record before you switch the scenario on.
Legito9

Delete a File

Action

In Make“Deletes existing file attached to specified Document Record.”

Clears one attachment from a Document Record, leaving the record itself in place for the rest of the process.

When to use it
an outdated appendix was replaced by a newer copy and the old one should not stay attached.
Watch out
the module needs to know which file to remove. List Files, placed just before, gives you the attachments of that record to pick from.
Legito11

Delete an Object Record

Action

In Make“Deletes existing Document Record.”

Removes an Object Record when data behind your documents becomes obsolete, such as an entry deleted in your source tool.

When to use it
a record was archived in your CRM and should leave Legito too.
Watch out
the directory's one-line description of this module mentions a Document Record, so check on a test record exactly what disappears before activating.
Legito12

Download a Document Version

Action

In Make“Downloads Document Version as base64 encoded file.”

Exports a Document Version as a base64-encoded file that the next module can pick up and send elsewhere.

When to use it
the final version of a contract should be copied to your cloud storage or attached to an email.
Watch out
the file arrives encoded in base64. After Run once, check that the receiving module accepts it before you switch the scenario on.
Legito13

Download a File

Action

In Make“Downloads a File from selected Document Record in encoded format.”

Retrieves a file attached to a Document Record, in encoded format, so it can travel to another app in the scenario.

When to use it
attachments such as scans or annexes need a copy in your archive or document storage.
Watch out
this module handles attached files. For the Legito document itself, Download a Document Version is the one to use.
Legito14

Get a Document Version Data

Action

In Make“Returns a list of Elements data from a Document Version.”

Reads the Elements data of a Document Version and returns it as a list, so values filled in a Legito document can be reused in later modules.

When to use it
figures or names from a finished document should flow into a spreadsheet or a CRM.
Watch out
open the bundle after Run once to see what the list holds before you map anything.
Legito15

Get a User Permissions

Action

In Make“Returns a list of permissions for a specified user.”

Tells you which permissions a given Legito user holds, as a list you can log or test in the next module.

When to use it
before sharing a sensitive document, or when you audit access after Create an User.
Watch out
the module only reports. Changing a permission still happens in Legito, since none of the listed modules edits permissions.
Legito16

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Legito API from your scenario, using the same connection as the other Legito modules.

When to use it
you need something the named modules do not cover, and you know which API request does it.
Watch out
you write the request yourself, and Make's documentation for Legito is limited, so keep Legito's own API reference open while you build.
Legito17

Share a Document

Action

In Make“Shares Document Record to a Legito user specified by email.”

Hands a Document Record to a Legito user, identified by email, so the right person finds it in their Legito workspace.

When to use it
a draft is ready and the reviewer is known from the request or from your CRM.
Watch out
the email must belong to a Legito user. For someone outside the account, Create an External Link is the right module.
Legito18

Update a Document Record

Action

In Make“Updates properties of Document Records like Summary, Signing Date, or Expiration.”

Changes properties of existing Document Records, such as the Summary, the Signing Date or the Expiration, without opening Legito.

When to use it
your signature tool reports a signed contract and Legito should record the date.
Watch out
the module works on records that already exist. Search Document Records placed before it helps you target the right one.
Legito19

Update a Document Version

Action

In Make“Creates new Document Version for existing Document Record.”

Adds a new Document Version to a Document Record you already have, so revisions stay grouped under the same record.

When to use it
a client sends corrected information and the contract has to be regenerated.
Watch out
despite its name, the directory describes this module as creating a version. Expect a new version on the record rather than an edited one.
Legito20

Update an Object Record

Action

In Make“Updates an object record.”

Edits an Object Record already stored in Legito, which keeps the data your documents draw on in step with your other tools.

When to use it
a detail changes in your CRM and the same entry in Legito should follow.
Watch out
identify the record first. Search Object Records returns it from its Object type, so you can map the right one.
Legito21

Upload a File

Action

In Make“Uploads a File to a specified Document Record.”

Attaches a file coming from another module to the Document Record you point to, so every piece of a deal sits in one place.

When to use it
a signed PDF or an annex arrives by email or in storage and belongs with its Legito record.
Watch out
on the Make Free plan, files are capped at 5 MB. Large scans or bundled annexes therefore call for a paid plan.
Legito22

Get Template Suites

Search

In Make“Lists all Template Suites.”

Lists all the Template Suites in your Legito account, one bundle per suite, useful to see what is available before creating documents.

When to use it
you are setting up a scenario and need to know which suite a new document should come from.
Watch out
as a search, it returns several bundles, and each one runs the modules placed after it.
Legito23

List Events

Search

In Make“Returns list of events.”

Returns Legito's list of events, which you can copy to a log or a spreadsheet for a trace of what happened.

When to use it
your team wants a running record of Legito activity outside Legito.
Watch out
Make's documentation does not say which events are included. Run the module once and read the bundles before you build on it.
Legito24

List Files

Search

In Make“Lists all files attached to a selected Document Record.”

Shows every file attached to a chosen Document Record, one bundle per file, so the next module can handle each attachment.

When to use it
before Download a File or Delete a File, to know exactly which attachments a record carries.
Watch out
a record with many attachments produces many bundles, and each module after it counts one operation per bundle.
Legito25

List Shares

Search

In Make“Lists sharing given by specified Document Record.”

Returns the shares given on a Document Record, a quick way to see who can open it.

When to use it
an access check before signature, or an audit trail for a sensitive contract.
Watch out
when the record has no share, the search returns zero bundles and the modules after it do not run, which can look like a silent failure.
Legito26

List Users

Search

In Make“Lists all users or a specific user by email.”

Brings back every Legito user, or a single one when you give an email, so the scenario knows who exists in the account.

When to use it
checking that a reviewer is a Legito user before Share a Document.
Watch out
without an email, all users come back as bundles, and each following module spends an operation per user.
Legito27

Search Document Records

Search

In Make“Returns a list of all Document Records.”

Pulls the list of all Document Records, the usual way to find the record a later module should change.

When to use it
before Update a Document Record or Upload a File, to get the right record from Legito.
Watch out
every record becomes a bundle. On a large account, the modules after it can burn through many operations in a single run.
Legito28

Search Object Records

Search

In Make“Retrieves object record of specified object type by its object ID.”

Retrieves the Object Records of one Object type, given by its object ID, so you can reuse their data or update them.

When to use it
looking up the entry to change before Update an Object Record or Delete an Object Record.
Watch out
you need the object ID first. Search Objects gives it to you.
Legito29

Search Objects

Search

In Make“Returns all Objects.”

Returns all the Objects defined in your Legito account, mostly a setup helper that reveals the IDs the object modules need.

When to use it
building a scenario with Create an Object Record or Search Object Records for the first time.
Watch out
run it with Run once, note the ID you need, then leave it out of the finished scenario if nothing else uses it.
Need help

Need help automating Legito with Make?

A person reads every message.

FAQ

Legito and Make: frequent questions

01Is the Legito Make integration free?
Yes, Legito is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 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 lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one per module per bundle. Your Legito subscription is a separate matter that this page does not cover.
02What do you need to connect Legito to Make?
A Legito account and a Make account. Make's documentation for Legito lists no prerequisite and no specific steps, so the generic path applies: add any Legito module, click Create a connection, name it if you like, authorize Make on the Legito page or paste the key Legito provides, then click Save. The same connection then serves all 29 Legito modules in every scenario you build. Use a Legito account that can open the documents your scenarios will work on, since every module acts through it.
03Does the Legito Make integration react in real time?
No, because Legito has no trigger module in Make. A scenario therefore starts from something else. The first option is a trigger from another app, such as a form or a CRM, placed in front of the Legito modules. The second is the schedule: the scenario runs on its own, every 15 minutes by default, and a search such as Search Document Records opens the flow. The Free plan keeps at least 15 minutes between scheduled runs, paid plans go down to 1 minute.
04What if a Legito module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Legito API with the connection you already set up, so the 29 listed modules are not a hard ceiling. You write the request yourself, which means reading Legito's API reference, since Make states that its own documentation for Legito is limited. If what you need is the missing trigger, start the scenario from another app or from the schedule instead.
05Should you use Make or n8n for Legito?
It depends on your team rather than on Legito alone. On Make, Legito comes with 29 ready modules plus Make an API Call, and it runs from the Free plan. The same app often has a node in n8n as well, so check it there before deciding. Compare the modules each side offers for what you want to automate, and which tool your team already knows. The n8n vs Make comparison on this site lays out the criteria without picking a winner.
Same platform

Other docs you might need on this stack.

Browse all integrations