---
title: "Connect Lokalise and Teachworks - APIANT.ai"
description: "When \"Contributor Added\" fires in Lokalise, your agent runs \"Add payment allocation\" in Teachworks."
canonical: "https://apiant.ai/connect/lokalise-to-teachworks"
---

# Connect Lokalise and Teachworks

When **Contributor Added** fires in [Lokalise](https://apiant.ai/connections/lokalise), your agent runs **Add payment allocation** in [Teachworks](https://apiant.ai/connections/teachworks), or **Lesson Completed** in Teachworks 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 Teachworks **17** triggers Teachworks **28** 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 Teachworks 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 Teachworks can do together

### From Lokalise to Teachworks

- When **Contributor Added** in Lokalise then **Add payment allocation** in Teachworks
- When **Key Added** in Lokalise then **Add profile note** in Teachworks

### From Teachworks to Lokalise

- When **Lesson Completed** in Teachworks then **Create a Task** in Lokalise
- When **New Availability** in Teachworks 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 Teachworks

## Triggers and actions 33 triggers · 54 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

**Lesson Completed**

Triggers when a lesson is marked completed in Teachworks.

- Trigger

**New Availability**

Triggers when a new availability block is added for a teacher or employee.

- Trigger

**New Cost Premium**

Triggers when a new cost premium is created in Teachworks.

- Trigger

**New Employee**

Triggers when a new employee (teacher or staff member) is added in Teachworks.

- Trigger

**New Invoice**

Triggers when a new invoice is created in Teachworks.

- Trigger

**New Lesson**

Triggers when a new lesson is scheduled in Teachworks.

- Trigger

**New Lesson Participant**

Triggers when a student is added to a lesson as a new lesson participant.

- Trigger

**New Location**

Triggers when a new location (or sub-location) is added in Teachworks.

- Trigger

**New Other Event**

Triggers when a new other event (such as an open house or staff meeting) is added to the Teachworks calendar.

- Trigger

**New Package Balance Alert**

Triggers when a customer's package balance is created or recalculated in Teachworks (for example after lessons use package units).

- Trigger

**New Payment**

Triggers when a new payment is recorded in Teachworks.

- Trigger

**New Refund**

Triggers when a new refund is recorded against a customer's payment in Teachworks.

- Trigger

**New Service**

Triggers when a new service is created in Teachworks.

- Trigger

**New Student**

Triggers when a new student is added in Teachworks.

- Trigger

**New Unavailability**

Triggers when a new unavailability (time off) is added for an employee in Teachworks.

- Trigger

**New Wage Payment**

Triggers when a new wage payment to an employee is recorded in Teachworks.

- Trigger

**New Wage Tier**

Triggers when a new wage tier is created in Teachworks.

- Action

**Add location**

Creates a new location in your Teachworks account.

- Action

**Add payment allocation**

Allocates part or all of a payment to an invoice.

- Action

**Add profile note**

Creates a profile note on a customer (family) or student.

- Action

**Add student to lesson**

Adds a student to an existing scheduled lesson and returns the updated lesson with its participants.

- Action

**Add wage payment**

Creates a wage payment for an employee in Teachworks.

- Action

**Complete lesson**

Completes a Teachworks lesson: sets attendance status for the lesson or each participant, and records charges and lesson notes.

- Action

**Create Child Student**

Creates a child student who belongs to a family, with their fees billed to that family.

- Action

**Create Employee**

Creates a new employee (teacher or staff member) in Teachworks.

- Action

**Create Family**

Creates a family customer in Teachworks. Families are billed for the lessons of their child students.

- Action

**Create Independent Student**

Creates an independent student in Teachworks: a directly billed customer together with its associated student record.

- Action

**Create Lesson**

Creates a single lesson in Teachworks with a teacher, service, students, location and start/end date and time.

- Action

**Create Payment**

Creates a payment received from a customer (family or independent student).

- Action

**Find Child Student**

Finds child students (students belonging to a family) matching the name, email, phone or other details you supply.

- Action

**Find Customer**

Finds customers (families and independent students) matching name, email, phone, address, type or status, and returns the first match plus all matches.

- Action

**Find Employee**

Finds employees (teachers and staff) matching the name, email, location, status or subject you give, and returns the first match plus the full list.

- Action

**Find Family**

Finds family customers in Teachworks matching the name, email, phone, address or status you supply, returning the first match and the full list.

- Action

**Find Independent Student (Full Details)**

Finds independent-student customers matching the search criteria and returns their full customer profile, including the student details and custom fields.

- Action

**Find Independent Student (Student Details)**

Finds independent students matching name, email, phone, school, status or other criteria and returns their student details.

- Action

**Find Payment**

Finds payments by customer and/or payment date, returning the first match and the full list of matching payments.

- Action

**Get lesson**

Returns a single lesson, including its time, teacher, service, location and participants.

- Action

**List lessons**

Returns lessons in your Teachworks account, optionally filtered by teacher, student, location, service, status or date range.

- Action

**Update customer**

Updates an existing customer in Teachworks — a family or an independent student — including contact details, status, notification preferences and invoice schedules.

- Action

**Update Customer Custom Field Values**

Sets the values of up to 10 custom profile fields on a Teachworks customer.

- Action

**Update employee**

Updates an existing employee's profile, wage settings and user permissions in Teachworks.

- Action

**Update lesson**

Updates an existing lesson's details, schedule, cost override and participants, and returns the updated lesson.

- Action

**Update payment**

Updates an existing payment's customer, date, amount, description, payment method or Stripe transaction ID.

- Action

**Update student**

Updates an existing child student in Teachworks, such as their name, contact details, status, billing and default teachers.

- Action

**Update Student Custom Field Values**

Sets the values of up to 10 custom profile fields on a Teachworks student.

## 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)
- [ **Teachworks** Teachworks is a simple, easy-to-use system that education companies use for managing teachers, students...](https://apiant.ai/connections/teachworks)

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 Teachworks

- [ **HubSpot to Teachworks** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-teachworks)
- [ **Salesforce to Teachworks** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-teachworks)
- [ **Slack to Teachworks** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-teachworks)
- [ **Google Sheets to Teachworks** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-teachworks)
- [ **Gmail to Teachworks** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-teachworks)
- [ **Google Calendar to Teachworks** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-teachworks)

Questions

## Lokalise and Teachworks, 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 Teachworks when something happens in Lokalise?

Any of Teachworks's 28 actions, including Create Child Student, Create Employee, Create Family and Create Independent Student. Your agent maps the data both ways and tests every scenario before it ships.

###

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

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

###

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

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