11:20Integrations

Loqalit integrations

Loqalit’s integrations are Crowdin, Phrase, Slack, GitHub Actions, signed webhooks, a REST API and a Chrome extension. Accepted fixes are posted to Crowdin or Phrase with a screenshot, and a GitHub Actions step can gate your releases.

Loqalit is an agentic localization QA platform that checks your live and staging websites, web apps and mobile apps in every language you ship. It catches translation, context and layout bugs in the rendered product, scores them with MQM, and routes fixes into Crowdin or Phrase.

Integrations

Works where your team already works

Phrase

Phrase New

Loqalit now works inside Phrase. When a translator finishes a job, Loqalit scans that language on its own and leaves each bug as a comment on the string, with a screenshot, visible to that language’s translators. When the follow-up scans come back clean, it marks the same thread fixed.

Job donePhrase tells Loqalit the German job is finished.ScanOnly the German pages, once the strings reach staging.CommentOn the string, with a screenshot, for the German translator.FixedA second note when the bug is gone.

Crowdin

Accepted fixes are posted to your Crowdin project as comments with a screenshot.

GitHub Actions

A release gate: the Loqalit step fails the build when a scan of your staging site finds critical or major issues. The findings and screenshots are in your inbox.

Slack

After a scan, you can send its summary to your Slack channel.

Signed webhooks

Send Loqalit events to your own systems, signed with your own keys. Phrase Orchestrator, for example, can start a workflow when a scan finds a critical issue.

REST API

Work with Loqalit programmatically, with your own API keys.

AI assistants (MCP)

Ask Claude, ChatGPT, Cursor or Claude Code to scan a page or check strings with Loqalit, and get MQM-scored findings back in the chat.

Chrome extension

The Chrome extension is one way to run Loqalit on demand; the platform runs scheduled scans without anyone logged in.

Release gate

Block a release when a locale breaks

Add Loqalit as a step in your GitHub Actions workflow. Pointed at your staging site, it starts a scan of the pages and languages you set, waits for it to finish, and fails if it finds critical or major issues, so the release waits. Each finding is in your Loqalit inbox with its screenshot.

API keys. Create a key in your Loqalit project under Settings → Integrations, for the GitHub Actions step and the REST API. Only people who can edit the project can create one. Each key works for that one project and can be revoked at any time, and we store only a hash of it.

Staging. Use a fixed staging address. A preview URL that changes with every pull request is scanned as a new site each time, so it can’t block a release.

Using another TMS?

The same flow is built to plug into other TMSs too.

Loqalit has no native integration with other TMSs such as Lokalise or memoQ yet. You can export findings (CSV, XLSX, PDF or JSON) or connect through signed webhooks and the REST API. On another TMS? Tell us which.

Schedule it. Forget it. Ship it.

Start with a free QA report. We scan your live site in up to 3 languages and email you the findings with screenshots, MQM severities and suggested fixes.