--- title: "Connect LearnWorlds and Lokalise - APIANT.ai" description: "When \"Assessment Completed\" fires in LearnWorlds, your agent runs \"Create a Task\" in Lokalise." canonical: "https://apiant.ai/connect/learnworlds-to-lokalise" --- # Connect LearnWorlds and Lokalise When **Assessment Completed** fires in [LearnWorlds](https://apiant.ai/connections/learnworlds), your agent runs **Create a Task** in [Lokalise](https://apiant.ai/connections/lokalise), or **Contributor Added** in Lokalise to **Add Tags to User** in LearnWorlds. Describe the whole flow and it is built, tested on every scenario and kept running. LearnWorlds **15** triggers LearnWorlds **15** 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 LearnWorlds 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 LearnWorlds and Lokalise can do together ### From LearnWorlds to Lokalise - When **Assessment Completed** in LearnWorlds then **Create a Task** in Lokalise - When **Course Completed** in LearnWorlds then **Create Comment** in Lokalise ### From Lokalise to LearnWorlds - When **Contributor Added** in Lokalise then **Add Tags to User** in LearnWorlds - When **Key Added** in Lokalise then **Create and Enroll User (Legacy)** in LearnWorlds 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 LearnWorlds and Lokalise ## Triggers and actions 31 triggers · 41 actions - Trigger **Assessment Completed** Triggers when a learner submits a completed assessment, returning their grade, pass/fail result and answers. - Trigger **Course Completed** Triggers when a user completes a course in your LearnWorlds school. - Trigger **New Certificate** Triggers when a certificate is issued to a learner for a course (or for a specific user). - Trigger **New Certificate (Legacy)** Triggers when a new certificate is issued for a course or a user in your LearnWorlds school. - Trigger **New Enrollment Purchase (Legacy)** Triggers when a new enrollment purchase (payment for a course, bundle or subscription) is recorded in your LearnWorlds school. - Trigger **New Form Submission** Triggers when a learner submits a response to the chosen LearnWorlds form. - Trigger **New Lead** Triggers when a new lead submits their email in one of your school's lead capture forms. - Trigger **New Lead (Legacy)** Triggers when a new lead submits their email in one of your school's lead capture forms. - Trigger **New User** Triggers when a new user registers in your LearnWorlds school. - Trigger **New User (Legacy)** Triggers when a new user signs up or is created in your LearnWorlds school. - Trigger **Payment Created** Triggers when a new payment is made in your LearnWorlds school. - Trigger **Payment Failed** Triggers when a payment fails in your LearnWorlds school, returning the failed-payment event with the user and its details. - Trigger **Subscription or Payment Plan Canceled** Triggers when a user's subscription or payment plan becomes inactive (canceled or expired), newest users first. - Trigger **Subscription Updated** Triggers when a user subscription is created or changes, such as a new status, plan or expiry date. - Trigger **User Updated** Triggers when a user in your LearnWorlds school is changed (profile fields, tags, role, suspension and so on). Checks the 200 most recently registered users. - Action **Add Tags to User** Adds one or more tags to a LearnWorlds user and returns the updated user. - Action **Create and Enroll User (Legacy)** Creates a new LearnWorlds user and enrolls them in a course, bundle or subscription in one step. - Action **Create User** Creates a new user in your LearnWorlds school and returns the created user. - Action **Create User (Legacy)** Creates a new user in your LearnWorlds school with optional sign-up fields, tags and UTM values. - Action **Enroll User in Product** Enrolls a user in a course, learning program (bundle) or subscription. - Action **Enroll User in Product (Legacy)** Enrolls an existing user in a course, bundle or subscription. - Action **Find a User** Finds a user in your LearnWorlds school by email address and returns their full record, including sign-up and custom fields. - Action **Get course** Returns a course's details, including its title, description, prices, access type and author. - Action **Get user** Returns a LearnWorlds user by ID or email, including sign-up fields, tags, UTMs and role. - Action **List bundles** Returns all bundles in your LearnWorlds school, most recently created first. - Action **List payments** Returns the school's payments, most recent first, optionally filtered by user, product, product type, affiliate or creation date. - Action **List users** Returns the users of your LearnWorlds school, newest first, optionally filtered by status, role, tags or registration date. - Action **Remove Tags From User** Removes one or more tags from a LearnWorlds user and returns the updated user. - Action **Unenroll User From Product** Removes a user's enrollment from a course, bundle or subscription in your LearnWorlds school. - Action **Update user** Updates a LearnWorlds user's email, username, marketing consent, admin status, profile fields, tags and UTM values, and returns the updated user. - 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 - [ **LearnWorlds** LearnWorlds is a premium learning platform via which you sell online courses under your own website.](https://apiant.ai/connections/learnworlds) - [ **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 LearnWorlds - [ **LearnWorlds to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/learnworlds-to-salesforce) - [ **LearnWorlds to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/learnworlds-to-slack) - [ **LearnWorlds to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/learnworlds-to-mailchimp) - [ **LearnWorlds to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/learnworlds-to-stripe) - [ **LearnWorlds to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/learnworlds-to-shopify) - [ **LearnWorlds to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/learnworlds-to-quickbooks-online) ## 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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](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 ## LearnWorlds and Lokalise, answered ### ### What can start an automation from LearnWorlds? Any of LearnWorlds's 15 triggers in the catalog, including Assessment Completed, Course Completed, New Certificate and New Certificate (Legacy). Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Lokalise when something happens in LearnWorlds? 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 LearnWorlds? Yes. When something happens in Lokalise, your agent can act in LearnWorlds too. This page covers both directions: Lokalise's triggers and LearnWorlds's actions are listed here as well. ### ### Do I have to build a connector for LearnWorlds 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 LearnWorlds 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.