Smartcat Integrations: Overview and Full List

Overview

Smartcat integrates with a wide range of third-party tools and platforms, letting you automate content exchange between your existing systems and Smartcat's translation workflows. Instead of manually exporting and importing files, integrations let Smartcat connect to your content source, translate it, and return the translation — on a schedule or on demand.

Smartcat's integrations fall into two distinct technical systems, and the difference matters for how you set them up and what they do:

  1. iHub connectors — connect Smartcat to a content backend (CMS, PIM, eCommerce, file storage, code repository, support tool) to pull source content in, translate it, and push translations back. These support auto-import/export rules and scheduled syncs.

  2. Website Translator — translates a published website on the fly using a JavaScript snippet (no content backend connection). Best for marketing sites and no-code website builders.

The marketing list of integrations is also available on the Smartcat website: https://www.smartcat.com/integrations/category/all-integrations/

⚠️ Note on sources: This list is reconciled against the Smartcat codebase (the source of truth for what is technically wired up). Some connectors may be behind feature flags, partner-specific, or not yet listed publicly on the website. Confirm availability for a specific connector before promising it to a customer.


System 1 — iHub Connectors

iHub connectors link Smartcat to a content backend. Smartcat reads source content from the connected system, creates translation projects, and writes the translations back into the system. iHub connectors support:

  • Auto-import / auto-export rules — automatically pull new/changed content and push completed translations back.

  • Scheduled syncs — run the exchange on a recurring schedule.

  • Manual sync — trigger an exchange on demand.

Content Management Systems (CMS) & DXP

Integration Notes
Contentful Available as an iHub connector and as a Contentful app/plugin.
Sanity iHub connector with locale mapping.
Kontent.ai Delivery + Management API keys.
Craft CMS Requires the Smartcat plugin installed in your Craft CMS instance.
Optimizely Connect via client ID and client secret.
Amplience Connect via client ID, client secret, and content hub.
ButterCMS Supports Page Types and locale mapping.
Drupal Via the TMGMT connector.
Adobe Experience Manager (AEM) Cloud Service or on-premise via the Smartcat Connector.
Sitecore Connect Sitecore content for translation.
WordPress (WPML) Via the WPML plugin.

Product Information Management (PIM) & eCommerce

Integration Notes
Salsify Pull product content in, push translations back to localized fields.
Akeneo Connect via API URL, client ID, and client secret.
inriver Connect via base URL and REST API key (admin access required).
Centra Connect via GraphQL endpoint URL and API key.
Shopify Connect via store URL and access token; optional GraphQL endpoint.
Salesforce Commerce Cloud Connect via base URL, client ID, and client secret. Supports content assets, catalogs, products, libraries, etc.
BigCommerce Listed on the website; confirm current availability.

CRM, Support & Marketing

Integration Notes
Zendesk Connect via Help Center URL, account email, and API key.
Salesforce Service Cloud Connect via My Domain URL and connected-app credentials.
Salesforce Marketing Cloud Server-to-server API integration.
ServiceNow Listed on the website; confirm current availability.

Documentation & Knowledge

Integration Notes
Paligo CCMS connector — base URL, username, and API key.
ReadMe Developer documentation; listed on the website.

File Storage & Cloud Documents

Integration Notes
Google Drive Place Google Docs in a folder; Smartcat creates _translations folders for output.
Google Docs / Google Sheets Translate Google Docs and Sheets content.
OneDrive Connect via tenant ID, client ID/secret, and folder URL.
SharePoint Documents Translate documents stored in SharePoint.
SharePoint Pages Translate SharePoint site pages (distinct from SharePoint Documents).

Code Repositories (Continuous Localization)

Integration Notes
Android Translate Android resource files.
iOS Translate iOS string files.
Java Translate Java resource bundles.
GitHub / GitLab / Bitbucket Connect repositories for continuous localization (listed on the website).
Jira Connect Jira for project/issue content.

Design

Integration Notes
Figma Translate Figma files via the "Smartcat Translator" plugin, with live preview in the Smartcat editor.

Localization Tools

Integration Notes
Lokalise API token requires both Read and Write permissions.

Custom Integration — Remote API Connector

Integration Notes
Remote API connector Build your own iHub connector by registering a remote API endpoint (with optional OAuth). Lets you connect a system Smartcat doesn't have a native connector for, including custom locale mapping.

System 2 — Website Translator

The Website Translator translates a published website on the fly. Instead of connecting to a content backend, you add a small JavaScript snippet to your site; Smartcat then serves AI-translated versions of your pages. This is the right choice for marketing sites and no-code/low-code website builders.

Website Translator integrations work differently from iHub connectors — they do NOT pull content into a Smartcat project for backend exchange. They translate the rendered website and publish localized versions via the snippet.

Platform Notes
Wix AI-translate Wix pages via a JavaScript snippet.
Webflow Translate and publish Webflow pages via the snippet.
Squarespace Translate Squarespace content including text, images, and video.
WooCommerce Translate WooCommerce store content.
Ghost Translate Ghost website content.
Weebly Translate Weebly website content.
Joomla Push Joomla site content for translation.
Framer Translate Framer websites.
Tumblr Translate Tumblr content.
Instapage / Lander / Leadpages / Unbounce / Pagewiz Translate landing pages built on these platforms.

💡 WordPress note: WordPress can be translated two ways — via the WPML plugin (iHub connector) for backend content exchange, or via the Website Translator snippet for on-the-fly site translation. Choose based on whether you need to manage translations inside WordPress (WPML) or just serve translated pages (Website Translator).


Browser Extensions & Desktop Apps

These are real-time / standalone tools rather than backend integrations:

Tool Notes
Smartcat Translator for Chrome Translate web content on the fly via the Chrome extension.
Smartcat for Windows / macOS / Linux Desktop apps to translate files and manage localization projects.

Smartcat API

For anything not covered by a native connector, use the Smartcat open REST API to build a fully custom integration — automated project creation, status tracking, file upload/download, and callback notifications.

  • API documentation: https://developers.smartcat.com

(For a no-code custom connector, see the Remote API connector under iHub above.)


Setting Up an Integration

Step 1 — Open your workspace

  1. Go to your Smartcat workspace.

  2. Click the Set up integration shortcut on the homepage.

Step 2 — Choose your integration

  1. Select the integration you want from the list.

  2. Follow the on-screen instructions for that platform.

⚠️ Setup steps vary by integration and by system (iHub vs. Website Translator). Each integration will have a dedicated help article with full setup instructions — links will be added below as those articles are created.


  • Full integrations list on Smartcat.com: https://www.smartcat.com/integrations/category/all-integrations/

  • Smartcat API documentation: https://developers.smartcat.com

  • Setting Up Integrations in Smartcat: An Overview (link when available)

  • Setting Up Auto Import and Export Rules for Integrations (link when available)

Still need help?

Our support team responds within one business day.

Open a support case