Resources · Make integration

BeLazy Make integrationAutomate BeLazy with Make.

What if approved translation projects moved forward on their own? The BeLazy Make integration offers 41 modules: 1 trigger, 31 actions and 9 searches. This guide is for language teams using BeLazy, and walks you through the connection and a first working scenario.

Try the BeLazy integration on MakeSee the 41 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the BeLazy Make integration do for you?

The BeLazy Make integration links your BeLazy account to Make, so project steps you repeat by hand run as an automation. Make calls that automation a scenario: a chain of modules, where each module is one brick, such as a trigger that watches BeLazy or an action that changes something in it.

Approved projects that get picked up without a reminder. Watch New Approved Project spots newly approved work, Acknowledges Project confirms it, and Set Vendor For Project hands it to the person your rules choose.

Offers sorted before anyone opens them. List Opportunities reads the waiting offers; a router then sends each one to Accept An Opportunity or Dismiss An Opportunity. Files from a form, like the ones collected with the 123FormBuilder Make integration, can also go through Create Workspace and Add File To Workspace to become a new opportunity.

Deliveries that close the loop. Download Deliverable copies finished work to your storage, and Deliver Entire Project or Signal Project Delivery updates the status.

What to keep in mind: the doc lists these modules by name without describing them, and flags its own content as AI generated, so confirm each result with a test run. When something breaks, Make troubleshooting helps. Deciding between tools? Read n8n vs Make, since the same app often has an n8n node too.

Connect

How do you connect BeLazy to Make?

  1. 01

    Copy your BeLazy API key

    You need an active BeLazy account with API access. In BeLazy, open the profile menu, click Api access tokens and copy the API key shown on screen. Keep it at hand for the next step.

  2. 02

    Add a BeLazy module

    In your Make account, open a scenario and add any BeLazy module, for example Watch New Approved Project. Then click Create a connection. A connection is your BeLazy account linked to Make once, and every BeLazy module reuses it.

  3. 03

    Paste the key and save

    If you like, give it a label in the Connection name field, useful when you manage several accounts. Paste the API key, or follow the instructions on screen, then save. Make can now read your BeLazy data.

First scenario

Your first scenario: confirm every approved project

GoalWhen a project is approved in BeLazy, Make acknowledges it and lists its files for you.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor. Search for BeLazy and pick Watch New Approved Project.

  2. 02

    Link your account

    Click Create a connection and paste your API key. Once the connection exists, Make shows the options it can read from BeLazy, so you pick them instead of typing them.

  3. 03

    Add the acknowledgment

    Click the + on the right of the trigger, add Acknowledges Project and map the project that the trigger returned. Each approved project now gets confirmed.

  4. 04

    List the project files

    Add List Files In Project after it, mapped on the same project. Its output is one bundle per file, ready for a storage or email module later on.

  5. 05

    Test with Run once

    Approve a test project in BeLazy, then click Run once. Open the bubble above each module to read the bundles it received and check the project was acknowledged.

  6. 06

    Schedule and switch on

    On the first module, open the clock: the default schedule is every 15 minutes, which is also the shortest on the Free plan. Save, then switch the scenario on.

Triggers

What can start a BeLazy scenario?

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

BeLazy1Watch New Approved Project

Watch New Approved Project

triggerIn the docs only

Watch New Approved Project picks up the projects approved in BeLazy since its last check, so the follow up work begins without anyone watching the list. Every approved project reaches the next modules as its own bundle, one item passed from module to module.

How it fires
it is a scheduled trigger, meaning Make checks BeLazy at the pace set on the scenario, every 15 minutes by default, and at least 15 minutes apart on the Free plan.
When to use it
as the first module of any flow that should react to newly approved work, such as assigning a vendor or copying source files.
Watch out
the doc gives the name only, so run it once on a test project to see what each bundle holds.
Modules

What can the BeLazy modules do?

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

BeLazy1

Accept An Opportunity

ActionIn the docs only

Accept An Opportunity says yes to a BeLazy opportunity for you, so the offer turns into work without a click in BeLazy. The doc gives only the name, so confirm the exact effect on a test.

When to use it
Use it right after List Opportunities or Get Opportunity, once a filter has kept only the offers your team really wants.
Watch out
Accepting commits your team, so test it with Run once on an opportunity you would accept anyway.
BeLazy2

Acknowledges Project

ActionIn the docs only

Acknowledges Project, judging by its name, tells BeLazy a project has been taken in hand, sparing the project manager a manual confirmation per job. The doc gives the name only, so check the result in BeLazy after a test.

When to use it
Place it straight after Watch New Approved Project when every approved project should be confirmed as soon as the scenario picks it up.
Watch out
If some projects need a human look first, put a filter between the trigger and this module instead of acknowledging everything.
BeLazy3

Add File To Workspace

ActionIn the docs only

Add File To Workspace puts a file into one of your BeLazy workspaces, next to the rest of the job, without dragging it in by hand.

When to use it
Reach for it when a scenario receives a document from another app, such as an email attachment, and that document belongs to a workspace you already have.
Watch out
It works on a file, and an upload module usually comes first; run the scenario once and read the bundles to see which one fits your case.
BeLazy4

Add/Update Deliverable

ActionIn the docs only

Add/Update Deliverable writes a deliverable onto a project: it creates one when none exists, and its name suggests it refreshes the one already there otherwise. The finished work reaches BeLazy without a manual upload.

When to use it
Pick it when a translated file comes back from a tool outside BeLazy and has to be attached to the matching project.
Watch out
Because the same module can overwrite, map the project and the deliverable carefully before you switch the scenario on.
BeLazy5

Clear Vendor Of Project

ActionIn the docs only

Clear Vendor Of Project removes the vendor assigned to a project, which frees the job so it can be handed to someone else. It is the undo of Set Vendor For Project.

When to use it
Use it when a vendor declines or drops out, and the scenario should reset the assignment before Set Vendor For Project picks a new one.
Watch out
Clearing leaves the project without anyone on it, so chain the new assignment in the same scenario if the gap would cause trouble.
BeLazy6

Create Opportunity From Workspace

ActionIn the docs only

Create Opportunity From Workspace turns the content of a workspace into an opportunity, so a batch of files becomes an offer that someone can accept. Next to the (Basic) variant, it looks like the fuller of the two.

When to use it
Choose it when you want to set more than the basics on the new opportunity, and the files are already sitting in the workspace.
Watch out
Add the files with Add File To Workspace before this module runs, otherwise the opportunity may start empty.
BeLazy7

Create Opportunity From Workspace (Basic)

ActionIn the docs only

Create Opportunity From Workspace (Basic) produces the same kind of opportunity from a workspace, with, judging by the (Basic) label, fewer settings to fill. For a first scenario that means less to map and fewer chances to get a field wrong.

When to use it
Start with this one while you learn the flow, then move to the full version if you find a setting missing.
Watch out
The doc does not list which settings the basic version drops, so compare both modules in the editor before you decide.
BeLazy8

Create Workspace

ActionIn the docs only

Create Workspace sets up a fresh workspace in BeLazy, a place to gather files before they turn into an opportunity. The scenario builds it for you instead of someone opening BeLazy each time.

When to use it
Use it at the start of a flow that receives a new batch of documents from a client form or a shared drive.
Watch out
Keep the new workspace from the output bundle and map it into Add File To Workspace, or the next module will not know where to put anything.
BeLazy9

Delete Deliverable

ActionIn the docs only

Delete Deliverable removes a deliverable from a project, which keeps a wrong or outdated file from reaching the client. It cleans up what Add/Update Deliverable put there.

When to use it
Pick it when a check later in the scenario finds that the file sent back is the wrong version.
Watch out
Test it on a throwaway project first, since the doc says nothing about getting a deleted deliverable back.
BeLazy10

Delete File

ActionIn the docs only

Delete File gets rid of a file in BeLazy, so leftovers and duplicates do not pile up. The doc does not say whether it targets project or workspace files, so check this in the editor fields.

When to use it
Use it at the end of a flow, once the file has been copied where it needs to be and the original is no longer useful.
Watch out
Like every delete, it is final: add a filter so only the files you mean to remove ever reach it.
BeLazy11

Delete Workspace

ActionIn the docs only

Delete Workspace removes a whole workspace, which keeps your BeLazy account tidy after a batch has done its job. It is the last step of the workspace life cycle that Create Workspace started.

When to use it
Place it after the opportunity has been created and accepted, when the workspace has nothing left to offer.
Watch out
Everything inside goes with it, so never map this module on a workspace chosen by a search that can return several items.
BeLazy12

Deliver Entire Project

ActionIn the docs only

Deliver Entire Project, as its name says, delivers a whole project in one go, which saves the project manager from closing each item by hand.

When to use it
Use it when every deliverable of the project is ready and nothing else needs to be sent separately.
Watch out
If only part of the work is done, go with Deliver Project Item instead so you do not close the project too early.
BeLazy13

Deliver Project Item

ActionIn the docs only

Deliver Project Item hands over one item of a project while the rest stays open. You get partial delivery without waiting for the full job.

When to use it
Choose it on projects split into several pieces, when each piece should go out as soon as it is ready.
Watch out
Each call handles one item, so a project with many pieces costs one operation per item when you loop over them.
BeLazy14

Dismiss A Project

ActionIn the docs only

Dismiss A Project sets aside a project your team will not handle, so it stops showing up among the jobs waiting for an answer. It works on projects, not on opportunities.

When to use it
Use it behind a filter that spots the jobs you never take, for example a language pair you do not cover.
Watch out
Test the filter first with Run once and read the bundles, because a wrong condition would dismiss good work.
BeLazy15

Dismiss An Opportunity

ActionIn the docs only

Dismiss An Opportunity declines an offer on your behalf, which keeps the list of opportunities down to the ones worth a look. It is the counterpart of Accept An Opportunity.

When to use it
Pair it with List Opportunities and a router: one branch accepts, the other dismisses whatever does not match your rules.
Watch out
Once dismissed, the offer may be gone for good, so check the rule on a few real opportunities before you activate the scenario.
BeLazy16

Download Deliverable

ActionIn the docs only

Download Deliverable pulls the file of a deliverable into the scenario, so you can pass it to storage, email or another tool. The file travels as data from one module to the next.

When to use it
Pick it when finished work must be archived outside BeLazy or sent to a client through another channel.
Watch out
On the Free plan, files over 5 MB are refused, so large deliverables need a paid plan.
BeLazy17

Download File

ActionIn the docs only

Download File brings a BeLazy file into your scenario as data, ready to be copied, attached or processed by the next module. It is the general purpose sibling of Download Deliverable.

When to use it
Use it when the file you need is a source document rather than a finished deliverable.
Watch out
The Free plan caps files at 5 MB and total transfer at 512 MB, which a few heavy documents can reach.
BeLazy18

Get Connection

ActionIn the docs only

Get Connection returns the details of one connection set up in BeLazy, so the scenario can read its current state before acting. It is a read only module and changes nothing.

When to use it
Reach for it before Synchronize Connection, to check which connection you are about to refresh.
Watch out
Do not confuse it with your Make connection: this one reads a connection that lives inside BeLazy itself.
BeLazy19

Get Deliverable

ActionIn the docs only

Get Deliverable fetches one deliverable and its details, giving the next modules something precise to work with. Nothing is modified on the BeLazy side.

When to use it
Use it when you already know which deliverable you want, and need its data before downloading or replacing it.
Watch out
If you only know the project, start with List Deliverables Of Project to find the one you need.
BeLazy20

Get File In Workspace

ActionIn the docs only

Get File In Workspace reads the details of one file sitting in a workspace, so you can check it before moving on. It does not bring the file itself, only what BeLazy knows about it.

When to use it
Pick it to confirm a file really landed in the workspace after Add File To Workspace.
Watch out
To get the actual content into the scenario, follow it with Download File.
BeLazy21

Get Opportunity

ActionIn the docs only

Get Opportunity pulls the full picture of one opportunity, so a filter can decide what to do with it. It reads and never answers the offer by itself.

When to use it
Use it between a list and a decision, when the list does not carry enough detail to accept or dismiss.
Watch out
Each call costs an operation, so on long lists filter first on what List Opportunities already returns.
BeLazy22

Get Project

ActionIn the docs only

Get Project returns the details of one project, handy when the trigger gives you just enough to identify the job. The next modules can then map everything they need.

When to use it
Place it right after Watch New Approved Project if you want more than the trigger hands over.
Watch out
Run once and compare both outputs, since the doc does not say what the trigger already includes.
BeLazy23

Get Workspace

ActionIn the docs only

Get Workspace reads one workspace and its details, so the scenario can check its state before adding files or creating an opportunity. It changes nothing in BeLazy.

When to use it
Use it when a workspace was created earlier in another scenario and you need to pick it up again.
Watch out
If you do not know which workspace to target, List Workspaces gives you the choices first.
BeLazy24

List Connections

SearchIn the docs only

List Connections returns the connections configured in BeLazy, one bundle per connection. You get an overview without opening the settings.

When to use it
Use it to feed Synchronize Connection for each connection, or to keep an inventory in a sheet.
Watch out
A search can come back with zero, one or many bundles, and every following module runs once per bundle.
BeLazy25

List Deliverables Of Project

SearchIn the docs only

List Deliverables Of Project returns every deliverable attached to one project, each as its own bundle. That makes it easy to download or check them one after the other.

When to use it
Pick it before Download Deliverable when a project has several files to archive.
Watch out
An empty result simply stops the flow for that project, which is normal and not an error.
BeLazy26

List Files In Project

SearchIn the docs only

List Files In Project gives you the files of a project as separate bundles, so each one can be handled on its own. It is the entry point for moving source files around.

When to use it
Use it after the trigger when every approved project should have its files copied somewhere else.
Watch out
Many files mean many bundles, and so many operations for every module that comes after.
BeLazy27

List Files In Workspace

SearchIn the docs only

List Files In Workspace returns what is currently inside a workspace, one bundle per file. You see the content before you turn it into an opportunity.

When to use it
Choose it to check that all expected documents are there before Create Opportunity From Workspace runs.
Watch out
It reads workspaces only; for files attached to a project, List Files In Project is the right module.
BeLazy28

List Languages

SearchIn the docs only

List Languages returns the languages BeLazy knows, which helps you match what another tool sends with what BeLazy expects. It is reference data rather than project data, judging by its name.

When to use it
Use it when a form or a sheet names languages its own way and you need the matching BeLazy value.
Watch out
Read its bundles once with Run once while you build, then decide whether the scenario really needs it at every run.
BeLazy29

List Opportunities

SearchIn the docs only

List Opportunities brings back the offers waiting in BeLazy, one bundle each. From there, a router can accept the good ones and dismiss the rest.

When to use it
Use it at the start of a scheduled scenario that sorts incoming offers for your team.
Watch out
The list may include offers the scenario already saw, so add a filter or a record in another app to avoid answering twice.
BeLazy30

List Projects

SearchIn the docs only

List Projects returns projects from BeLazy as separate bundles, a good base for reports or bulk updates. It reads without changing anything.

When to use it
Choose it when you need all projects matching a condition, not only the newly approved ones the trigger watches.
Watch out
A broad list can produce many bundles, so narrow it with the module settings or a filter before costly steps.
BeLazy31

List Specializations

SearchIn the docs only

List Specializations returns the specializations BeLazy knows, which helps you map a client request to the right value.

When to use it
Pick it while setting up a flow that creates opportunities and needs a valid specialization.
Watch out
Like List Languages, it is reference data; read it with Run once rather than on every execution.
BeLazy32

List Workspaces

SearchIn the docs only

List Workspaces returns your BeLazy workspaces one by one, so a scenario can pick the right one or clean up old ones. Nothing is modified.

When to use it
Use it before Delete Workspace in a tidy up flow, with a filter that keeps only the workspaces you are done with.
Watch out
Never connect it straight to a delete module without a filter in between.
BeLazy33

Make an API Call

ActionIn the docs only

Make an API Call reaches any endpoint of the BeLazy API with the connection you already set up. It covers what the other 40 modules do not.

When to use it
Use it when you need a call that none of the listed modules offers.
Watch out
You write the request yourself, so keep the BeLazy API documentation open while you fill the module.
BeLazy34

Remove File From Workspace

ActionIn the docs only

Remove File From Workspace takes a file out of a workspace, so an opportunity built from it does not carry the wrong document. It is the reverse of Add File To Workspace.

When to use it
Use it when a check finds a duplicate or an outdated version among the workspace files.
Watch out
The doc does not say whether the file is deleted or only detached, so test on a copy first.
BeLazy35

Set Vendor For Project

ActionIn the docs only

Set Vendor For Project assigns a vendor to a project, so the job lands with the right person without a manual choice. It is the step that turns an approved project into assigned work.

When to use it
Place it after Watch New Approved Project when your rules decide who handles which kind of job.
Watch out
Map the vendor from a reliable source, such as a lookup sheet, because a wrong value sends the job to the wrong person.
BeLazy36

Signal Project Delivery

ActionIn the docs only

Signal Project Delivery tells BeLazy that delivery for a project has happened, which keeps its status in line with what really went out. Its name suggests it reports the delivery rather than sending files.

When to use it
Use it when files are delivered through another channel and BeLazy only needs to know it is done.
Watch out
If BeLazy should send the work itself, Deliver Entire Project or Deliver Project Item fit better.
BeLazy37

Synchronize Connection

ActionIn the docs only

Synchronize Connection asks BeLazy to refresh one of its connections, so the data it holds matches the system behind it. You trigger the refresh from a scenario instead of the BeLazy screen.

When to use it
Use it before reading projects, when you need the freshest state of a connected system.
Watch out
Pick the connection with Get Connection or List Connections, since the module works on one at a time.
BeLazy38

Synchronize Project

ActionIn the docs only

Synchronize Project refreshes a single project in BeLazy, so its data lines up with the source it came from. It targets one job instead of a whole connection.

When to use it
Choose it when one project looks out of date and you do not want to refresh everything around it.
Watch out
If many projects need it, a List Projects step before it will run the sync once per bundle, each costing an operation.
BeLazy39

Update Workspace

ActionIn the docs only

Update Workspace changes the settings of an existing workspace, so it stays accurate while files are being gathered. It edits in place rather than creating anything new.

When to use it
Use it when details of a batch change after the workspace was created, for example when the client renames the batch.
Watch out
Map the workspace from the right module output, or you will edit a different one.
BeLazy40

Upload a file

ActionIn the docs only

Upload a file sends a file from the scenario into BeLazy, the first step before it can be attached to a workspace or a project. The file comes from an earlier module, such as a download from a storage app.

When to use it
Pick it when documents arrive through email or a drive and have to enter BeLazy without anyone handling them.
Watch out
Free plan scenarios stop at 5 MB per file, so large source documents need a paid plan.
Need help

Need help automating BeLazy with Make?

A person reads every message.

FAQ

Questions about BeLazy and Make

01Is the BeLazy Make integration free?
Yes, on the Make side. BeLazy is a standard app, so it works on the Free plan like the 3000+ standard apps. That plan allows 2 active scenarios, runs at most every 15 minutes, stops each run after 5 minutes, accepts files up to 5 MB and 512 MB of transfer. Paid plans drop the interval to 1 minute and allow 40 minutes per run. On the BeLazy side, you need an active account with API access, and the BeLazy pricing page covers that subscription.
02What do you need to connect BeLazy to Make?
An active BeLazy account with API access and a Make account. In BeLazy, open the profile menu, click Api access tokens and copy the key. In Make, add a BeLazy module, click Create a connection, name it if you want, paste the key and save. That single connection then serves every one of the 41 modules, so you only go through this once per BeLazy account. If the connection is refused, first check that the key comes from Api access tokens and that your account has API access.
03Does the BeLazy Make trigger fire instantly?
No. Watch New Approved Project is a scheduled trigger: Make checks BeLazy at the pace you set on the scenario, every 15 minutes by default. On the Free plan the shortest gap is 15 minutes, on paid plans it goes down to 1 minute. A newly approved project therefore waits until the next check. BeLazy has no instant trigger in Make, which would be the kind the app calls through a webhook as soon as something happens.
04What if a BeLazy module is missing in Make?
Use Make an API Call. It reaches any endpoint of the BeLazy API with the connection you already have, so the 40 other modules are not a ceiling. Keep in mind that the Make doc for BeLazy lists modules by name only and warns that its content is AI generated and may contain mistakes. When a module behaves differently from what you expected, check the BeLazy documentation or contact BeLazy directly.
05Should you use Make or n8n for BeLazy?
It depends on the tool your team already runs. On Make, BeLazy comes with 41 modules, a scheduled trigger for approved projects and Make an API Call for the rest, all usable on the Free plan within its limits. The same app often has an n8n node as well, so check whether one exists for BeLazy and what it covers before choosing. Compare the modules you need on each side rather than the brand.
Same platform

Other docs you might need on this stack.

Browse all integrations