Resources · Make integration

Lokalise Make integrationAutomate Lokalise with Make.

Can Lokalise tell the rest of your stack when a language, task or order changes? With the Lokalise Make integration it can: 20 modules, 4 of them instant triggers, and no code. This guide is for localization and product teams, and it walks you from connection to a first working scenario.

Try the Lokalise integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Lokalise Make integration automate?

The Lokalise Make integration links your Lokalise account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Lokalise then reacts to what happens in your projects and hands the work to your other apps, without a line of code.

Languages that come with their own to-do list. Watch a Language fires when someone adds a language to a project. Follow it with Create a Task and the translation work is assigned before anyone has to remember it.

Orders that keep finance and project leads in the loop. Watch an Order reacts when a translation order is created, completed or deleted. Get an Order then fetches its details so you can post them to a chat channel or log them in a spreadsheet app.

Files that travel on their own. Upload a File pushes source files into a project when they are ready elsewhere, and Download a File pulls the project files back out when a task closes, which Watch a Task can detect.

Every Lokalise trigger here is instant, so there is no polling interval to tune. Where the 20 listed modules stop, Make an API Call reaches the rest of the Lokalise API with the same connection. The Make documentation page for Lokalise flags its content as AI-generated from the vendor docs, so double-check anything critical with Lokalise itself. The same app often exists as an n8n node too; the n8n vs Make comparison helps you pick. New to the editor? The Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect Lokalise to Make?

  1. 01

    Generate an API token in Lokalise

    You need an active Lokalise account. Click your avatar in the bottom left corner, open Profile settings, then API tokens. Click Generate new token, pick the token type, click Generate and copy the token from the list.

  2. 02

    Add a Lokalise module in Make

    In your scenario, add any Lokalise module and click Create a connection. A connection is your Lokalise account linked to Make once, then reused by every Lokalise module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the token and save

    Paste the API token you copied, or follow the on-screen instructions, and confirm. Make can now read your Lokalise projects and list them for you in the module fields.

First scenario

Build your first scenario with Lokalise

GoalWhen a language is added to a Lokalise project, Make creates a task in that project for the translators.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for Lokalise and pick Watch a Language as the first module.

  2. 02

    Set up the webhook and connection

    Click Create a webhook, then Create a connection with your API token. Once connected, Make lists the Lokalise projects it can read, so you choose rather than type.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger and add Create a Task. Map the project and language data that came from Watch a Language into the task fields.

  4. 04

    Test with Run once

    Click Run once, then add a language to a test project in Lokalise. Open each module to read the bundle it received: a bundle is one item passed from a module to the next, here one language change.

  5. 05

    Switch the scenario on

    If the task shows up in Lokalise, switch the scenario on. Because the trigger is instant, it runs whenever Lokalise sends a language change, and each module run counts as one operation on your Make plan.

Triggers

Lokalise triggers in Make

4 modules start a scenario when something happens in Lokalise. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Lokalise as soon as it happens.

Lokalise1Watch a Language

Watch a Language

Instant trigger

In Make“Triggers when a language is added, deleted or language settings are changed.”

Your scenario starts the moment a language is added to a Lokalise project, removed from it, or has its settings changed. You receive one bundle describing that change, ready for the next module.

How it fires
instant: Lokalise calls Make through a webhook as soon as it happens, so there is no schedule to wait on.
When to use it
a new market opens and translators, tasks and release notes should follow without anyone relaying the news.
Watch out
one trigger covers additions, deletions and setting changes, so check in the Run once output which kind of change arrived before you map anything.
Lokalise2Watch an Order

Watch an Order

Instant trigger

In Make“Triggers when an order is created, completed or deleted.”

Translation orders stop living only inside Lokalise: this trigger wakes your scenario when an order is created, completed or deleted, so budget holders and project leads hear about it where they already work.

How it fires
instant: Lokalise calls Make through a webhook as soon as it happens.
When to use it
you want a message to the project lead the moment a vendor order is completed, so the release can move forward.
Watch out
deletions fire too; a scenario that announces every event will also announce cancelled orders.
Lokalise3Watch a Project

Watch a Project

Instant trigger

In Make“Triggers when a project is imported, exported or deleted.”

Hand the next step to Make each time a Lokalise project is imported, exported or deleted. The trigger passes one bundle per event, which makes it a clean starting point for file handoffs and housekeeping.

How it fires
instant: Lokalise calls Make through a webhook as soon as it happens.
When to use it
an export has just finished and you want Download a File to fetch the result and share it with the developers.
Watch out
when you add it, click Create a webhook first, then Create a connection, as the Make documentation asks for instant modules.
Lokalise4Watch a Task

Watch a Task

Instant trigger

In Make“Triggers when a new task is created, closed or deleted.”

Know when translation work moves: this trigger fires when a task is created, closed or deleted in Lokalise, and hands the task data to the rest of your scenario.

How it fires
instant: Lokalise calls Make through a webhook as soon as it happens.
When to use it
a reviewer closes a task and the product manager should get the news right away, together with the details fetched by Get a Task.
Watch out
if the same scenario also runs Create a Task, every task it creates fires this trigger again, so keep those two in separate scenarios.
Modules

Lokalise actions and searches in Make

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

Lokalise1

Create a Branch

Action

In Make“Creates a new branch for project.”

Gives a Lokalise project a new branch, so work for one feature can be kept apart from the rest of the project until it is ready to merge back.

When to use it
a developer starts a feature and you want the matching Lokalise branch created from the same event, without a manual request.
Watch out
this module only creates; renaming an existing branch is the job of Update a Branch Name.
Lokalise2

Create an Order

Action

In Make“Creates a translation order.”

Places a translation order in Lokalise from your scenario, so buying translations becomes a step that follows an event instead of a form someone has to fill in.

When to use it
content has been approved in another tool and should go out for professional translation straight away.
Watch out
each bundle it receives places a real order, so test with Run once on a sandbox project before switching the scenario on.
Lokalise3

Create a Project

Action

In Make“Creates a project.”

Sets up a fresh Lokalise project from Make, which saves the repetitive setup whenever a new app, site or client lands on your desk.

When to use it
a deal is marked as won in your CRM and the localization space for that client should exist before the kickoff.
Watch out
the scenario creates one project per bundle it receives, so a trigger that sends several items will create several projects.
Lokalise4

Create a Task

Action

In Make“Creates a task in project.”

Assigns translation or review work inside a Lokalise project, so nobody has to remember to open the task list after an upstream change.

When to use it
a new language has just been added, or new source content has been uploaded, and translators should see a task waiting for them.
Watch out
paired with Watch a Task in the same scenario, each created task fires the trigger again; keep them apart.
Lokalise5

Delete a Project

Action

In Make“Deletes a Project.”

Removes a whole Lokalise project from a scenario, which keeps your workspace tidy when a product or client is retired elsewhere.

When to use it
a client contract is closed in your CRM and its localization project should disappear as part of the offboarding.
Watch out
a delete does not come back; test on a throwaway project and map the right project from the previous module before you switch the scenario on.
Lokalise6

Delete a Task

Action

In Make“Deletes a task from the project.”

Clears a task out of a Lokalise project, useful when the work it described no longer exists and an open task would only confuse translators.

When to use it
a feature is cancelled in your project tool and the translation task created for it should go too.
Watch out
the task is gone for good; if you only want to mark it as finished, Update a Task is the safer choice.
Lokalise7

Download a File

Action

In Make“Downloads project files.”

Pulls your project files out of Lokalise and into the scenario. From there, translated content can go to storage, to a code repository or straight to a teammate, and nobody has to run a manual export.

When to use it
Watch a Project reports a finished export, or Watch a Task reports a closed review, and the files should move on.
Watch out
Make's Free plan stops at 5 MB per file. Big exports? Check their size first.
Lokalise8

Get an Order

Action

In Make“Retrieves information about specific order.”

Fetches the full details of one translation order, handy when a trigger only gives you part of the picture and the next module needs more.

When to use it
Watch an Order fires on completion and you want to post the order details to the finance channel.
Watch out
it reads one specific order. Map it from the previous module instead of typing a fixed value, or every run will fetch the same one.
Lokalise9

Get a Project

Action

In Make“Retrieves projects details.”

Reads the details of one Lokalise project, so later modules can reuse its details without you copying anything by hand.

When to use it
a task event arrives and the message you send should include the project it belongs to.
Watch out
it targets a single project; to go through all of them, List Projects is the module to pick instead.
Lokalise10

Get a Task

Action

In Make“Gets information about specific task.”

Loads everything Lokalise knows about one task, which turns a bare task event into a message a person can actually act on.

When to use it
Watch a Task reports a closed task and the product manager should receive its full details in a chat message.
Watch out
every call is one operation on your plan, so fetch details only when the next module really uses them.
Lokalise11

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Lokalise API with the connection you already set up, so you are not stuck when the listed modules stop short of what you need.

When to use it
your case involves a Lokalise feature with no dedicated module here, and you know which API endpoint handles it.
Watch out
you write the request yourself, so keep the Lokalise API reference open and check the answer with Run once.
Lokalise12

Update a Branch Name

Action

In Make“Updates a branch name in the project.”

Renames an existing branch in a Lokalise project, keeping branch names aligned with how your developers refer to the feature.

When to use it
a feature is renamed in your development tools and the Lokalise branch should follow so nobody translates in the wrong place.
Watch out
it changes the name only; to open a new branch instead, reach for Create a Branch.
Lokalise13

Update a Task

Action

In Make“Updates the properties of a task.”

Edits the properties of a task that already exists, so a Lokalise task can keep pace with decisions made in other tools.

When to use it
a release date moves in your project tool and the matching translation task should reflect the change.
Watch out
map the task from an earlier module such as Get a Task, or the scenario will not know which task to edit.
Lokalise14

Upload a File

Action

In Make“Uploads a file.”

Sends a file into Lokalise from your scenario, so new source strings reach translators as soon as they exist somewhere else.

When to use it
a developer drops an updated language file in cloud storage and it should land in the Lokalise project without a manual upload.
Watch out
the Make Free plan limits files to 5 MB, so check file size before relying on it for large projects.
Lokalise15

Get Translation

Search

In Make“Gets one translation for one key by language ISO.”

Returns one translation for one key in the language you name by its ISO code, which lets other tools reuse approved wording without a full file download.

When to use it
a support tool needs the Spanish version of a single interface string to answer a customer.
Watch out
as a search, it can return zero results; plan what the next module does when the key has no translation yet.
Lokalise16

List Projects

Search

In Make“Lists all projects.”

Brings back every Lokalise project your connection can see, one bundle per project, so a scenario can work across your whole account.

When to use it
you want a single overview of all projects written into a spreadsheet app for the team lead.
Watch out
each project becomes its own bundle, and every module after it runs once per project, which adds operations quickly.
Need help

Need help automating Lokalise with Make?

A person reads every message.

FAQ

Lokalise and Make: common questions

01Is the Lokalise Make integration free?
Yes, on the Make side. Lokalise is a standard app, so it is available from the Make Free plan. That plan allows 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) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. You still need an active Lokalise account, whose subscription is described on the Lokalise pricing page.
02What do you need to connect Lokalise to Make?
An active Lokalise account and an API token. In Lokalise, click your avatar in the bottom left corner, go to Profile settings, then API tokens, click Generate new token, choose the token type, click Generate and copy the token. In Make, add a Lokalise module, click Create a connection, optionally name it, and paste the token. For any of the four instant triggers, click Create a webhook first and then Create a connection. The same connection then serves every Lokalise module in your scenarios.
03Do Lokalise triggers in Make fire in real time?
Yes. All four Lokalise triggers (Watch a Language, Watch an Order, Watch a Project and Watch a Task) are instant: Lokalise calls Make through a webhook as soon as the event happens, and the lightning badge on the module shows it. There is no polling interval to set for them, so the 15 minute default schedule of a new scenario does not apply to these triggers. Each event arrives as one bundle, and each module that processes it counts as one operation on your Make plan.
04What if a Lokalise module is missing in Make?
Use Make an API Call. It is part of the Lokalise app in Make and calls any endpoint of the Lokalise API with the connection you already have, so a feature without a dedicated module is still reachable. You write the request yourself, which means checking the Lokalise API reference first and testing with Run once. Also keep in mind that the Make documentation for Lokalise is marked as AI-generated from the vendor docs and may contain mistakes, so confirm important details with Lokalise directly.
05Make or n8n for Lokalise automations?
It depends on the tool your team already uses. In Make, Lokalise comes with 20 modules, including 4 instant triggers and Make an API Call for anything they do not cover, and the whole setup is visual. The same app often exists as an n8n node as well, so check the n8n catalog before deciding. A fair way to choose is to list the Lokalise events and actions your process needs, then confirm the tool you prefer covers each of them. Neither choice is wrong if the modules you need are there.
Same platform

Other docs you might need on this stack.

Browse all integrations