---
title: "Connect Copper and Lokalise - APIANT.ai"
description: "When \"New Activity\" fires in Copper, your agent runs \"Create a Task\" in Lokalise, or \"Contributor Added\" in Lokalise to \"Create Lead\" in Copper."
canonical: "https://apiant.ai/connect/copper-to-lokalise"
---

# Connect Copper and Lokalise

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

Copper **17** triggers Copper **22** actions Lokalise **16** triggers Lokalise **26** actions

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

## What do you want Copper and Lokalise 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 Copper and Lokalise can do together

### From Copper to Lokalise

- When **New Activity** in Copper then **Create a Task** in Lokalise
- When **New Company** in Copper then **Create Comment** in Lokalise

### From Lokalise to Copper

- When **Contributor Added** in Lokalise then **Create Lead** in Copper
- When **Key Added** in Lokalise then **Create Task** in Copper

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 Copper and Lokalise

## Triggers and actions 33 triggers · 48 actions

- Trigger

**New Activity**

Triggers when a new activity is created.

- Trigger

**New Company**

Triggers when a new Company is created in Copper.

- Trigger

**New Lead**

Triggers when a Lead is created in Copper.

- Trigger

**New Opportunity**

Triggers when an Opportunity is created in Copper.

- Trigger

**New Person**

Triggers when a new Person is created in Copper.

- Trigger

**New Project**

Triggers when a new Project is created in Copper.

- Trigger

**New Task**

Triggers when a new Task is created in Copper.

- Trigger

**Updated Company**

Triggers when a Person's Company is changed.

- Trigger

**Updated Contact Type**

Triggers when a Person's Contact Type is changed.

- Trigger

**Updated Lead**

Triggers when a Lead is changed.

- Trigger

**Updated Lead Status**

Triggers when a Lead's status is changed.

- Trigger

**Updated Opportunity**

Triggers when an Opportunity is changed.

- Trigger

**Updated Opportunity Stage**

Triggers when an Opportunity's stage is changed.

- Trigger

**Updated Opportunity Status**

Triggers when an Opportunity's status is changed.

- Trigger

**Updated Person**

Triggers when a Person is changed.

- Trigger

**Updated Project**

Triggers when a Project is changed.

- Trigger

**Updated Task**

Triggers when a Task is changed.

- Action

**Associate to Project**

This Action allows you to relate an existing Project to and existing CRM object; both objects have to exist before you run this Action. This Action expects two ID's for input: the ID of the CRM record you want to relate to and the Project ID you want to relate it with. This Action was designed to be used in multi-step Zaps, where you already have a Project ID and an related record ID (e.g. a Person) from previous steps.

- Action

**Create Activity**

Logs a new Activity on a Person, Company, Opportunity, or Lead.

- Action

**Create Company**

Creates a new Company.

- Action

**Create Lead**

Creates a new Lead.

- Action

**Create Opportunity**

Creates a new Opportunity.

- Action

**Create Person**

Creates a new Person.

- Action

**Create Project**

Creates a new Project.

- Action

**Create Task**

Creates a new Task.

- Action

**Create/Update Company**

Creates or Updates a Company depending on the match criteria.

- Action

**Create/Update Lead**

Creates or Updates a Lead depending on the match criteria.

- Action

**Create/Update Opportunity**

Creates or Updates an Opportunity based off of a match criteria.

- Action

**Create/Update Person**

Creates or Updates a Person depending on the match criteria.

- Action

**Create/Update Project**

Creates or Updates a Project depending on the match criteria.

- Action

**Search for a Company**

Searches for an existing company in Copper.

- Action

**Search for an Activity**

Searches for an existing activity in Copper.

- Action

**Search for a Opportunity**

Searches for an existing opportunity in Copper.

- Action

**Search for a Person**

Searches for an existing person in Copper.

- Action

**Search for a Project**

Searches for an existing project in Copper.

- Action

**Update Company**

Updates a Company depending on the match criteria.

- Action

**Update Opportunity**

Updates an Opportunity based off of a match criteria.

- Action

**Update Person**

Updates a Person depending on the match criteria.

- Action

**Update Project**

Updates a Project depending on the match criteria.

- 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.

## Each app on its own

- [ **Copper** Copper is a Recommended for Google Workspace CRM that improves productivity and increases visibility across...](https://apiant.ai/connections/copper)
- [ **Lokalise** Lokalise is a translation management tool that lets you structure and automate workflows while encouraging...](https://apiant.ai/connections/lokalise)

Reviews

## What our customers say

## More from Copper

- [ **Copper to LeadSimple** LeadSimple is the CRM that property management and real estate companies use to scale and grow.](https://apiant.ai/connect/copper-to-leadsimple)
- [ **Copper to Nvidia** API platform for deploying GPU-accelerated AI models, including inference microservices and a container...](https://apiant.ai/connect/copper-to-nvidia)
- [ **Copper to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/copper-to-hubspot)
- [ **Copper to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/copper-to-salesforce)
- [ **Copper to Google Sheets** Google Sheets](https://apiant.ai/connect/copper-to-google-sheets)
- [ **Copper to Google Drive** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/copper-to-google-drive)

## More into Lokalise

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

Questions

## Copper and Lokalise, answered

###

### What can start an automation from Copper?

Any of Copper's 17 triggers in the catalog, including New Activity, New Company, New Lead and New Opportunity. Describe the moment in plain language and your agent picks the right one.

###

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

Any of Lokalise's 26 actions, including Create a Key, Create a Task, Create Comment and Create Project. Your agent maps the data both ways and tests every scenario before it ships.

###

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

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

###

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

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 Copper and Lokalise 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.
