Connectors / Integration
Automate Localization Workflows Between Lokalise and GitHub
Keep your translation files and code repositories in sync — no manual exports, no pull request bottlenecks, no back-and-forth.
Lokalise + GitHub integration
Lokalise and GitHub each do one thing well. Developers store and version their codebase — including locale files — in GitHub. Translators and localization managers work inside Lokalise to manage translations across languages. The problem is the gap between them: someone has to manually export files, commit them, and keep both systems current. With tray.ai, that gap closes. You can automate the entire localization pipeline so your engineering and translation teams always work from the same source of truth.
Localization is continuous work, not a one-time task. Every time a developer adds a string, updates copy, or ships a feature, translation files in GitHub need to change — and those changes need to reach Lokalise so translators can act on them right away. Without automation, the cycle is tedious: export files, paste into Lokalise, wait for translations, re-export, open pull requests. It slows releases and invites human error. Connecting Lokalise and GitHub through tray.ai removes that friction. Teams can trigger translation workflows directly from GitHub events, push completed translations back to repositories automatically, and make sure no string is ever missed or stale.
Automate & integrate Lokalise + GitHub
Automating Lokalise and GitHub business processes or integrating data is made easy with Tray.ai.
Use case
Push New Source Strings from GitHub to Lokalise Automatically
When a developer merges a pull request to a main branch that contains changes to locale files, tray.ai detects the change in GitHub and uploads the updated source strings to Lokalise. Translators are notified immediately so they can start working without waiting for a manual handoff. The translation queue stays populated continuously, with no developer effort required.
- Eliminates manual file uploads after every code merge
- Reduces time-to-translation by triggering translator tasks instantly
- Ensures Lokalise always reflects the latest source content from your repository
Use case
Pull Completed Translations Back to GitHub as a Pull Request
Once translations are marked complete in Lokalise for all target languages, tray.ai exports the translation files and opens a pull request in the appropriate GitHub repository and branch. Engineers can review and merge the PR on their own schedule, keeping localized content flowing into the codebase without bottlenecks. The full localization cycle closes programmatically.
- Removes the manual step of exporting and committing translated files
- Keeps translation delivery integrated with existing code review workflows
- Reduces release delays caused by waiting for localization to be committed manually
Use case
Trigger Localization Tasks When GitHub Issues Are Labeled
When a GitHub issue is labeled with a localization-related tag — such as 'needs-translation' or 'l10n' — tray.ai can automatically create a corresponding task or comment in Lokalise, linking the two systems. Product managers can flag localization needs directly in their issue tracker without switching tools. Localization managers see the request in Lokalise with full context pulled from the GitHub issue.
- Bridges product and localization teams across their native tools
- Reduces context-switching for both developers and localization managers
- Ensures no localization request gets lost in GitHub issue queues
Use case
Sync Lokalise Translation Status to GitHub Commit Statuses
tray.ai can write translation completion status from Lokalise back to GitHub as commit statuses or check runs, giving developers real-time visibility into whether translations are ready to ship. Localization becomes a first-class check in your CI/CD pipeline, blocking or allowing releases based on actual translation progress. Teams can gate releases on localization completeness without manual status checks.
- Integrates translation readiness into CI/CD pipelines as a native check
- Prevents shipping untranslated strings to production
- Gives developers live localization status without leaving GitHub
Use case
Automatically Create Lokalise Keys from New GitHub Commits
When a developer pushes a commit that introduces new translation keys parsed from locale files, tray.ai can automatically create those keys in Lokalise with the correct file format, platform target, and initial source text. Developers don't have to manually set up keys inside Lokalise, and every new string is immediately ready for translation. Tags and metadata can be applied based on the GitHub branch or repository context.
- Reduces developer time spent manually managing keys in Lokalise
- Ensures 100% key coverage between your codebase and Lokalise project
- Applies consistent tagging and metadata based on repository structure
Use case
Notify GitHub Teams When Translations Hit Quality Milestones
When Lokalise reports that a project has reached a defined translation completeness threshold — say, 100% translated and reviewed for all target locales — tray.ai can post a comment on the relevant GitHub pull request or issue to notify the engineering team. Release planning conversations stay grounded in real localization data without anyone logging into Lokalise to check progress. Teams can coordinate shipping decisions without a status update meeting.
- Keeps engineering teams informed of localization progress inside GitHub
- Reduces status update overhead between engineering and localization teams
- Enables release decisions based on live translation metrics
Challenges Tray.ai solves
Common obstacles when integrating Lokalise and GitHub — and how Tray.ai handles them.
Challenge
Keeping Locale Files in Sync Across Two Different Platforms
Locale files live in GitHub but translations happen in Lokalise, so the two systems fall out of sync whenever changes in one aren't reflected in the other. Teams relying on manual exports and commits regularly find translators working from outdated source strings, or engineers shipping code with stale translations.
How Tray.ai helps
tray.ai listens for real-time events from both GitHub and Lokalise via webhooks, then pushes changes in either direction the moment they occur. Both platforms stay current without manual intervention.
Challenge
Managing Multiple Repositories and Lokalise Projects at Scale
Large engineering organizations often have multiple GitHub repositories — each representing a product, platform, or microservice — with corresponding Lokalise projects. Manually routing locale files between the right repos and the right projects is error-prone and time-consuming.
How Tray.ai helps
tray.ai's workflow logic lets you route data dynamically based on repository name, branch, file path, or custom metadata. A single integration can handle multiple repo-to-project mappings with conditional logic, so files always land in the correct Lokalise project regardless of where they originate.
Challenge
Handling Different File Formats Between Repositories
Different repositories may use different locale file formats — one service might use JSON, another YAML, and a mobile app XLIFF or Android XML. Syncing these formats reliably between GitHub and Lokalise requires format-specific parsing and export configuration that's hard to maintain manually.
How Tray.ai helps
tray.ai supports flexible data transformation steps between GitHub and Lokalise API calls, letting you specify the correct file format for each project or repository in the workflow configuration. Format-specific parameters are passed cleanly to the Lokalise Files API so translations are always imported and exported in the expected format.
Templates
Pre-built workflows for Lokalise and GitHub you can deploy in minutes.
Sync GitHub Locale File Changes to Lokalise on Merge
GitHub 
Lokalise Automatically detects changes to locale files in a GitHub repository when a pull request is merged, parses the updated source strings, and uploads them to the corresponding Lokalise project. Supports common formats including JSON, YAML, PO, and XLIFF.
Push Completed Lokalise Translations to GitHub as a Pull Request
Lokalise GitHub When all target language translations are marked complete in a Lokalise project, this template exports the translation files and automatically opens a pull request against the configured GitHub repository and branch, ready for engineering review.
Create Lokalise Keys from New Strings Detected in GitHub Commits
GitHub Lokalise Monitors GitHub commits for additions or changes to locale source files and automatically creates corresponding keys in Lokalise with source text, platform tags, and file format metadata derived from the repository structure.
Post Lokalise Translation Progress to GitHub Pull Request Comments
Lokalise GitHub Polls or receives webhook data from Lokalise on translation progress and writes the current completion percentage for each target language as a comment on the corresponding GitHub pull request, keeping engineers informed without leaving GitHub.
Archive Lokalise Keys When a GitHub Branch Is Deleted
GitHub Lokalise Listens for branch deletion events in GitHub and automatically archives or applies a deprecation tag to the associated Lokalise keys created during that branch's lifecycle, preventing orphaned keys from cluttering the Lokalise workspace.
Create GitHub Issues for Untranslated Strings Detected in Lokalise
Lokalise GitHub Periodically queries Lokalise for keys that are missing translations in one or more target languages and automatically creates GitHub issues assigned to the appropriate team, so untranslated strings are tracked and resolved before release.
How Tray.ai makes this work
Lokalise + GitHub runs on the full Tray.ai platform
Intelligent iPaaS
Integrate and automate across 700+ connectors with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Lokalise and GitHub — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway
Expose Lokalise + GitHub actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Ship your Lokalise + GitHub integration.
We'll walk through the exact integration you're imagining in a tailored demo.