Skip to main content
Connect the systems that hold your content or provide tools for your workflows. A connection gives access; you still need to configure the task or sync that uses it.

​
GitHub

Connect the GitHub App, enable the repositories you need, then configure content sync or an automation trigger. Refreshing the repository list does not move files.

​
Canva

Create a Canva connection with a personal token. Designers pick the native project in the Canva app. Jobs use that project’s source and target languages. There is no separate Canva locale list. Follow Localize Canva to collect page files and apply existing translations.

​
Figma

The Figma plugin uses a personal token to extract text, create translation jobs, and pull completed locales. See design tools for access requirements and availability.

​
GitLab

An administrator can connect GitLab from Integrations through the authorization flow. Connected GitLab.com projects that you can clone with Reporter access or higher can be used as repository context in chat. Select a project or provide its project or merge-request URL. Use Use GitLab repo in a manual or scheduled automation for repository analysis. Merge-request comment tools and GitLab content sync are not available in this workflow.

​
Intercom

Connect Intercom from Integrations, then create a scheduled or manual automation with the Translate Intercom Help Center articles skill. Import writes markdown source files into a native project. Push to Intercom writes Intercom drafts. It does not publish. See Localize Intercom Help Center articles.

​
Braze

Connect Braze from Integrations with a REST API key and REST cluster. Two workflows share that connection. Apply Translate Braze Email Templates or Translate Braze Campaigns & Canvas from Popular or Marketing. Do not attach both on one automation. Email Templates imports HTML and Push to Braze writes locale-suffixed library copies. Campaigns & Canvas imports tagged draft JSON maps and writes approved locales through the Translation API. Neither action publishes. See Localize Braze.

​
Other external services

Use the provider’s Connect action in Integrations, complete authorization or supply the requested credential, then select that tool in your automation. Availability and actions differ by provider; a catalog entry does not guarantee content sync. For Ahrefs, connect the account and add the Ahrefs tool to the automation. For Zernio, save a valid API key, then select the Zernio tool and connection. Confirm the intended account and action before running tasks that publish or change external content.

​
MCP server connections

To let an automation call tools on an external MCP server:
  1. Open Integrations → MCP Server.
  2. Enter a display name, HTTPS endpoint, transport (http or sse), and the required authentication.
  3. Save and validate the connection.
  4. Add the MCP Server tool to an automation and select the connection.
This connects Platform to an external server. To connect an agent such as Cursor to Platform, use the hosted MCP server instead.

​
Slack Connect

Use the Slack integration for bot tools and automation notifications in your Slack workspace. The Slack Connect invitation on workspace Overview, when available, creates a shared support channel instead. See Contact support.

​
API keys and tokens

Manage organization keys and personal tokens in Settings. If a connection fails or a resource is missing, use Connection troubleshooting.

​
Translation management systems

Connect supported Crowdin, Lokalise, Phrase Strings, or Smartling workflows through Platform TMS integrations. For repository and CI operations, use the all-in-one Hyperlocalise CLI. Provider-specific commands and Platform connections have separate capabilities and credentials.