---
title: "Connect Lokalise and Myphoner - APIANT.ai"
description: "When \"Contributor Added\" fires in Lokalise, your agent runs \"Create Lead\" in Myphoner."
canonical: "https://apiant.ai/connect/lokalise-to-myphoner"
---

# Connect Lokalise and Myphoner

When **Contributor Added** fires in [Lokalise](https://apiant.ai/connections/lokalise), your agent runs **Create Lead** in [Myphoner](https://apiant.ai/connections/myphoner), or **Lead updated (instant)** in Myphoner to **Create a Task** in Lokalise. Describe the whole flow and it is built, tested on every scenario and kept running.

Lokalise **16** triggers Lokalise **26** actions Myphoner **11** triggers Myphoner **14** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Lokalise and Myphoner to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Lokalise and Myphoner can do together

### From Lokalise to Myphoner

- When **Contributor Added** in Lokalise then **Create Lead** in Myphoner
- When **Key Added** in Lokalise then **Update Lead** in Myphoner

### From Myphoner to Lokalise

- When **Lead updated (instant)** in Myphoner then **Create a Task** in Lokalise
- When **New call (instant)** in Myphoner then **Create Comment** in Lokalise

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Lokalise and Myphoner

## Triggers and actions 27 triggers · 40 actions

- Trigger

**Contributor Added**

Triggers when a new contributor is added to a Lokalise project.

- Trigger

**Contributor Removed**

Triggers when a contributor is removed from the selected Lokalise project.

- Trigger

**Key Added**

Triggers when a new translation key is added to a Lokalise project, whether individually or in bulk (import, API or bulk action). Fires once per added key.

- Trigger

**Key Comment Added**

Triggers when someone adds a comment to a translation key in a Lokalise project.

- Trigger

**Key Modified**

Triggers when a translation key is modified in a Lokalise project, either individually or in bulk (renames, tag changes, file assignments, hiding).

- Trigger

**Key Removed**

Triggers when one or more translation keys are removed from a Lokalise project, whether deleted individually, in bulk, through the API, or moved to another project. Fires once per removed key.

- Trigger

**Language Added**

Triggers when one or more languages are added to a Lokalise project, firing once for each language added.

- Trigger

**Language Removed**

Triggers when a language is removed from a Lokalise project.

- Trigger

**Poll Tasks**

Triggers when a new task is created in a Lokalise project.

- Trigger

**Project Exported**

Triggers when translation files are downloaded (exported) from a Lokalise project.

- Trigger

**Project Imported**

Triggers when a translation file is uploaded to a Lokalise project. Fires once per uploaded file.

- Trigger

**Project Snapshot**

Triggers when a snapshot is taken of the selected Lokalise project.

- Trigger

**Task Created**

Triggers when a new translation or review task is created in a Lokalise project.

- Trigger

**Task Deleted**

Triggers when a task is deleted in a Lokalise project.

- Trigger

**Translation Reviewed**

Triggers when a translation is marked or unmarked as reviewed in a Lokalise project, individually or in bulk.

- Trigger

**Translation Updated**

Triggers when a translation is changed in the selected Lokalise project, either one at a time or several at once through a bulk action, file upload or the API.

- Action

**Add Contributor**

Adds a contributor to a Lokalise project, inviting them by email with the chosen languages and permissions.

- Action

**Add Languages**

Adds one or more languages to a Lokalise project, optionally overriding each language's code, name and plural forms.

- Action

**Create a Key**

Creates a new translation key in a Lokalise project, optionally with its translations, tags, comments and screenshots, and returns the new key.

- Action

**Create a Task**

Creates a translation, review or automatic-translation task in a Lokalise project for the chosen keys and languages.

- Action

**Create Comment**

Adds a comment to a translation key in a Lokalise project.

- Action

**Create Project**

Creates a new Lokalise project in your team, optionally with its languages, base language and project type. Returns the created project.

- Action

**Create Snapshot**

Creates a snapshot of a Lokalise project, saving its current state so it can be restored later.

- Action

**Delete a Key**

Deletes a key, with its translations, from a Lokalise project.

- Action

**Delete a Language**

Removes a language from a Lokalise project.

- Action

**Delete a Task**

Deletes a task from a Lokalise project.

- Action

**Download Files**

Exports a Lokalise project's translation files as a.zip bundle and returns the download URL of the bundle.

- Action

**List All Orders**

Returns all translation orders placed under a Lokalise team.

- Action

**List All Tasks**

Returns the tasks in a Lokalise project, optionally filtered by title or status.

- Action

**List All Translations**

Returns the translation items of a Lokalise project (one row per key and language), optionally filtered by language, review status, QA issues or task.

- Action

**List Project Languages**

Returns the languages set up in a Lokalise project, with each language's code, name, direction and plural forms.

- Action

**List Snapshots**

Returns the snapshots saved for a Lokalise project, with each snapshot's title and creation details.

- Action

**Remove Contributor**

Removes a contributor from a Lokalise project.

- Action

**Retrieve a Comment**

Returns a single comment left on a key in a Lokalise project, including its text, author and when it was added.

- Action

**Retrieve a Contributor**

Returns a contributor of a Lokalise project, including their email, name, role flags, languages and permissions.

- Action

**Retrieve a Key**

Returns one translation key from a Lokalise project, including its names, description, platforms, tags, comments, screenshots and translations.

- Action

**Retrieve a Task**

Returns a Lokalise task, including its status, progress, due date and the languages and assignees it covers.

- Action

**Retrieve Project**

Returns a Lokalise project's details, including its name, type, base language, settings and translation statistics.

- Action

**Update a Key**

Updates an existing key in a Lokalise project, such as its name, description, platforms, tags or flags, and returns the updated key.

- Action

**Update a Translation**

Updates the text and review flags of a translation in a Lokalise project.

- Action

**Update Language**

Updates a language in a Lokalise project, changing its code, name or plural forms.

- Action

**Upload File**

Uploads a localization file to a Lokalise project and queues it for import. Returns the queued import process so you can follow its status.

- Trigger

**Archived Lead**

Triggers when a lead is archived (marked 'archive').

- Trigger

**Call Back**

Triggers when a lead is marked for 'call back'.

- Trigger

**Lead updated (instant)**

Fires when a lead's information is updated by an agent (webhook event: lead_updated).

- Trigger

**Lost Lead**

Triggers when a lead is lost (marked 'loser').

- Trigger

**New call (instant)**

Fires when a new call is conducted (webhook event: new_call).

- Trigger

**New call recording (instant)**

Fires when a new call recording becomes available (webhook event: new_recording).

- Trigger

**New comment (instant)**

Fires when a new comment is created for a lead (webhook event: new_comment).

- Trigger

**New lead (instant)**

Fires when a new lead is created in Myphoner (webhook event: lead_created).

- Trigger

**New Winner**

Triggers when a lead is won.

- Trigger

**Text message received (instant)**

Fires when a text message is received from a lead (webhook event: inbound_text).

- Trigger

**Text message sent (instant)**

Fires when a text message is sent to a lead (webhook event: text).

- Action

**Archive a lead**

Archives a lead in Myphoner, optionally recording a comment and archive category, or scheduling the lead to come back for a call later.

- Action

**Create a list**

Creates a new lead list in Myphoner, optionally defining its columns.

- Action

**Create Lead**

Creates a lead in a Myphoner list. The lead's fields are the columns defined on the chosen list.

- Action

**Find Lead**

Searches Myphoner for a lead matching your text and returns the first match, optionally limited to certain lists.

- Action

**Get a lead**

Returns one Myphoner lead by its ID, including every column defined on the lead's list.

- Action

**Get a list**

Returns one Myphoner list by its ID, with its name, lead count and the categories configured for each lead state.

- Action

**List leads**

Returns a page of leads from a Myphoner list, newest-updated first when you ask for that order.

- Action

**List lists**

Returns every lead list in the Myphoner account, with each list's name, ID and lead count.

- Action

**Mark Lead as Loser**

Marks a Myphoner lead as lost, optionally recording a comment and loser category or scheduling it to come back for a call later.

- Action

**Mark Lead as Winner**

Marks a Myphoner lead as won, optionally recording a comment and winner category or scheduling it to come back for a call later.

- Action

**Mark Lead for Call Back**

Schedules a Myphoner lead for a call back, optionally recording a comment and category and setting when the lead should come back.

- Action

**Move a lead to another list**

Moves a Myphoner lead into a different list, optionally releasing it back to the calling queue.

- Action

**Search for Lead**

Searches Myphoner leads for your text and returns every match, optionally limited to certain lists.

- Action

**Update Lead**

Updates a lead in Myphoner. Only the fields you fill in are changed; the lead's fields are the columns defined on its list.

## Each app on its own

- [ **Lokalise** Lokalise is a translation management tool that lets you structure and automate workflows while encouraging...](https://apiant.ai/connections/lokalise)
- [ **Myphoner** Myphoner is a cold calling tool used for lead management and lead tracking, with the focus of creating a...](https://apiant.ai/connections/myphoner)

Reviews

## What our customers say

## More from Lokalise

- [ **Lokalise to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/lokalise-to-salesforce)
- [ **Lokalise to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/lokalise-to-slack)
- [ **Lokalise to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/lokalise-to-mailchimp)
- [ **Lokalise to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/lokalise-to-stripe)
- [ **Lokalise to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/lokalise-to-shopify)
- [ **Lokalise to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/lokalise-to-quickbooks-online)

## More into Myphoner

- [ **HubSpot to Myphoner** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-myphoner)
- [ **Gmail to Myphoner** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-myphoner)
- [ **Google Calendar to Myphoner** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-myphoner)
- [ **Google Drive to Myphoner** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-myphoner)
- [ **Mailchimp to Myphoner** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-myphoner)
- [ **ActiveCampaign to Myphoner** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-myphoner)

Questions

## Lokalise and Myphoner, answered

###

### What can start an automation from Lokalise?

Any of Lokalise's 16 triggers in the catalog, including Contributor Added, Contributor Removed, Key Added and Key Comment Added. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Myphoner when something happens in Lokalise?

Any of Myphoner's 14 actions, including Create a list, Create Lead, Update Lead and Find Lead. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Myphoner to Lokalise?

Yes. When something happens in Myphoner, your agent can act in Lokalise too. This page covers both directions: Myphoner's triggers and Lokalise's actions are listed here as well.

###

### Do I have to build a connector for Lokalise or Myphoner?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Lokalise and Myphoner without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
