Lokalise connector
Automate Localization Workflows with Lokalise Integrations
Connect Lokalise to your development, project management, and content tools to ship translations faster and cut out manual handoffs.
What can you do with the Lokalise connector?
Lokalise is a translation management platform for engineering and product teams who need to handle localization at scale. The catch: keeping translation projects in sync with development sprints, content updates, and release cycles eats up a lot of manual effort. With tray.ai, you can automate the localization pipeline from end to end — triggering translation tasks when new copy lands in your codebase, notifying stakeholders when strings are ready for release, and everything in between. Whether you're managing mobile app localization, SaaS product strings, or marketing content, tray.ai connects Lokalise to the rest of your stack so nothing gets missed.
Automate & integrate Lokalise
Automating Lokalise business process or integrating Lokalise data is made easy with tray.ai
Use case
Automated Translation Task Creation from Development Workflows
When developers merge new feature branches or update resource files in GitHub or GitLab, tray.ai can automatically create Lokalise tasks, assign translators, and set deadlines based on your release calendar. This cuts out the back-and-forth between engineering and localization teams and makes sure no new strings go untranslated before launch.
Use case
Bi-Directional Sync Between Lokalise and Project Management Tools
Keep Jira, Asana, or Monday.com tickets in sync with Lokalise translation task status. When a translation task moves to 'In Review' or 'Completed' in Lokalise, the corresponding ticket updates automatically and stakeholders get a notification. Product managers get real-time visibility into localization progress without ever logging into Lokalise.
Use case
Localization-Triggered Content Publishing Pipelines
For marketing and content teams, connect Lokalise to your CMS — Contentful, Sanity, WordPress — so approved translations are automatically pushed to the right locale in production. No more manual export and re-import of translation files. Localized content goes live the moment it passes review.
Use case
Translation Quality and Review Notification Workflows
Automatically notify linguists, reviewers, or vendor contacts in Slack or Microsoft Teams when strings are ready for review, when comments are added to a translation key, or when a task is rejected and needs revision. Keeping these alerts in your communication tools means review cycles keep moving without anyone having to check Lokalise constantly.
Use case
Automated Screenshot and Context Capture for Translators
Connect Lokalise to your CI/CD pipeline or Figma to automatically attach screenshots and in-context previews to translation keys when new UI components are built or updated. Translators get accurate visual context up front, which means fewer questions, fewer revisions, and faster delivery.
Use case
Multi-Vendor Translation Order Automation
When untranslated keys accumulate past a set threshold, tray.ai can automatically place orders with your preferred translation vendor or machine translation service, route specific content types to the right vendor, and update Lokalise with the returned translations when they're done. The result is a fully automated translation procurement loop.
Use case
Localization Progress Reporting and Analytics
Pull Lokalise project statistics — translation completion percentages, word counts, task statuses — and push them into Looker, Google Sheets, or a BI dashboard on a schedule. Leadership gets a current view of localization health across all projects and languages without anyone building manual reports from Lokalise exports.
Build Lokalise Agents
Give agents secure and governed access to Lokalise through Agent Builder and Agent Gateway for MCP.
Data Source
Fetch Translation Keys
Retrieve all translation keys and their strings from a Lokalise project so an agent has full context on existing localizable content. Useful for auditing coverage or finding missing translations.
Data Source
Look Up Project Details
Pull metadata about a Lokalise project including supported languages, contributors, and settings. Helps an agent understand the scope of a localization effort before taking action.
Data Source
Retrieve Translation Strings by Language
Fetch translated values for a specific language within a project to verify completeness or pull content for review. Agents can compare translations across locales and flag inconsistencies.
Data Source
List Contributors and Permissions
Query team members and their roles on a Lokalise project to determine who owns specific languages or tasks. Useful for routing review requests to the right people.
Data Source
Monitor Translation Task Status
Check the status of active translation tasks and assignments within Lokalise to track progress against deadlines. An agent can surface blockers or send alerts when tasks fall behind.
Agent Tool
Create or Update Translation Keys
Add new keys or update existing translation strings in a Lokalise project programmatically. An agent can push newly written content or product copy directly into the localization pipeline without manual entry.
Agent Tool
Trigger File Export
Kick off an export of translation files from Lokalise in formats like JSON, XLIFF, or PO for use in downstream deployments. An agent can automate release workflows by pulling the latest translations on demand.
Agent Tool
Import Translation Files
Upload translation files from external sources directly into a Lokalise project. An agent can automate ingestion of translated content from vendors or other tools, keeping projects in sync.
Agent Tool
Create a New Project
Spin up a new Lokalise project with specified languages and settings when a new product or feature launches. Automates project setup as part of a broader product delivery workflow.
Agent Tool
Add a New Language to a Project
Programmatically add a new target language to an existing Lokalise project when expanding to new markets. An agent can trigger this as part of an internationalization workflow driven by business or product changes.
Agent Tool
Create Translation Tasks
Automatically create and assign translation tasks within Lokalise for specific keys or languages when new content is ready for localization. Keeps translator workloads organized so nothing gets missed.
Agent Tool
Delete Unused Keys
Identify and remove deprecated or unused translation keys from a Lokalise project to keep it clean and maintainable. An agent can cross-reference code exports with existing keys and safely prune stale entries.
Get started with our Lokalise connector today
If you would like to get started with the tray.ai Lokalise connector today then speak to one of our team.
Lokalise Challenges
What challenges are there when working with Lokalise and how will using Tray.ai help?
Challenge
Keeping Translation Status in Sync Across Multiple Tools
Localization teams often manage tasks in Lokalise while engineering tracks work in Jira and stakeholders monitor progress in separate project management tools. Manually updating status across all three systems is error-prone, produces stale data, and burns hours of coordination time each sprint.
How Tray.ai Can Help:
tray.ai listens to Lokalise webhook events for task status changes and automatically propagates updates to Jira, Asana, or any PM tool in real time. Custom field mappings make sure the right data reaches the right fields, and conditional logic can trigger downstream actions — like moving a release checklist item forward when all languages hit 100%.
Challenge
Bridging the Gap Between Code Deploys and Translation Requests
Without automation, developers have to manually notify the localization team after merging new strings, and then someone has to log into Lokalise to create tasks and assign translators. This handoff introduces delays — often measured in days — that push localized releases behind the English release.
How Tray.ai Can Help:
tray.ai connects directly to GitHub, GitLab, or Bitbucket webhooks so the moment a merge happens and locale files change, a Lokalise task is created automatically with the correct keys, assignees, and deadline. The handoff is gone entirely and localization starts within seconds of the code merge.
Challenge
Managing Complex Multi-Locale, Multi-Vendor Translation Pipelines
Large products support dozens of locales sourced from multiple translation vendors, machine translation engines, and internal linguist teams. Routing the right content to the right vendor, tracking order status, and consolidating translated strings back into Lokalise manually becomes a full-time coordination job.
How Tray.ai Can Help:
tray.ai's branching and routing logic lets you build rules that direct content by locale, content type, word count, or project to the right vendor API or MT service. Completed translations are automatically imported back into Lokalise and spend data is logged to your financial system — no human intervention required.
Challenge
Lack of Visibility for Non-Technical Stakeholders
Product managers, marketing leads, and executives need to know whether localization will hold up a release, but they rarely have Lokalise access or know how to read raw translation statistics. This creates last-minute surprises when a release slips because of incomplete translations.
How Tray.ai Can Help:
tray.ai pulls Lokalise project statistics on a schedule and pushes them into tools stakeholders already use — Google Sheets dashboards, Tableau reports, or weekly email digests. Progress data is presented in plain business terms (e.g., '85% complete, 3 languages at risk') rather than raw API responses, so teams can make informed release decisions without any Lokalise access.
Challenge
Export/Import File Management Between Lokalise and CMS or Code Repositories
Teams frequently export translation files from Lokalise, manually upload them to a CMS like Contentful or Strapi, or commit them back to a repository. This repetitive process is a reliable source of errors — wrong file versions, missed locales, overwrites of previously approved content.
How Tray.ai Can Help:
tray.ai automates the full export-and-deliver cycle. When translations are approved in Lokalise, tray.ai fetches the relevant file bundle via the Lokalise Files API and pushes the content directly to the target CMS entry fields or commits the files to the correct repository path via the GitHub API. No manual file handling.
Talk to our team to learn how to connect Lokalise with your stack
Find the tray.ai connector with one of the 700+ other connectors in the tray.ai connector library to integrate your stack.
Integrate Lokalise With Your Stack
The Tray.ai connector library can help you integrate Lokalise with the rest of your stack. See what Tray.ai can help you integrate Lokalise with.
Start using our pre-built Lokalise templates today
Start from scratch or use one of our pre-built Lokalise templates to quickly solve your most common use cases.
Template
GitHub PR Merged → Create Lokalise Task with Deadline
When a pull request is merged into a specified branch in GitHub and modified locale files are detected, automatically create a Lokalise translation task, assign it to the appropriate translator team, and set a deadline based on the next scheduled release date stored in a configuration sheet.
Steps:
- Listen for pull_request closed and merged webhook event from GitHub
- Filter for changes to locale or i18n file paths using a path matching condition
- Look up the next release date from a Google Sheet release calendar
- Call Lokalise API to create a new task with keys from the diff, assign translators, and set the deadline
- Post a confirmation message to the #localization Slack channel with task link and deadline
Connectors Used: GitHub, Lokalise, Google Sheets, Slack
Template
Lokalise Task Completed → Update Jira Ticket and Notify Team
When a translation task in Lokalise reaches 'Completed' status, automatically transition the linked Jira ticket to 'Ready for QA', add a comment with the Lokalise task summary, and send a Slack notification to the product manager and QA lead.
Steps:
- Receive Lokalise webhook for task status change event
- Filter for tasks where new status equals 'completed'
- Look up the linked Jira issue key stored in the Lokalise task description or a mapping sheet
- Transition Jira issue to 'Ready for QA' using the Jira Transitions API
- Post Slack message to product manager and QA channels with translation summary and Jira link
Connectors Used: Lokalise, Jira, Slack
Template
Lokalise Translation Approved → Publish to Contentful Locale
When a translation in Lokalise is marked as approved for a given locale, fetch the translated strings and automatically update the corresponding Contentful entry fields for that locale, then trigger a Contentful publish action so localized content goes live without manual intervention.
Steps:
- Receive Lokalise webhook for key translation approved event, capturing locale and key data
- Fetch the full translated string values from Lokalise using the Keys API
- Map Lokalise key names to Contentful entry IDs and field names using a lookup table
- Update the Contentful entry fields for the target locale via the Contentful Management API
- Publish the updated Contentful entry and send a Slack summary of published locale updates
Connectors Used: Lokalise, Contentful, Slack
Template
Weekly Lokalise Progress Report to Google Sheets and Email
On a weekly schedule, pull translation completion statistics for all active Lokalise projects, calculate completion percentages by language, write the results to a Google Sheet dashboard, and email a formatted summary report to the localization program manager.
Steps:
- Trigger on a weekly schedule every Monday morning
- Fetch all active projects from Lokalise and iterate through each project
- For each project, retrieve language statistics including word counts and completion percentages
- Write aggregated statistics rows to the designated Google Sheet dashboard tab
- Compile a summary email with project highlights and send via Gmail to the localization team lead
Connectors Used: Lokalise, Google Sheets, Gmail
Template
New Figma Component → Attach Screenshot Context to Lokalise Keys
When a new UI component is published in Figma, extract frame images for components containing string references, upload the screenshots to the matching Lokalise translation keys, and notify translators that new visual context is available for their pending tasks.
Steps:
- Receive Figma webhook for file published event
- Use the Figma API to identify frames tagged with localization key annotations
- Export frame images as PNG from Figma's image render API
- Upload screenshots to the corresponding Lokalise keys using the Screenshots API
- Post a Slack notification to the #translators channel listing keys updated with new context
Connectors Used: Figma, Lokalise, Slack
Template
Untranslated Key Count Threshold → Auto-Order Machine Translation
Check the number of untranslated keys in Lokalise on a daily schedule. If any project language falls below a translation completion threshold, automatically submit a machine translation order for the outstanding keys and log the order details to a Google Sheet for cost tracking.
Steps:
- Run on a daily schedule to check Lokalise language statistics for all active projects
- Calculate the percentage of untranslated keys per language using a formula step
- Filter for languages where completion is below the configured threshold (e.g., 80%)
- Submit a machine translation request in Lokalise for the identified language gaps
- Log order details including word count, language, and timestamp to Google Sheets and alert the team in Slack
Connectors Used: Lokalise, Google Sheets, Slack