Lokalise is a collaborative translation platform.
Lokalise currently provides 3 triggers that can start a workflow and 12 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
Key Added
Trigger when a new key is added to your Lokalise project
Key Updated
Trigger when a key is updated in your Lokalise project
Translation Updated
Trigger when a translation is updated in your Lokalise project
Create Comment
Add comments to a key in your Lokalise project
Create Key
Create one or more keys in your Lokalise project
Create Project
Create a new project in your Lokalise team
Create Task
Create a new task in your Lokalise project
Delete Key
Delete a key from your Lokalise project (software and marketing projects only)
Retrieve a comment
Retrieve a specific comment on a key in your Lokalise project
Retrieve a key
Retrieve detailed information about a specific key in your Lokalise project
Retrieve a project
Retrieve detailed information about a Lokalise project
Retrieve Translation
Retrieve a specific translation from your Lokalise project
Update Key
Update properties of a key in your Lokalise project
Update Translation
Update a translation in your Lokalise project
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Lokalise event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Key Added
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Lokalise action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Comment
Combine Lokalise with another integration and Coherence records to connect product and engineering activity to the customers and work it affects.
Starts with
Key Added
Finishes with
Create Comment, then preserve the outcome in Coherence
The exact authentication fields depend on Lokalise. The workflow structure stays straightforward:
Authorize the Lokalise account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Lokalise or provide a complementary trigger or action.
Lokalise currently provides 3 triggers that can start a workflow and 12 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
Lokalise currently lists 3 triggers and 12 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Lokalise triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
