Phrase

What is Phrase: Phrase is a cloud-based translation management system that automates multilingual content creation. It provides translation memory, glossaries, and machine translation to help teams maintain consistent terminology across languages and projects.

How to integrate Phrase with Webflow

The three integration methods here suit different technical setups and team structures. The official Phrase app covers most content teams: install it from the Webflow Apps Marketplace, send pages and CMS collections to Phrase, and pull completed translations back into Webflow locales with no code required. Automation platforms like Zapier, n8n, and viaSocket let you trigger translation jobs from CMS events without manual steps. Direct API integration using the Phrase Strings API and Webflow API supports custom sync pipelines, webhook-driven job creation, and programmatic locale management for teams with developer resources. Most production implementations combine two or more of these approaches.

Before setting up any method, enable localization in your Webflow site and create your target locales. The Phrase app and all API-based methods require this configuration to exist before content can be sent or received.

Use the Phrase app

Install the Phrase app from the Webflow Apps Marketplace. It provides a direct connection between your Webflow site and Phrase TMS, letting you authenticate, select content, and send it to Phrase, and import completed translations back, without writing any code.

To set up the integration:

1. Install the Phrase app from the Webflow Apps Marketplace
2. Authenticate using your Phrase username and password (use your Phrase username, not your email address, as described in the Phrase Webflow TMS guide)
3. Select content for translation and send it to Phrase from within Webflow
4. Import completed translations individually or in bulk back into your Webflow locales

The app supports the following content types:

• Static pages, with all text content sent to Phrase for localization
• Webflow CMS collections and items, with translated content mapped back to the correct locale fields
• Reusable components
• SEO metadata, including page titles and meta descriptions, sent alongside page content in translation jobs
• Select/Option elements, so dropdown menus and form field options can be localized across languages

Completed translations import in bulk, so you can update multiple locales at once after translators finish their work in Phrase.

Note: Webflow's localization APIs require careful handling of cmsLocaleId when creating and updating items programmatically. For simpler setups, create CMS items in Webflow first, then use the Phrase app to send them for translation.

Connect with Zapier, n8n, or viaSocket

Automation platforms connect Phrase and Webflow to trigger translation jobs from CMS events without manual steps. This suits teams who want new content to enter Phrase automatically when it's published, or who want Webflow updated as soon as translations are complete.

Zapier offers a Phrase and Webflow integration with Phrase triggers for new or updated jobs and Webflow triggers like new CMS items and form submissions. Check the Zapier integration page for the current list of trigger and action names, as these can change. n8n includes a Webflow node for creating and updating collection items and can react to Webflow events via webhooks, while you connect to Phrase via HTTP Request nodes. viaSocket can connect Phrase and Webflow through its no-code workflow builder, with Phrase triggers and Webflow actions such as creating or updating items. Check the viaSocket integration catalog for the current trigger and action list.

Common automation patterns using these platforms include:

• Triggering a Phrase translation job when a new CMS item is created in Webflow
• Updating Webflow CMS items with translated content when a Phrase job completes
• Sending a Slack or email notification when translations are ready for review

As of writing, Phrase does not offer native connectors for Make.com or IFTTT, so those platforms would require generic HTTP or webhook modules rather than a pre-built Phrase app.

Note: CMS items created via the Webflow API require consistent cmsLocaleId mapping for locale sync to work correctly. For automation-triggered content, test locale field mapping carefully before deploying to production.

Build with the Webflow and Phrase APIs

For custom localization pipelines, both platforms provide REST APIs. This approach suits sites with large CMS libraries, custom translation routing logic, or multi-step review workflows. It requires developer resources — this is not a no-code path.

The Phrase Strings API uses token-based authentication with the header Authorization: token TOKEN and a base URL of https://api.phrase.com/v2. The Webflow Data API v2 uses Bearer token authentication with the header Authorization: Bearer <token> at https://api.webflow.com/v2.

Extract and prepare content from Webflow:

• GET /collections/:collection_id/items to retrieve translatable text from Webflow CMS collections, using offset and limit parameters for pagination on large catalogs
• POST /v2/projects/:project_id/keys to register content strings in Phrase as translation keys
• GET /v2/projects/:project_id/locales to list and configure target languages in your Phrase project
• POST /v2/projects/:project_id/keys/search to find specific content segments for targeted translation updates

Push completed translations back to Webflow:

• PATCH /collections/:collection_id/items/:item_id with the cmsLocaleId query parameter to target specific locale variants when writing translations back
• PATCH /collections/:collection_id/items/bulk to update multiple items per request in batches, keeping API calls efficient for large collections
• POST /sites/:site_id/publish to deploy translated content across all locales

When writing translations back in bulk, batch your updates into smaller groups to stay within Webflow API constraints. Refer to the Webflow API reference for current rate limits and pagination guidance.

One important constraint: Webflow does not provide API endpoints for creating, updating, or deleting locale configurations. All locale setup — primary locale, secondary locales, and routing method — must be completed in Webflow before API-driven content sync can begin.

Automate with webhooks

Webhooks from both platforms replace manual triggers and polling with event-driven synchronization. Configure webhooks in Phrase that fire when translations are created or updated — for example, when a translation job is completed. Check Phrase's webhook documentation for the current list of supported event names. On the Webflow side, register webhooks for events like collection_item_created to detect new CMS content that needs translation.

A typical automated flow looks like this:

1. A new CMS item is created in Webflow and sent to Phrase for translation — either via the official Phrase app or a custom API implementation
2. Your middleware extracts the content via the Webflow API and transforms it into Phrase-compatible format
3. The content is submitted to Phrase as translation keys within a translation project
4. Phrase fires webhook events when translators complete their work
5. Your middleware retrieves the completed translation via the Phrase API and prepares it for Webflow
6. Translated content is written back to Webflow CMS items with the correct cmsLocaleId, then staged items are published

This setup works best when you maintain consistent item IDs and cmsLocaleId mappings throughout the pipeline.

What you can build with the Phrase Webflow integration

Integrating Phrase with Webflow supports multilingual site delivery across content types — from product catalogs and marketing pages to help centers and campaign landing pages — with translation workflows managed centrally in Phrase rather than through fragmented handoffs.

Here are a few things you can build:

• Multilingual marketing site: A SaaS product site with localized landing pages, feature descriptions, and SEO metadata, where translation memory in Phrase maintains consistent terminology across language versions as content evolves.
• Localized e-commerce catalog: A Webflow CMS product catalog where product names, descriptions, and category pages are translated through Phrase and synced to each locale automatically when source content changes in Shopify or another backend.
• Global help center: A Webflow CMS knowledge base where new articles trigger translation jobs in Phrase and completed translations are pushed back to locale-specific pages without manual import steps.
• Region-specific campaign pages: Marketing landing pages translated through Phrase with brand glossaries enforced across all languages, published with localized URLs and hreflang tags managed through Webflow's localization features.

To get started, install the Phrase app from the Webflow Apps Marketplace. For API-based pipelines, the Webflow localization documentation and Phrase Webflow TMS guide cover the full configuration process.