Project branch added
Start a workflow when a project branch is added in Lokalise. Use this to coordinate work across your team and other apps.
Translation
Automate Lokalise projects, keys and translations. Import localization files and connect native project events to other apps with FastHook.
Start a workflow
Choose what starts your automation.
Start a workflow when a project branch is added in Lokalise. Use this to coordinate work across your team and other apps.
Start a workflow when a project branch is deleted in Lokalise. Use this to flag related records in another system for review.
Start a workflow when Lokalise reports a project branch merged event. Use this to coordinate work across your team and other apps.
Start a workflow when a project contributor is added in Lokalise. Use this to coordinate work across your team and other apps.
Start a workflow when a project contributor is deleted in Lokalise. Use this to flag related records in another system for review.
Start a workflow when Lokalise reports a project copied event. Use this to coordinate work across your team and other apps.
Start a workflow when a project is deleted in Lokalise. Use this to flag related records in another system for review.
Start a workflow when Lokalise reports a project exported event. Use this to coordinate work across your team and other apps.
Start a workflow when Lokalise reports a project imported event. Use this to coordinate work across your team and other apps.
Start a workflow when a project key is added in Lokalise. Use this to coordinate work across your team and other apps.
Start a workflow when a project key comment is added in Lokalise. Use this to route messages or notify the right people in another app.
Start a workflow when Lokalise reports a project key modified event. Use this to coordinate work across your team and other apps.
Start a workflow when a project keys is added in Lokalise. Use this to coordinate work across your team and other apps.
Start a workflow when a project keys is deleted in Lokalise. Use this to flag related records in another system for review.
Start a workflow when Lokalise reports a project keys modified event. Use this to coordinate work across your team and other apps.
Start a workflow when a project language is removed in Lokalise. Use this to flag related records in another system for review.
Start a workflow when Lokalise reports a project language settings changed event. Use this to coordinate work across your team and other apps.
Start a workflow when a project languages is added in Lokalise. Use this to coordinate work across your team and other apps.
Start a workflow when Lokalise reports a project snapshot event. Use this to coordinate work across your team and other apps.
Start a workflow when Lokalise reports a project task closed event. Use this to coordinate work across your team and other apps.
Then take action
Choose what your workflow does in Lokalise.
Creates one or more keys in the project. Requires Manage keys admin right. We recommend sending payload in chunks of up to 500 keys per request.
Updates a translation. Alternatively, use the Multi-key update endpoint to update translations. Requires write_translations OAuth access scope.
Add members to group in Lokalise. Requires Admin right in the team. Requires write_team_groups OAuth access scope.
Add projects to group in Lokalise. Requires Admin right in the team. Requires write_team_groups OAuth access scope.
Creates a branch in the project. Before using this endpoint, please enable Branching in your project by following this guide. Requires admin rights.
Adds new payment card to user cards. Requires write_payment_cards OAuth access scope.
Creates a group in the team. Requires Admin right in the team. If is_admin flag is set to true, the group would automatically get access to all project languages, overriding supplied languages object.
Creates a new project in the specified team. Requires Admin role in the team. Requires write_projects OAuth access scope.
Creates a new project in the specified team. Requires Admin role in the team. Requires write_projects OAuth access scope.
Create a JWT token for working with other services (primarily OTA/mobile SDKs). Project Type Compatibility: - ✅ Software projects (localization_files) - Used with mobile SDKs and OTA updates - ❌ Documents projects (paged_documents) - Not supported - ❌ Marketing projects (content_integration, marketing, marketing_integrations) - Not supported.
Creates snapshot of the project. Requires Manage settings admin right. Requires write_snapshots OAuth access scope.
Creates a custom translation status in the project. Requires write_custom_translation_statuses OAuth access scope.
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. Use this to turn an incoming request into work your team can track.
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. Use this to turn an incoming request into work your team can track.
Creates a webhook in the project. Requires Manage settings admin right. See our documentation for available events and payload examples.
Creates a translation order. You must have admin privileges in the project you are placing an order in. Requires write_team_orders OAuth access scope.
Adds a set of comments to the key. Requires write_comments OAuth access scope.
Adds a set of comments to the key. Requires write_comments OAuth access scope.
Creates one or more contributors in the project. Requires Manage contributors admin right. If is_admin flag is set to true, the user would automatically get access to all project languages, overriding supplied languages object.
Creates one or more glossary terms in the project. Requires Manage glossary admin right. Requires write_glossary OAuth access scope.
Start with a published template and adapt it to your work.
Send a Telegram notification when someone updates a translation in the selected Lokalise project.
Create a branch onboarding task so a coordinator can check language coverage.
Track each proofreading event by project, key and locale, without forwarding translation text.
Let translators know when a new key needs coverage.
Notify the release team when a localization task closes.
Connection. In Lokalise, open Profile and API tokens. Create a READ WRITE token for workflows that change data or manage webhooks. Connect the token in FastHook; it is stored encrypted. Your account must belong to at least one accessible project. Select the project in each Trigger or Action. Native triggers also require Manage settings permission.
Available workflows. Create, find and update localization projects, keys, translations, languages and tasks. Work with project branches and retrieve paginated API data. Import a localization File from an earlier workflow step, with explicit filename, language and import options. Start workflows from native project, key, translation, task and other documented Lokalise events. Export localization bundles and inspect queued import processes.
This integration uses an API token. OAuth connection support is pending approval of the FastHook application.
Permissions, project settings and Lokalise plan entitlements determine which operations are available. A catalog entry does not mean every endpoint has been live tested.
List Actions return a page. Use the documented page or cursor inputs to retrieve additional results.
Upload File accepts one FastHook File from 1 byte to 10 MiB. An accepted upload returns a queued process; check its status to confirm that import finished.
Export translations as File returns a ZIP File up to 2 MiB from the documented Lokalise export bucket. Download files returns the provider bundle URL when you need a larger export. Other storage locations require support.
Active workflows share a managed webhook for the selected project. FastHook verifies its generated secret and checks project and webhook identity. Byte-identical redeliveries share a deduplication identity; manual replays may repeat downstream effects.
Bulk update and single-item events have different payloads. Map fields from the selected event, and avoid sending translation contents to destinations that should not receive them.
Vantage and OTA APIs use separate protocols and are not included in this API-token integration.
Disconnect removes the saved FastHook connection. Revoke the API token in Lokalise to invalidate its remote access.