---
title: "Connect Kit and Lokalise - APIANT.ai"
description: "When \"New Form Subscriber\" fires in Kit, your agent runs \"Create a Task\" in Lokalise, or \"Contributor Added\" in Lokalise to \"Add Subscriber to Form\" in Kit."
canonical: "https://apiant.ai/connect/kit-to-lokalise"
---

# Connect Kit and Lokalise

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

Kit **7** triggers Kit **7** 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 Kit 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 Kit and Lokalise can do together

### From Kit to Lokalise

- When **New Form Subscriber** in Kit then **Create a Task** in Lokalise
- When **New Purchase** in Kit then **Create Comment** in Lokalise

### From Lokalise to Kit

- When **Contributor Added** in Lokalise then **Add Subscriber to Form** in Kit
- When **Key Added** in Lokalise then **Add Tag to Subscriber** in Kit

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

## Triggers and actions 23 triggers · 33 actions

- Trigger

**New Form Subscriber**

Triggers when a subscription occurs on a specific form.

- Trigger

**New Purchase**

Triggers when a new purchase is added to your account.

- Trigger

**New Sequence Subscriber**

Triggers when a subscriber is added to a sequence.

- Trigger

**New Subscriber**

Triggers when a new subscriber is confirmed within your account (has completed any applicable double opt-ins).

- Trigger

**New Unsubscribe**

Triggers when a subscriber unsubscribes from your emails.

- Trigger

**Subscriber Added to Tag**

Triggers when a specific tag is added to a subscriber.

- Trigger

**Tag Removed From Subscriber**

Triggers when a specific tag is removed from a subscriber.

- Action

**Add Subscriber to Form**

Subscribe someone to a specific form.

- Action

**Add Tag to Subscriber**

Add a subscriber to a specific tag.

- Action

**Create or Update Subscriber**

Creates a Kit subscriber, or updates the first name and custom fields of an existing subscriber with the same email address. Returns the subscriber.

- Action

**Find Subscriber**

Finds an existing confirmed subscriber by email.

- Action

**Get Subscriber**

Returns one Kit subscriber by ID, with their name, email address, state and custom field values.

- Action

**List Tags for Subscriber**

Lists the tags on a Kit subscriber, with each tag's ID, name and the date it was applied.

- Action

**Remove Tag From Subscriber**

Remove a specific tag from a subscriber if they have it.

- 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

- [ **Kit** Kit is an email marketing platform for professional bloggers.](https://apiant.ai/connections/kit)
- [ **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 Kit

- [ **Kit to API Snap** Free utility API platform. QR codes, screenshots, PDFs, image resize, hashing, and more](https://apiant.ai/connect/kit-to-api-snap)
- [ **Kit to Clerk** Clerk is a user authentication and management platform that lets developers add sign-in, profiles, and...](https://apiant.ai/connect/kit-to-clerk)
- [ **Kit to PostLake** One API to publish, schedule, and read analytics across every major social network](https://apiant.ai/connect/kit-to-postlake)
- [ **Kit to Synchroteam** Synchroteam is a Cloud-based Field Service Management application](https://apiant.ai/connect/kit-to-synchroteam)
- [ **Kit to Wikimedia** This API provides cacheable and straightforward access to Wikimedia content and data, in machine-readable...](https://apiant.ai/connect/kit-to-wikimedia)
- [ **Kit to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/kit-to-hubspot)

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

## Kit and Lokalise, answered

###

### What can start an automation from Kit?

Any of Kit's 7 triggers in the catalog, including New Form Subscriber, New Purchase, New Sequence Subscriber and New Subscriber. Describe the moment in plain language and your agent picks the right one.

###

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

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 Kit?

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

###

### Do I have to build a connector for Kit 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 Kit 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.
