Locale Zapier integrationAutomate Locale with Zapier.
The Locale Zapier integration gives you 1 trigger and 1 action. The trigger is instant, Locale runs on the free plan, and this page walks through what both steps do, what they cost you in tasks and the spots where a Zap tends to trip.
Verified Trustpilot reviews · AI, automation & growth agency
What the Locale Zapier integration does for you
The integration links your Locale account to Zapier, so a finished translation can kick off work in your other tools, and content from those tools can be sent to Locale for translation. You build a Zap (one automation: an event that starts it, then the steps that follow) and Zapier runs it each time that event happens.
Finished translations that land where they are used. Translations Ready is the trigger (the event that starts the Zap): it fires once a new translation is done. The next step can save the result, post it or pass it on, so nobody has to go and fetch it.
Content that leaves for translation without a manual upload. Translate Content is the action (the step that writes, sends or moves something for you). It sends content to Locale for translation from whatever app started the Zap, for instance a new row in a spreadsheet.
A team that hears about it. Chain the trigger to a message in your team chat and the people waiting on a translation know it is there the moment it is finished.
What Zapier does not do here: the connector stops at those two steps. There is no search, no way to update or delete a translation from a Zap, and no trigger for anything other than a finished translation. If that is too narrow, the n8n vs Zapier comparison is worth a look before you decide.
The Zapier words used on this page
Seven terms, one line each. With these, nothing below needs a second read.
- 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 on, Zapier simply waits for that event to come in.
- 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 action your Zap completes successfully. The allowance of your plan counts those.
- Polling vs instant
- Zapier checks a polling trigger on a timer. An instant trigger is reported by the app itself as soon as 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.
- Connection
- Your Locale account linked to Zapier once, then reused by every step of every Zap that works with Locale.
What a Locale Zap costs you in tasks
Zapier bills completed actions, not events. The trigger costs nothing, and waiting for new translations is free however many arrive.
- 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 uses three times what a one-action Zap uses. An action that fails is not counted. Locale is not a premium app, so it works on the free plan: 100 tasks a month, as many Zaps as you like, but two steps per Zap. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below is for polling triggers; it does not apply to Translations Ready, which is instant.
Connect your Locale account to Zapier
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. Before that, you need a Locale account, plus access to anything you do not own but want the Zap to read or change.
- 02
Find Locale in the dialog
Type Locale in the search box of the dialog, select it and click Add connection. A new tab opens on the Locale side so you can sign in with the account that holds your content.
- 03
Allow access
Sign in to Locale in that tab and grant Zapier access to the account. The connection then appears in your Apps list, and every Zap that uses Locale picks it up from there.
Your first Zap: tell your team a translation is ready
GoalEvery finished translation in Locale that passes your filter posts a message in your team chat, so nobody keeps checking by hand.
- 01
Create the Zap and set the trigger
Start a new Zap, choose Locale as the app and Translations Ready as the event, then pick your connection. It is an instant trigger, so the editor shows a lightning bolt on it.
- 02
Test it on a real translation
Run the test. Zapier brings back the three most recent items from your account, so finish a translation beforehand and pick it. You will map fields from that real sample.
- 03
Add the filter
Click the plus icon, choose Filter and fill the three boxes: the field to look at, the rule and the value. A text rule only works on text.
- 04
Add the chat message and test
Add the action of your team chat and map the translation data into the message. With a filter the Zap is multi-step, so it needs a paid plan. Test each step once.
- 05
Publish
Click Publish to switch it on. Only translations finished from then on go through. New to the editor? The Zapier training is a good next step.
The Locale trigger in Zapier
1 event starts a Zap when something happens in Locale, and one of them is instant: the app calls Zapier straight away, whatever your plan.
Translations Ready
Instant triggerIn Zapier“Triggers when a new translation is finished.”
Starts your Zap as soon as Locale has finished a new translation, and hands the result to the steps that follow so they can store it, share it or announce it.
The Locale action
Locale gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Translate Content
ActionIn Zapier“Sends content to our servers for translation”
Hands content from the app that started your Zap over to Locale, which takes it in for translation. It is the action Zapier puts forward for this app.
When a Locale Zap breaks
Zapier links no help article to Locale and documents no limit of its own for the app. What goes wrong comes from how Zapier itself works.
These are the cases to know before you publish. For an error that is not listed here, the Zapier troubleshooting page is the place to start.
Nothing from before is replayed
A Zap only reacts to what happens after you switch it on. Translations already finished are ignored, and moving them is a separate job.A translation loop
A Zap that starts on Translations Ready and runs Translate Content can feed itself: each result sends new content, which finishes and fires again, and tasks burn fast.A flood held back
When the trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the Zap back instead of running it.A filter that never passes
Filter rules are typed: a number rule applied to text never matches, so the message after the filter never goes out.
Need help automating Locale with Zapier?
A person reads every message.
