Integration
Connect LifterLMS and Lokalise
When New Course fires in LifterLMS, your agent runs Create a Task in Lokalise, or Contributor Added in Lokalise to Create a WordPress User in LifterLMS. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want LifterLMS and Lokalise to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What LifterLMS and Lokalise can do together
From LifterLMS to Lokalise
When New Course in LifterLMS
then Create a Task in Lokalise
From Lokalise to LifterLMS
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 LifterLMS and Lokalise
Triggers and actions 26 triggers · 40 actions
- Course Access Cancelled
Triggers when a student's enrollment in the selected LifterLMS course is cancelled.
- Course Access Expired
Triggers when a student's access to a LifterLMS course expires.
- Membership Access Cancelled
Triggers when a student's access to a LifterLMS membership is cancelled.
- Membership Access Expired
Triggers when a student's access to the selected LifterLMS membership expires.
- New Course
Triggers when a new course is created in LifterLMS.
- New Course Enrollment
Triggers when a student enrolls in the selected LifterLMS course.
- New Membership
Triggers when a new LifterLMS membership is created.
- New Membership Enrollment
Triggers when a student is enrolled in the selected LifterLMS membership.
- New Order
Triggers when a new LifterLMS order is placed on your site, optionally limited to a status, student, product or access plan.
- New Student
Triggers when a new LifterLMS student (a WordPress user with the student role) is created.
- Cancel Course Access
Cancels a student's access to a LifterLMS course by setting their course enrollment status to cancelled.
- Cancel Membership Access
Cancels a student's access to a LifterLMS membership by setting their membership enrollment status to cancelled.
- Create a WordPress User
Creates a new WordPress user (a LifterLMS student) on your site, with the student role unless you choose another.
- Enroll in a Course
Enrolls a WordPress user (student) in a LifterLMS course and returns the new enrollment.
- Enroll in a Membership
Enrolls a WordPress user in a LifterLMS membership and returns the resulting enrollment.
- Expire Course Access
Sets a student's enrollment in a LifterLMS course to expired and returns the updated enrollment.
- Expire Membership Access
Sets a student's enrollment in a LifterLMS membership to expired and returns the updated enrollment.
- Find Courses
Searches LifterLMS courses by a search term and returns the matching courses.
- Get Course
Returns the details of a LifterLMS course, including its title, content, status, enrollment and access dates, and catalog settings.
- Get Course Enrollment
Returns a student's enrollment in a LifterLMS course, including its status, dates and what triggered it.
- Get Order
Returns the details of a LifterLMS order, including the student, purchased course or membership, access plan, totals and status.
- Retrieve a WordPress User
Returns a WordPress user (LifterLMS student) by their user ID, including profile and billing details.
- Search WordPress User by Email
Finds the WordPress user (LifterLMS student) whose email address exactly matches the one you supply, and returns their profile.
- Search WordPress User by Username
Finds the WordPress user on your LifterLMS site whose username exactly matches the one you supply, and returns their profile.
- Contributor Added
Triggers when a new contributor is added to a Lokalise project.
- Contributor Removed
Triggers when a contributor is removed from the selected Lokalise project.
- 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.
- Key Comment Added
Triggers when someone adds a comment to a translation key in a Lokalise project.
- Key Modified
Triggers when a translation key is modified in a Lokalise project, either individually or in bulk (renames, tag changes, file assignments, hiding).
- 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.
- Language Added
Triggers when one or more languages are added to a Lokalise project, firing once for each language added.
- Language Removed
Triggers when a language is removed from a Lokalise project.
- Poll Tasks
Triggers when a new task is created in a Lokalise project.
- Project Exported
Triggers when translation files are downloaded (exported) from a Lokalise project.
- Project Imported
Triggers when a translation file is uploaded to a Lokalise project. Fires once per uploaded file.
- Project Snapshot
Triggers when a snapshot is taken of the selected Lokalise project.
- Task Created
Triggers when a new translation or review task is created in a Lokalise project.
- Task Deleted
Triggers when a task is deleted in a Lokalise project.
- Translation Reviewed
Triggers when a translation is marked or unmarked as reviewed in a Lokalise project, individually or in bulk.
- 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.
- Add Contributor
Adds a contributor to a Lokalise project, inviting them by email with the chosen languages and permissions.
- Add Languages
Adds one or more languages to a Lokalise project, optionally overriding each language's code, name and plural forms.
- 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.
- Create a Task
Creates a translation, review or automatic-translation task in a Lokalise project for the chosen keys and languages.
- Create Comment
Adds a comment to a translation key in a Lokalise project.
- Create Project
Creates a new Lokalise project in your team, optionally with its languages, base language and project type. Returns the created project.
- Create Snapshot
Creates a snapshot of a Lokalise project, saving its current state so it can be restored later.
- Delete a Key
Deletes a key, with its translations, from a Lokalise project.
- Delete a Language
Removes a language from a Lokalise project.
- Delete a Task
Deletes a task from a Lokalise project.
- Download Files
Exports a Lokalise project's translation files as a .zip bundle and returns the download URL of the bundle.
- List All Orders
Returns all translation orders placed under a Lokalise team.
- List All Tasks
Returns the tasks in a Lokalise project, optionally filtered by title or status.
- 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.
- List Project Languages
Returns the languages set up in a Lokalise project, with each language's code, name, direction and plural forms.
- List Snapshots
Returns the snapshots saved for a Lokalise project, with each snapshot's title and creation details.
- Remove Contributor
Removes a contributor from a Lokalise project.
- Retrieve a Comment
Returns a single comment left on a key in a Lokalise project, including its text, author and when it was added.
- Retrieve a Contributor
Returns a contributor of a Lokalise project, including their email, name, role flags, languages and permissions.
- Retrieve a Key
Returns one translation key from a Lokalise project, including its names, description, platforms, tags, comments, screenshots and translations.
- Retrieve a Task
Returns a Lokalise task, including its status, progress, due date and the languages and assignees it covers.
- Retrieve Project
Returns a Lokalise project's details, including its name, type, base language, settings and translation statistics.
- 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.
- Update a Translation
Updates the text and review flags of a translation in a Lokalise project.
- Update Language
Updates a language in a Lokalise project, changing its code, name or plural forms.
- 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.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from LifterLMS
LifterLMS to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
LifterLMS to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
LifterLMS to MailchimpMailchimp marketing automation and email platform.
LifterLMS to StripeStripe is a payment processing platform for online businesses.
LifterLMS to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
LifterLMS to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Lokalise
HubSpot to LokaliseHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LokaliseGoogle Sheets
Gmail to LokaliseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LokaliseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to LokaliseGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to LokaliseActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
LifterLMS and Lokalise, answered
What can start an automation from LifterLMS?
Any of LifterLMS's 10 triggers in the catalog, including New Course, New Course Enrollment, New Membership and New Membership Enrollment. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Lokalise when something happens in LifterLMS?
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 LifterLMS?
Yes. When something happens in Lokalise, your agent can act in LifterLMS too. This page covers both directions: Lokalise's triggers and LifterLMS's actions are listed here as well.
Do I have to build a connector for LifterLMS 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 LifterLMS 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.