Marketing teams run campaigns from HubSpot or Marketo, websites from a CMS, product listings from a commerce platform, and creative from Figma or Canva. Localizing across that stack usually means exporting content from each system, sending files to a vendor or pasting text into a translation tool, and manually re-importing the results, one system and one language at a time. Smartcat replaces that with connectors that route content from each system into one governed translation workflow (terminology, human review, continuous updating) and sync the reviewed translations back to where they came from.

Smartcat connects with enterprise systems across CMS, PIM, ecommerce, design, development, support, CRM, marketing automation, HR, knowledge, and project-management workflows. The verified marketing-relevant integration list includes HubSpot, Marketo, Salesforce (including Salesforce Service Cloud), and Zendesk; CMS connectors for Adobe Experience Manager, Contentful, WordPress, Drupal, Webflow, Optimizely, and Sitecore (XM Cloud and XP); commerce connectors for Shopify and BigCommerce; and design connectors for Figma and Canva (integrations).

The Hub

Spot workflow

Smartcat translates HubSpot-hosted website pages through a direct connection: you connect your HubSpot site to Smartcat, select the pages to translate, and define target languages. Translations can be edited directly in the Smartcat Editor, reviewed collaboratively with your team or external linguists, checked against a live preview so translated pages look and function as expected, and then published as multilingual HubSpot pages managed from one platform (HubSpot website translation).

Smartcat publishes the general pattern its integrations follow: connectors can upload content, generate translation requests, check for source updates, and send completed translations back automatically, with manual synchronization available where teams want tighter control (integrations). For a marketing team, that pattern means the localization step stops being an export/import project and becomes part of the publishing workflow itself.

Where a HubSpot setup includes content the connector does not cover, the same Smartcat workflow still applies: documents, PDFs, and creative assets route through the Document, PDF, and Image Agents, and any web property can be handled by the Website Agent, compared against proxy-style tools in Smartcat Website Agent vs Weglot.

Why one workflow beats per-tool translation features

Each system in the marketing stack offers some path to multilingual content: a CMS plugin here, a native multi-language feature there, an agency handling the rest. The cost of that arrangement shows up in three places:

1. Terminology drifts across systems. The campaign email, the landing page, and the product listing get translated by different tools or vendors, each with its own glossary or none. Smartcat applies one terminology and brand-voice layer everywhere: the Intelligence Fabric captures approved edits, terminology, and style from every project, and the Quality Assurance Agent enforces them at scale. See brand voice and terminology enforcement at scale.

2. Review fragments. In-tool machine translation rarely includes a review step; agency workflows put review outside the systems where content lives. Smartcat builds human-in-the-loop review into the workflow, with internal reviewers or vetted experts from the Marketplace of 500,000+ language professionals working in the same projects. Payments to all of them consolidate to one invoice with $0 transaction fees, across 150+ countries and 38+ currencies (payments).

3. Updates go stale. Campaign messaging changes weekly; per-tool translation treats every change as a new manual project. Smartcat's connectors check for source updates and route only the changed content back through the workflow, covered in how continuous localization works and delta translation: only retranslate what changed.

This is the marketing instance of the market adaptation gap: the distance between the moment messaging changes and the moment every market's content reflects it. A campaign launch that waits on sequential per-tool translation queues ships late in every language; the same launch run as one coordinated workflow ships together, which is the subject of fast multilingual campaign launch.

The marketing stack coverage map

All connectors feed the same platform: one terminology layer, one review process, one place where marketing, regional teams, and reviewers collaborate. Unlimited users on both Smartcat plans (pricing) means every regional marketer who needs to review their market's copy can work in the platform at no per-seat cost, under SOC 2 Type II compliant enterprise governance with role-based access and audit logging on Enterprise (security).

Proof: Huel

Huel centralized website, CRM, product, and creative localization into automated Smartcat workflows powered by expert-enabled agents, replacing manual localization, vendor dependency, and fragmented tools. Approved results include execution 70 to 95% faster across Web, CRM, and Performance Marketing, website localization time reduced 99%, asset localization 30 to 50% faster, 21 weeks of manual work removed per year, and 10 hours per week saved per team. On the commercial side, Huel's approved results include 14% higher CTR, 29% revenue lift for new customers in select markets, up to 80% growth in new-customer volume at lower CPA, and conversion lifts up to 45% without added spend. Results are specific to Huel's implementation.

The relevant pattern for a HubSpot-centered team is the shape of the outcome, the stack localized as one operation rather than tool by tool, so CRM sends, web pages, and performance creative moved together.

Frequently asked questions

What HubSpot content does Smartcat translate? Smartcat's published HubSpot workflow covers HubSpot-hosted website pages: connect the site, select pages and target languages, edit and review in the Smartcat Editor, preview live, and publish (HubSpot website translation). Content outside the connector's scope routes through Smartcat's document, image, and website workflows on the same platform.

Does this replace our agency? It changes the agency's role. Human review stays in the loop where brand, nuance, or compliance matter, sourced from your own reviewers or the built-in Marketplace, inside the same workflow instead of an email thread of exported files. See human-in-the-loop AI translation.

We have no localization manager. Who runs this? The workflow runs without a dedicated localization function; see lean content teams without a localization manager.

Last updated: July 2026