Resources · Zapier integration

Localazy Zapier integrationAutomate Localazy with Zapier.

The Localazy Zapier integration gives you 3 triggers, 1 action and 1 search. All three triggers are instant, Localazy works from the free plan, and the page below covers what each step does, what it costs and where it trips.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Localazy Zapier integration actually does for you

The integration links your Localazy account to Zapier so that something happening in a localization project can set off work in your other tools, and the other way round. You build a Zap (one automation: an event that starts it, then the steps that follow) and Zapier runs it every time the event happens, without you copying anything by hand.

Comments that reach the people who can answer them. With Comment Added as the trigger (the event that starts the Zap), every comment left on a project can land in your team chat or task list. Questions about a string stop waiting inside a tool that half the team never opens.

A release bundle the moment a project goes out. Project Published starts the Zap, then Zip Files in Languages gathers the files and languages you picked into one zip. The next step (an action, meaning the part of the Zap that writes, sends or moves something) can store that zip or hand it to someone else.

Source text that arrives without a manual upload. Import to Localazy pushes source keys, and keys in other languages too, from whatever app your Zap started in. Pair it with Content Imported & Content Imported Empty on a second Zap and you also know when each import has finished.

What Zapier does not do here: there is one write action, and it imports. You cannot publish a project, post a comment or delete anything in Localazy from a Zap, and there is no trigger for a single new translation. If those gaps matter, the n8n vs Zapier comparison is worth a look before you decide.

Vocabulary

The Zapier words you will meet on this page

Eight terms, each in one line. Once you have them, the rest of the page reads without a dictionary.

Zap
The automation you build: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier simply waits for it to happen.
Action
What the Zap does after it starts: the step that writes, sends or moves something in another app for you.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps that follow can use what it found.
Connection
Your Localazy account linked to Zapier once, then reused by every step of every Zap that touches Localazy.
Cost

What a Localazy Zap costs you in tasks

Zapier bills completed actions, not events. The trigger never costs a task, and watching for new data is free however often it happens.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, 2-step Zaps
  • Premium appNo, works on the free plan

Each action that succeeds counts once, so a Zap with three actions eats three times what a one-action Zap does. An action that fails is not counted. Localazy is not a premium app, so it runs on the free plan: 100 tasks a month, unlimited Zaps, but only two steps per Zap. Add the zip search, a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below belongs to polling triggers and does not apply to this app, whose three triggers are all instant.

Connect

Connect your Localazy account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a Localazy account first, plus access to any project you do not own yourself but want the Zap to read or write.

  2. 02

    Pick Localazy in the dialog

    Type Localazy in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the Localazy side so you can sign in with the account that holds your projects.

  3. 03

    Grant access and come back

    Sign in to Localazy in that tab and allow Zapier to use the account. The connection then shows up in your Apps list and every Zap that uses Localazy picks it from there, no second login needed.

First Zap

Your first Zap: route project comments to your team

GoalEach comment added to a Localazy project lands in your team chat and becomes a task, so no question gets lost.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose Localazy as the app and Comment Added as the event. Select the connection you added earlier. Because the trigger is instant, the editor shows a lightning bolt on it.

  2. 02

    Test the trigger on a real comment

    Run the test. Zapier brings back the three most recent items from your account, so leave a comment on a project beforehand and pick it. You will map fields from that sample.

  3. 03

    Add the chat message

    Add an action in your team chat app, then map the comment text and the project name into the message. Keep it short: the point is that someone sees it and opens Localazy.

  4. 04

    Add the task, then test each step

    Add a second action in your task list and reuse the same fields. Two actions make this a multi-step Zap, so it needs a paid plan. Test each step once and read what came back.

  5. 05

    Publish

    Click Publish to switch the Zap on. Only comments posted from that moment on will run through it. If you are new to the editor, the Zapier training is a good next step.

Triggers

Localazy triggers in Zapier

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

1

Comment Added

Instant trigger

In Zapier“Triggers when a comment is added to a project.”

Hands each new comment on a Localazy project to your Zap, so a discussion about a string can reach the people who never log in to the platform.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
reviewers ask about context in Localazy, and the answer sits with someone who only lives in chat.
Watch out
comments written before you publish the Zap are never picked up, so old threads stay where they are.
2

Content Imported & Content Imported Empty

Instant trigger

In Zapier“Triggers when importing to a project is finished (from CLI or Gradle or File Upload).”

Starts your Zap once an import into a project has finished, whether the content came through the CLI, through Gradle or as an uploaded file.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want a heads-up that fresh source text is waiting before anyone starts translating it.
Watch out
if Import to Localazy runs inside the same project, its import can set this trigger off again and loop.
3

Project Published

Instant trigger

In Zapier“Triggers when a project is successfully published (applies to tags too).”

Fires when a project is published successfully, and publishing a tag counts as well. It is the natural starting point for anything that should follow a release.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
pair it with Zip Files in Languages to package the translated files as soon as they go live.
Watch out
a published tag starts the Zap too, so add a filter if only some publications matter.
Actions

The Localazy action

Localazy gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Import to Localazy

Action

In Zapier“Import source and other languages keys to Localazy.”

Sends source keys, and keys in other languages if you have them, into a Localazy project from the app that started your Zap.

When to use it
your source text is maintained outside Localazy and you are tired of uploading it by hand.
Watch out
by default Localazy keeps existing current versions and lets review decide. The Force source option overwrites source text even where a human changed it, so tick it only when Localazy is not your source of truth.
Searches

The Localazy search

1 search step looks for data that already exists in Localazy, so a later step can use it.

A search sits at the bottom of the action list, under SEARCH. It makes the Zap multi-step, and three settings decide what happens when results are odd.

1

Zip Files in Languages

Search

In Zapier“Allows you to select from the project's files and languages and bundle them into a zip file.”

Lets you choose files and languages from a project and returns them bundled as a single zip that the next steps can store or send.

When to use it
right after Project Published, to hand the fresh translations to whoever ships them.
Watch out
this is a search step, so any Zap that uses it is multi-step and needs a paid plan.

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 there and skips the steps that relied on it. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this turns a search into find-or-create. Localazy offers no such variant, so you will not see this box on its search.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When a Localazy Zap breaks

Zapier links no help article to Localazy and documents no app-specific limit. What goes wrong comes from how Zapier itself behaves.

These are the cases worth knowing before you publish. When a Zap stops for a reason that is not listed here, the Zapier troubleshooting page is where to start.

  • The past is never replayed

    A Zap reacts only to what happens after you switch it on. Projects published or comments left before that are ignored; moving them is a separate job.

  • An import that triggers itself

    Import to Localazy on a Zap that starts from Content Imported in the same project sets itself off again and again, and burns tasks fast.

  • A bulk import held back

    When a trigger suddenly sends a huge batch, after a migration for instance, Zapier's flood protection can hold the Zap back instead of running it.

  • A zip search that stops the Zap

    If Zip Files in Languages comes back empty and the default setting is kept, the Zap stops there and the save step after it never runs.
Need help

Need help automating Localazy with Zapier?

A person reads every message.

FAQ

Localazy Zapier integration: common questions

01Is the Localazy Zapier integration free?
Yes, as long as each Zap stays at two steps. Localazy is not a premium app, so it works on the free plan, which gives you 100 tasks a month and as many Zaps as you like. The limit is the shape of the Zap: one trigger and one action. A Comment Added trigger posting to a chat fits. Add the zip search, a filter or a second action and the Zap becomes multi-step, which only paid plans run. A two-step Zap is often enough to start, and you can extend it once the habit is there.
02How many tasks does a Localazy Zap use?
One task per action that completes, nothing for the trigger. A Zap that turns each new comment into a chat message costs one task per comment. If the same Zap also creates a task in your task list, it costs two per comment, because every successful action counts on its own. An action that fails is not billed. Watching Localazy for new events never costs anything either, so a quiet project costs you nothing at all while the Zap waits.
03Do Localazy triggers fire in real time?
Yes. All three Localazy triggers are instant: the app tells Zapier the moment a comment is added, an import finishes or a project is published, and the Zap starts right away whatever your plan. The polling intervals you see in Zapier's plan grid apply to triggers that Zapier checks on a timer, and Localazy has none of those. In the editor, you will recognise an instant trigger by the lightning bolt on its card.
04What does it take to connect Localazy to Zapier?
A Localazy account, plus access to any project you want the Zap to read or write that you do not own yourself. The connection itself happens from the Apps page of your Zapier account: add a connection, pick Localazy, sign in in the tab that opens and allow access. Once that is done, every Zap that uses Localazy reuses the same connection, so you link the account once. If a project belongs to someone else, ask for access before you build, or the Zap will fail on it.
05Can Import to Localazy overwrite translations a person edited?
Only if you tell it to. By default Localazy does not overwrite the current version of a translation and leaves the decision to the review process. The Force current option sets every imported translation as current, and Force source overwrites source text even where a human made changes. Use those two only when the truth lives outside Localazy and must always win. Import as new does the opposite and routes everything through review.
06What if the Localazy operation you need is not in Zapier?
Then it is not something a Zap can do today. Zapier exposes three triggers, one action and one search for Localazy, and nothing else appears in the editor. Publishing, commenting or deleting from a Zap is not on the list. The usual answer is to rethink the flow around what exists, for example starting from Project Published instead of trying to publish from a Zap, or to look at another automation tool that can call the app directly.
07Zapier, Make or n8n for Localazy?
It depends on what matters to you, not on a ranking. Zapier's strength here is setup: three instant triggers and a guided connection. Its limit here is the catalog, with a single write action, and the fact that the zip scenario needs a paid plan. Make and n8n are separate tools with their own connectors, so check what each one offers for Localazy before you move. Weigh how many steps your flow needs, which plan it forces on you and who will maintain it.
Same platform

Other docs you might need on this stack.

Browse all integrations