Resources · Zapier integration

Lokalise Zapier integrationAutomate Lokalise with Zapier.

The Lokalise Zapier integration gives you 24 triggers, 9 actions and 12 searches. Twenty-two triggers are instant and two poll on a timer, so keys, tasks, orders and projects can start Zaps, while actions create keys, tasks and projects or move files in and out.

See the 45 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Lokalise Zapier integration does for a translation team

Lokalise is a translation management tool: projects hold keys, each key holds its translations, and tasks and orders organize who translates what. The Zapier integration connects that work to your other apps in both directions. A change in Lokalise can start an automation, and another app can create keys, tasks or projects, update translations or move files without anyone opening Lokalise.

Three results come up most. First, a team that knows when work is done: Task Closed fires as soon as a task ends, and a message lands in the chat the team already reads. Second, a running record of orders: Order Completed adds a row to a spreadsheet each time an order finishes, which gives one place to check what came back. Third, files that reach Lokalise without manual uploads: a new file in your storage tool goes to Upload File, tagged and in the right language.

Around those, the catalog covers keys, comments, languages, contributors, snapshots, imports and exports, plus twelve searches that fetch a key, a task, an order or a list mid-Zap.

What Zapier does not do for Lokalise: no action deletes a project or a task, and the only way to delete a key sits among the searches, which surprises people. Two task triggers poll instead of reacting at once. The same app also exists on Make: see the Lokalise Make integration, and weigh the tools in Make vs Zapier before you build.

Vocabulary

Zapier words, in plain English

Eight words carry this page. Read them once, the rest follows.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills: one action your Zap completes successfully. Not to be confused with a Lokalise task.
Instant vs polling
An instant trigger is reported by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
Filter
A step that lets the Zap go on only when what arrived meets a condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists, such as a key or an order, so later steps can use what it found.
Connection
Your Lokalise account linked to Zapier once, then reused by every step of every Zap that works with Lokalise.
Cost

What a Lokalise Zap really costs

Lokalise is not a premium app, so it runs on the free Zapier plan. Watching for a closed task or a new key costs nothing: only an action that succeeds is billed as a task.

  • Premium appNo, the free plan works
  • Free plan100 tasks a month, two-step Zaps
  • Trigger cost0 tasks
  • Instant triggers22 out of 24

The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. A filter, a second action or one of the twelve searches makes the Zap multi-step, which needs a paid plan. A failed action is not counted, and polling costs nothing however often Zapier checks. The interval grid below only concerns the two polling triggers, Poll Tasks and Poll Tasks' Languages' Progress; the 22 instant triggers ignore it.

Connect

Connect your Lokalise account in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. You need a Lokalise account first, with access to the projects and the team the Zap will touch.

  2. 02

    Pick Lokalise

    Type Lokalise in the search box of the dialog, select it in the results, then click Add connection. A new browser tab opens on the Lokalise side for the sign-in.

  3. 03

    Sign in and allow access

    Sign in to Lokalise in that tab and grant Zapier access to the account. The connection then shows on your Apps page, ready for every Zap that uses Lokalise.

First Zap

Your first Zap: closed tasks announced in the team chat

GoalEach time a Lokalise task is closed in your project, a message reaches the team chat, but only when it passes the filter you set.

  1. 01

    Create the Zap

    Start a new Zap in Zapier. Choose Lokalise as the trigger app and Task Closed as the event, then pick your Lokalise connection.

  2. 02

    Set the project

    Enter the Project ID of the project to watch. It is required, and the Zap only hears about tasks closed in that project.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the account, so you build the message on a real closed task rather than empty fields.

  4. 04

    Add the filter

    Click the plus icon, add Filter, then fill in the field, the rule and the value. A filter makes this a multi-step Zap, so it needs a paid plan.

  5. 05

    Write the message and publish

    Add your chat step, place the task title in the text, test it, then click Publish. Only tasks closed from now on will be announced.

Triggers

Lokalise triggers

24 events start a Zap when something happens in Lokalise, and 22 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Contributor Added

Instant trigger

In Zapier“Triggers when new contributor has been added to the project”

Starts the Zap when someone new joins a Lokalise project as a contributor. It turns a change of access into an event other tools can react to, instead of something people find out by chance.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep a shared access sheet up to date with every person added to a project.
Watch out
Project ID is required, so one Zap follows one project.
2

Contributor Removed

Instant trigger

In Zapier“Triggers when contributor has been removed from the project”

Fires when a contributor leaves a project or is taken off it. Paired with the previous trigger, it gives a full picture of who can work on what, entry and exit included.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
mark a person as removed in the same access sheet so the record stays honest.
Watch out
it watches a single project, given by its Project ID; another project needs another Zap.
3

Key Added

Instant trigger

In Zapier“Triggers when a new key is added to the project.”

Reacts when a new key appears in the project. A key is the unit Lokalise translates, so this is the earliest signal that fresh text needs work in every language.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
warn the people in charge of a language that new text is waiting.
Watch out
a large import adds many keys at once, which means many runs and, behind them, many tasks.
4

Key Comment Added

Instant trigger

In Zapier“Triggers when a new comment is added to the key.”

Fires when someone leaves a comment on a key. Comments are where questions about context live, and they are easy to miss when nobody is looking at that key.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
forward each new question on a key to the team chat so it gets an answer.
Watch out
unlike most Lokalise triggers, Zapier lists no required Project ID here, so check in the test which comments it actually returns.
5

Key Modified

Instant trigger

In Zapier“Triggers when a translation has been modified.”

Runs when a translation is modified, despite a name that suggests the key itself. In practice it follows edits to the text, which is what most review flows care about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
log every edit in a review sheet that someone checks before a release.
Watch out
if the same Zap uses Update a Translation on that project, each update counts as a modification and restarts the Zap.
6

Key Removed

Instant trigger

In Zapier“Triggers when a key is removed from the project.”

A key taken out of the project starts this one. That text no longer exists in any language, and other tools that hold a copy should know.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
flag the matching line as removed in a sheet that tracks keys outside Lokalise.
Watch out
an upload in Cleanup mode can remove many keys at once, and each one starts this Zap.
7

Language Added

Instant trigger

In Zapier“Triggers when new language has been added to the project”

Adding a new language to a project sets this trigger off. A new language usually means new work for someone, and this gets that news out without waiting for a meeting.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
open a card in your project tool to plan the work for the new language.
Watch out
Project ID is required; a language added elsewhere goes unnoticed.
8

Language Removed

Instant trigger

In Zapier“Triggers when language has been removed from the project”

Dropping a language from the project is the event here. Anything planned or billed for that language elsewhere may need to stop.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
close the matching card in your project tool so nobody keeps working on it.
Watch out
the Zap only covers the project whose Project ID you entered.
9

Language Settings Changed

Instant trigger

In Zapier“Triggers when new language has been removed from the project”

Going by its name, this one reacts when the settings of a project language change. Zapier's own description of it repeats the wording of a language removal, so the exact event deserves a test before you rely on it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
note setting changes in a project log that the team can look back on.
Watch out
run the trigger test and read what comes back before building on it.
10

Order Completed

Instant trigger

In Zapier“Triggers when an order has been completed.”

This one waits for a translation order to be completed. Orders are the work Lokalise sends out to be done, so this is the moment the result is ready to use.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
add a row per finished order to the spreadsheet that tracks orders.
Watch out
it needs both a Team ID and a Project ID, two values to have at hand before you start.
11

Order Created

Instant trigger

In Zapier“Triggers when an order has been created.”

A newly placed translation order is what wakes this trigger. It is the start of the order's life, useful for anyone who follows spending or workload.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
tell whoever approves orders that a new one was placed.
Watch out
Team ID and Project ID are both required here too.
12

Order Deleted

Instant trigger

In Zapier“Triggers when an order has been deleted.”

Fires when an order is deleted. Without it, a sheet that tracks orders keeps lines for work that no longer exists.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
strike the order from the tracking sheet as soon as it disappears.
Watch out
only a Team ID is required, so it follows orders across the team rather than one project.
13

Poll Tasks' Languages' Progress

Polling trigger

In Zapier“Polls periodically to check the progress of your tasks' languages.”

Checks how far each language of your tasks has progressed. It is one of the two Lokalise triggers that Zapier has to come and ask about, rather than being told.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
feed a progress board where the team follows languages task by task.
Watch out
Project ID is required, and Zapier skips items it has already seen, so the same progress update does not start the Zap twice.
14

Poll Tasks

Polling trigger

In Zapier“Periodically checks your Lokalise project for updates to tasks.”

Looks at your Lokalise project for updates to tasks, on Zapier's timer. Broader than the instant task triggers, it catches task changes in general rather than one specific event.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
keep a task list in another tool aligned with Lokalise.
Watch out
for a closed or created task, the instant triggers react sooner on the free plan.
15

Project Deleted

Instant trigger

In Zapier“Triggers when project has been deleted”

Deleting a project starts the Zap. Everything attached to it in other tools, from boards to sheets, loses its reason to exist.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
archive the matching folder or board elsewhere.
Watch out
it asks for the Project ID of the very project it watches, so set it up before the project goes.
16

Project Exported

Instant trigger

In Zapier“Triggers when a project export is performed.”

Reacts when an export of the project is performed. An export usually means translations are on their way to wherever they are used.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
tell the team that a fresh export exists so nobody works from an old one.
Watch out
each export starts the Zap, including ones made only for a check.
17

Project Imported

Instant trigger

In Zapier“Triggers when the import is performed into the project.”

Every import performed into the project counts as an event for this trigger. New or changed text has arrived, and that often calls for a review.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
post a note when an upload lands, so reviewers know where to look.
Watch out
Zapier lists no required Project ID for it; check in the test which imports it reports.
18

Project Snapshot

Instant trigger

In Zapier“Triggers when a snapshot is created in the project.”

Creating a snapshot of the project sets it off. A snapshot is a saved state you can go back to, so knowing one exists is reassuring before risky changes.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
record each snapshot in a log before someone runs an upload in Cleanup mode.
Watch out
Project ID is required.
19

Task Closed

Instant trigger

In Zapier“Triggers when a task is closed.”

Fires as soon as a Lokalise task is closed. It is the clearest signal that a batch of translation work is finished.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
announce the end of a task in the team chat, as in the first Zap above.
Watch out
Project ID is required, so a task closed in another project stays silent.
20

Task Created

Instant trigger

In Zapier“Triggers when a new task is created.”

Whenever a new task is created in Lokalise, this trigger starts the Zap. Work has been assigned, and the people concerned can hear about it outside Lokalise.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
mirror each new task as a card in the tool the team plans in.
Watch out
a Zap that also uses Create a Task on the same project will start itself again.
21

Task Deleted

Instant trigger

In Zapier“Triggers when a task has been deleted.”

Deleting a task in Lokalise starts this Zap. Any copy of it elsewhere, a card, a calendar entry or a line in a sheet, is now out of date and can be cleaned up without anyone having to remember it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
remove or archive the matching card in your planning tool.
Watch out
Project ID is required; deleted tasks in other projects are not reported.
22

Task Language Closed

Instant trigger

In Zapier“Triggers when a language is closed in the task.”

Fires when one language inside a task is closed, before the whole task ends. It gives a finer view than Task Closed, language by language.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
tell the reviewer of a language that their part is ready.
Watch out
a task with many languages starts the Zap once per language, so count the tasks it will cost.
23

Translation Reviewed

Instant trigger

In Zapier“Fires when a translation has been marked or unmarked as reviewed in a project.”

Marking a translation as reviewed starts it, and so does removing that mark. Both directions start the Zap, which matters if you only care about one.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
track review progress in a sheet, line by line.
Watch out
add a filter on the reviewed status if you only want one direction, knowing a filter needs a paid plan.
24

Translation Updated

Instant trigger

In Zapier“Triggers when a translation has been updated.”

Any update to a translation in a project is caught here. It sees every change to the text, whoever or whatever made it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep a copy of changed translations in another tool that displays them.
Watch out
it needs both Project ID and Team ID, and it loops if the same Zap uses Update a Translation.
Actions

Lokalise actions

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

1

Create Comment

Action

In Zapier“Adds a comment to a key.”

Posts a comment on a key. Context gathered elsewhere, a question or an answer, ends up where the people working on that key read it.

When to use it
copy a reply from the team chat onto the key it concerns.
Watch out
both Project ID and Key ID are required, so the Zap must know the exact key.
2

Create a Key

Action

In Zapier“Creates one key in the project. Requires Manage keys admin right. We recommend sending payload in chunks of up to 500 keys per request.”

Adds one key to a project, with the platforms it belongs to. The text then exists in Lokalise, ready to be translated.

When to use it
add a key when a new string is listed in your content sheet.
Watch out
Key Name and Platforms are required, and the connected user needs the Manage keys admin right.
3

Create Project

Action

In Zapier“Creates an empty Project.”

Creates an empty project in your Lokalise team. Useful when a new piece of work starts elsewhere and should get its own space in Lokalise.

When to use it
open a Lokalise project each time a new project line appears in your planning sheet.
Watch out
Team ID and Project Name are required, and the project starts empty.
4

Create a Task

Action

In Zapier“Creates a task in the project. Requires Manage tasks admin right. Keep in mind, that initial_tm_leverage attribute will be empty in server response. It's being calculated after the task is created and this process may take some time.”

Creates a task in a project, with options to close languages or the task automatically when the work is done.

When to use it
open a translation task when a request lands in another tool.
Watch out
Project ID and Title are required, and the user needs the Manage tasks admin right.
5

Download Files

Action

In Zapier“Downloads files.”

Exports the project's files so the next step can store or send them, with options for filenames, platforms and comments.

When to use it
save an export into your storage tool once a task closes.
Watch out
with original filenames turned off, all keys go into one file per language.
6

Retrieve a Translation

Action

In Zapier“Retrieves a Translation object.”

Fetches one translation by its identifier and hands it to the next step. Though listed with the actions, it reads rather than writes.

When to use it
pull the current text of a translation before sending it somewhere else.
Watch out
Project ID and Translation ID are required.
7

Update a Key

Action

In Zapier“Updates the properties of a key and it's associated objects. Requires Manage keys admin right.”

Changes the properties of an existing key, and can merge new tags with the ones it already has.

When to use it
tag a key when its status changes in another tool.
Watch out
Project ID and Key ID are required, along with the Manage keys admin right.
8

Update a Translation

Action

In Zapier“Updates a translation.”

Replaces the content of one translation, and can set its Reviewed or Unverified flags at the same time.

When to use it
push a corrected text approved elsewhere back into Lokalise.
Watch out
Project ID, Translation ID and Translation are required; plural keys expect a structured value.
9

Upload File

Action

In Zapier“Uploads a file to the project.”

Sends a file into a project, with options to tag inserted, updated or skipped keys and to apply translation memory matches.

When to use it
push a file dropped in your storage tool into Lokalise.
Watch out
Cleanup mode deletes every key missing from the file; take a snapshot first. Data, Language code and Filename are required.
Searches

Lokalise searches

12 search steps look for data that already exists in Lokalise, so a later step can use it.

A search step looks up something that already exists in Lokalise, so the steps after it can use it. Searches sit at the bottom of the action list, under SEARCH. Any Zap with a search is multi-step and needs a paid plan. One of the twelve does not search at all: it deletes.

1

Delete a Key

Search

In Zapier“Deletes multiple keys from the project. Requires Manage keys admin right.”

Deletes a key from the project, even though Zapier files it under searches. It is the only way this integration removes anything.

When to use it
remove a key once its line is struck from your content sheet.
Watch out
it needs the Manage keys admin right, and the deletion is real.
2

Retrieve a Comment

Search

In Zapier“Retrieves a Comment object.”

Brings back one comment on a key so a later step can quote or forward it.

When to use it
fetch the comment text before sending it to the chat.
Watch out
Project ID, Key ID and Comment ID are all required.
3

List Keys

Search

In Zapier“Lists all keys in the project.”

Returns all keys of a project, or only their identifiers if you turn on Simple Key Array.

When to use it
gather key identifiers before creating a task that covers them.
Watch out
Project ID is required, and the full list can be large.
4

Get Order

Search

In Zapier“Retrieves an Order object.”

Looks up one translation order and its details, so the Zap can report on it.

When to use it
enrich a message about an order with its full record.
Watch out
Team ID and Order ID are required; Lokalise points to its dev-hub for the Team ID.
5

Retrieve Project

Search

In Zapier“Retrieves a project object”

Fetches a project's details by its Project ID, the only field it asks for.

When to use it
add the project name to a message that started from a bare identifier.
Watch out
a wrong Project ID returns nothing and, by default, stops the Zap.
6

Retrieve a Task

Search

In Zapier“Retrieves a Task object.”

Finds one task and returns its details to the next step. Handy when the trigger only carried an identifier, with no title.

When to use it
read a task's title and status before posting an update about it.
Watch out
Project ID and Task ID are both required.
7

List All Orders

Search

In Zapier“Lists all translation orders in the team.”

Lists every translation order in the team, across projects.

When to use it
build a summary of orders for a report sent to the team.
Watch out
Team ID is required; Lokalise's dev-hub is where it says to find it.
8

List All Translations

Search

In Zapier“Retrieves a list of project translation items, ungrouped. You may want to request Keys resource in order to get the structured key/translation pairs for all languages.”

Returns the translation items of a project as a flat list, not grouped by key.

When to use it
collect translations for a check outside Lokalise.
Watch out
for key and translation pairs per language, List Keys gives a more structured view.
9

List Key Comments

Search

In Zapier“Retrieves a list of all comments for a key.”

Retrieves every comment left on a key, so the whole discussion can travel together. A single comment often lacks the context of the ones before it.

When to use it
attach a key's full comment thread to a review card.
Watch out
Project ID and Key ID are required.
10

List Project Languages

Search

In Zapier“Retrieves a list of project languages.”

Lists the languages of a project, which tells later steps how many versions to expect. The answer follows languages as they are added or removed, so it shows the project as it stands now.

When to use it
check which languages exist before creating a task for them.
Watch out
only Project ID is required.
11

List All Tasks

Search

In Zapier“Lists all tasks in the project.”

Lists all tasks in a project in one go, open or not.

When to use it
send a digest of a project's tasks to the people who follow it.
Watch out
Project ID is required; to pass every task on rather than only the first, change If multiple search results are found?.
12

Retrieve a Key

Search

In Zapier“Retrieves a Key object.”

Fetches one key and its details by identifier. Before a Zap comments on a key or changes it, this makes sure the steps after it work on the right one.

When to use it
read a key's name before commenting on it or updating it.
Watch out
Project ID and Key ID are both required.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. Lokalise offers no find-or-create, so it does not appear on these searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on.
When it breaks

When a Lokalise Zap breaks

Zapier links no help article to Lokalise, and no app-specific limit is on record. The cases below come from how every Zap behaves and from the fields Lokalise asks for.

Most failures are not bugs: the Zap does what it was told, at a moment nobody expected. For other cases, see our Zapier troubleshooting guide.

  • Past work never shows up

    A Zap only reacts to what happens after you switch it on. Tasks closed or keys added before stay in Lokalise; moving them is a separate job.

  • The Zap keeps editing itself

    Translation Updated with Update a Translation on the same project is a loop: every update starts the Zap again and burns through tasks.

  • A big import goes quiet

    When an upload adds or changes a huge batch of keys, Zapier's flood protection can hold the batch back instead of running each item.

  • Keys vanish after an upload

    Upload File in Cleanup mode deletes every key not present in the file. Take a project snapshot before, as Lokalise itself advises.

  • A step fails on rights

    Key and task actions need the Manage keys or Manage tasks admin right. Without it the step fails; no task is billed, but nothing changes.

  • Polling never repeats an item

    On Poll Tasks and Poll Tasks' Languages' Progress, Zapier remembers what it has seen, so an item that comes back unchanged does not start the Zap twice.
Need help

Need help automating Lokalise with Zapier?

A person reads every message.

FAQ

Lokalise Zapier integration: questions people ask

01Is the Lokalise Zapier integration free?
Yes, for simple Zaps. Lokalise is not a premium app, so it runs on the free Zapier plan. That plan gives 100 tasks a month and two-step Zaps only: one trigger and one action. A closed task announced in a chat fits inside it. A filter, a second action or any of the twelve searches turns the Zap into a multi-step Zap, which needs a paid plan. Your Lokalise subscription is separate.
02How many Zapier tasks does a Lokalise Zap use?
One per action that succeeds, nothing for the trigger. A Zap that posts every closed task costs one task per task closed. Triggers that fire in bursts change the math: Key Added after a big import, or Task Language Closed on a task with many languages, start the Zap once per item. Waiting and polling cost nothing, and a failed action is not billed. Note that a Zapier task and a Lokalise task are two different things.
03Does Lokalise trigger Zaps in real time?
Mostly. Twenty-two of the 24 Lokalise triggers are instant: Lokalise tells Zapier the moment the event happens, and the Zap starts right away on every plan. The two exceptions are Poll Tasks and Poll Tasks' Languages' Progress, which Zapier checks at the interval of your plan, every 15 minutes on Free, down to 1 minute on Team and Enterprise. For a closed or created task, prefer the instant triggers. The type is set by Lokalise and cannot be changed in the editor.
04What do you need to connect Lokalise to Zapier?
A Lokalise account and a Zapier account. On the Apps page of Zapier, click + Add connection, search for Lokalise, click Add connection, then sign in to Lokalise in the tab that opens and grant access. Most steps then ask for a Project ID, some for a Team ID, so have both ready. Key and task actions also need the Manage keys or Manage tasks admin right on the connected user.
05Can Upload File delete keys in Lokalise?
Yes, if you switch on Cleanup mode. With that option, every key that is not in the uploaded file is deleted from the project, with its translations in every language. Lokalise itself suggests making a snapshot of the project before such an import. Leave Cleanup mode off unless the file is truly the full reference, and test the Zap on a copy project first. The Key Removed trigger will fire for each deleted key.
06What if the Lokalise operation you need is not in Zapier?
Then this integration does not offer it as such. Zapier lists 24 triggers, 9 actions and 12 searches for Lokalise, but nothing deletes a project or a task. Look in the searches before giving up: Delete a Key, for instance, sits there although it deletes. If the missing piece is central, another automation tool may reach Lokalise in a different way, so compare before investing in the workflow. Searches sit at the bottom of the action event list, under their own heading.
07Zapier, Make or n8n for Lokalise?
It depends on the criterion that matters most. On setup, Zapier is short: three steps to connect, and most Lokalise triggers are instant even on the free plan. On coverage, Zapier offers 45 visible operations, with key deletion hidden among searches, so check what Make and n8n expose for Lokalise before choosing. On cost, any Zapier Zap with a filter, a search or a second action needs a paid plan. Weigh those points rather than a ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations