Skip to main content
Lokalise is a translation management platform that agile teams use to manage multilingual content. Teams that write campaign content in MoEngage move it to Lokalise for translation and then rebuild each localized campaign by hand. The Lokalise connector gives your Custom Agents access to your Lokalise account over the Model Context Protocol (MCP). An agent finds the content that needs translating, sends it to Lokalise, brings the translations back into MoEngage, and builds the campaign from them. There are no API keys to exchange between the two platforms and no app to install in Lokalise.
Custom Agents and Connectors are currently Early Access features. If you do not see AI Agents > Connectors in your dashboard, contact your Customer Success Manager (CSM) to request access.
MoEngage also integrates with Lokalise through the MoEngage app in Lokalise, which syncs saved templates between the two platforms. Use that approach when you translate campaign templates and want each language to arrive as its own template. Refer to Lokalise.

​
Overview

You connect your Lokalise account once on the Connectors page, and its tools become available to every Custom Agent you run. Each user connects their own Lokalise account, and an agent works with the account of the person who starts the run.

​
Prerequisites

Before you begin, make sure that:
  • Your workspace has Custom Agents and Connectors enabled.
  • You have an active Lokalise account with access to the translation projects you want to use.
  • Your MoEngage role includes permission to create content blocks and campaigns. A Custom Agent acts within the MoEngage permissions of the user who runs the agent. Refer to Custom Agent Essentials: Permissions and Security.

​
Generate a Lokalise API Token

Connecting Lokalise requires a personal API token from your Lokalise account:
  1. In Lokalise, click your avatar in the lower-left corner, and then click Profile Settings.
    Lokalise account menu with Profile Settings highlighted
  2. Click API tokens.
  3. Click Generate new token.
  4. Copy the token.
    API tokens tab of a Lokalise profile with the tab, the token, and the Generate new token button highlighted
Keep the token somewhere safe. Lokalise lists it on this page, where you can also delete it when you no longer need the connection.

​
Connect Lokalise to MoEngage

  1. On the sidebar menu in MoEngage, hover over the Merlin AI menu item Merlin AI menu icon. The Merlin AI menu appears.
  2. Click Connectors.
    Merlin AI menu open on the sidebar with Connectors highlighted
  3. In the Search box, enter Lokalise.
  4. Click the Lokalise card. The Connection details dialog appears.
    Connectors page filtered to Lokalise, showing the Lokalise connector card
  5. Review the tools Lokalise provides and the terms of usage, and then click Connect.
  6. On the Merlin AI wants to connect to your Lokalise page, paste your token in API Token, and then click Connect.
    Page asking for a Lokalise API token with the field and the Connect button highlighted
  7. Close the window once it confirms the connection, and then return to the MoEngage dashboard.
    Window confirming that Merlin AI is connected to Lokalise
Lokalise moves to Connected, and a message confirms that your agents can use its tools. To find Lokalise again later, use the Connected filter or the Search box.
Connectors page with a message confirming that Lokalise is connected
For the complete connector behavior, per-tool controls, and terms of usage, refer to Connect External Apps to Custom Agents.

​
Use Cases

Marketing teams write content blocks in MoEngage in one language and need them in several others. A Custom Agent with access to Lokalise covers that work from end to end:
  • Scheduled translation runs. Translate the content blocks your team created or edited since the last run, on a schedule, without anyone moving files between the two platforms.
  • Translated campaigns built for you. Create campaigns from the returned translations, so a localized campaign is ready to review instead of waiting to be rebuilt by hand.
  • Review before anything goes out. Leave translated campaigns as drafts, so a marketer approves each one before it reaches users.
  • Consistent wording across markets. Keep the keys and translations an agent writes back in the same Lokalise project your translators already work in.

​
Tools

The Lokalise connector covers projects, keys, translations, and contributors, along with file uploads and downloads and translation workflows. The Connection details dialog lists every tool the connector provides along with its description and its status, either Enabled or Disabled. To control which tools your agents can call:
  1. On the Connectors page, click the Lokalise card. The Connection details dialog lists every tool with its description and its status.
  2. Select the checkbox next to each tool you want to change.
  3. Click Enable or Disable. The Status column updates for each tool you selected.
    Connection details dialog for a connected Lokalise account with two tools selected in the table
Disabling matters most for the tools that change data in Lokalise rather than read it. A tool’s status belongs to the connector rather than to an individual agent, so it applies to every agent you run, and you can change a status at any time. Refer to Enable or Disable a Connector’s Tools.

​
Example Usage

A connected application is available to every agent you run, so there is nothing to attach in the Agent Builder. What the agent does with Lokalise comes from the instructions you write. On the sidebar menu in MoEngage, hover over the Merlin AI menu item Merlin AI menu icon, click Custom Agents, and create an agent from scratch. Describe the job you want done, answer the questions Merlin AI asks, and set the schedule you want the agent to run on. Refer to Create and Manage Custom Agents.
Merlin AI menu open on the sidebar with Custom Agents highlighted

​
Translate Content Blocks and Create a Campaign

The following instruction covers a complete translation workflow, from finding the content to leaving a campaign ready for review:
Agent Instruction
On each run, the agent finds the content blocks by tag rather than by name, sends only what it has not sent before, waits for the translations to complete, writes them back as content blocks, and creates the campaign as a draft.
Name every detail the agent cannot infer, including the target languages, the channel, the platforms within that channel, the audience, and what to do with campaigns that are already live. The agent leaves out whatever you do not name, and you then correct it on the draft.
Run the agent a few times against your own content before you make it live, and keep the campaigns as drafts until you trust the output. Refer to Test Agent and Make the Agent Live.
MoEngage does not gate a connector write. An agent that reaches Lokalise can change data in your Lokalise account, so disable the write tools your agents do not need and write the same rule into the agent’s instructions.

​
FAQs

The MoEngage app in Lokalise syncs saved templates between the two platforms, and you import and export each one. The connector gives a Custom Agent access to your Lokalise account, so the agent finds the content, translates it, and builds the campaign on a schedule you set. Refer to Lokalise.
Yes. You connect an application once, and it becomes available to every agent you run. The agent’s instructions decide whether it uses Lokalise on a given run. Refer to How Connectors Work.
The account of the person who starts the run. Each teammate generates their own API token and connects their own Lokalise account on the Connectors page, so an agent works with that teammate’s Lokalise projects when they run it.
Yes, when a tool that writes to Lokalise is enabled. MoEngage does not ask for your approval before a connector write. Disable the tools you want kept out of reach, and write your agent’s instructions to match.
Reconnect Lokalise on the Connectors page in a separate browser tab, and then send your next message in the same session. Restate any step that the agent skipped so that the agent retries the step. Refer to Reconnect During a Run.