Integration
Connect LifterLMS to Mx Technologies
When New Course fires in LifterLMS, your agent runs Add user in Mx Technologies. 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 Mx Technologies 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 can start in Mx Technologies
When New Course in LifterLMS
then Add user in Mx Technologies
When New Course Enrollment in LifterLMS
then Add account in Mx Technologies
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 Mx Technologies
Triggers and actions 10 triggers · 49 actions
Trigger
Course Access CancelledTriggers when a student's enrollment in the selected LifterLMS course is cancelled.
Trigger
Course Access ExpiredTriggers when a student's access to a LifterLMS course expires.
Trigger
Membership Access CancelledTriggers when a student's access to a LifterLMS membership is cancelled.
Trigger
Membership Access ExpiredTriggers when a student's access to the selected LifterLMS membership expires.
Trigger
New CourseTriggers when a new course is created in LifterLMS.
Trigger
New Course EnrollmentTriggers when a student enrolls in the selected LifterLMS course.
Trigger
New MembershipTriggers when a new LifterLMS membership is created.
Trigger
New Membership EnrollmentTriggers when a student is enrolled in the selected LifterLMS membership.
Trigger
New OrderTriggers when a new LifterLMS order is placed on your site, optionally limited to a status, student, product or access plan.
Trigger
New StudentTriggers when a new LifterLMS student (a WordPress user with the student role) is created.
Action
Cancel Course AccessCancels a student's access to a LifterLMS course by setting their course enrollment status to cancelled.
Action
Cancel Membership AccessCancels a student's access to a LifterLMS membership by setting their membership enrollment status to cancelled.
Action
Create a WordPress UserCreates a new WordPress user (a LifterLMS student) on your site, with the student role unless you choose another.
Action
Enroll in a CourseEnrolls a WordPress user (student) in a LifterLMS course and returns the new enrollment.
Action
Enroll in a MembershipEnrolls a WordPress user in a LifterLMS membership and returns the resulting enrollment.
Action
Expire Course AccessSets a student's enrollment in a LifterLMS course to expired and returns the updated enrollment.
Action
Expire Membership AccessSets a student's enrollment in a LifterLMS membership to expired and returns the updated enrollment.
Action
Find CoursesSearches LifterLMS courses by a search term and returns the matching courses.
Action
Get CourseReturns the details of a LifterLMS course, including its title, content, status, enrollment and access dates, and catalog settings.
Action
Get Course EnrollmentReturns a student's enrollment in a LifterLMS course, including its status, dates and what triggered it.
Action
Get OrderReturns the details of a LifterLMS order, including the student, purchased course or membership, access plan, totals and status.
Action
Retrieve a WordPress UserReturns a WordPress user (LifterLMS student) by their user ID, including profile and billing details.
Action
Search WordPress User by EmailFinds the WordPress user (LifterLMS student) whose email address exactly matches the one you supply, and returns their profile.
Action
Search WordPress User by UsernameFinds the WordPress user on your LifterLMS site whose username exactly matches the one you supply, and returns their profile.
Action
Add accountCreates a manual account for an MX user. Manual accounts sit under the Manual Institution member and never aggregate data from a financial institution.
Action
Add budgetCreates a budget for a category on an MX user.
Action
Add categoryCreate a custom category for a user.
Action
Add goalCreate a goal for a user.
Action
Add memberCreate a member (connection between a user and a financial institution) to start aggregation.
Action
Add transactionCreates a manual transaction on a manual account belonging to an MX user.
Action
Add userCreates a new MX user. The returned user guid is what other MX actions (such as Add member) use to identify the user.
Action
Aggregate memberStarts an aggregation for a member, pulling the latest account and transaction data from the connected institution. MX may skip the aggregation if the data was updated recently.
Action
Delete accountDelete a manually created account.
Action
Delete budgetDeletes a budget belonging to an MX user.
Action
Delete categoryDelete a custom category.
Action
Delete goalDelete a goal.
Action
Delete memberDelete a member connection.
Action
Delete userDelete a user.
Action
Get accountRead an account's attributes.
Action
Get budgetRetrieves a specific budget for an MX user.
Action
Get institutionRead an institution's attributes.
Action
Get memberRead a member's attributes and connection status.
Action
Get merchantReturns information about a particular merchant, such as its logo, name, and website.
Action
Get transactionRead a transaction's attributes.
Action
Get userRetrieves the attributes of a specific MX user.
Action
List accountsLists all accounts belonging to an MX user. Returns up to 1000 accounts in one call.
Action
List categoriesLists all categories for an MX user, including default and custom categories.
Action
List goalsLists all goals for an MX user.
Action
List institutionsLists financial institutions available through MX, optionally filtered by name, country and supported product.
Action
List membersList all members belonging to a user.
Action
List merchantsLists merchants in the MX system, optionally filtered by a name substring.
Action
List transactionsList all transactions for a user.
Action
Update accountUpdates an account belonging to a member. Manual accounts can have every field updated; aggregated accounts only accept changes to Is Business, Is Hidden and Metadata.
Action
Update budgetUpdate a specific budget.
Action
Update categoryUpdate a custom category.
Action
Update goalUpdates an existing savings or payoff goal for an MX user. Only the fields you fill in are changed.
Action
Update memberUpdates a member's credentials, id, metadata, background aggregation setting or use cases. At least one value to update must be supplied.
Action
Update transactionUpdate a transaction's category, description, or other editable attributes.
Action
Update userUpdate a user's attributes.
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 Mx Technologies
HubSpot to Mx TechnologiesHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Mx TechnologiesSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Mx TechnologiesSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Mx TechnologiesGoogle Sheets
Gmail to Mx TechnologiesGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Mx TechnologiesGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
LifterLMS and Mx Technologies, 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 Mx Technologies when something happens in LifterLMS?
Any of Mx Technologies's 35 actions, including Update account, Update budget, Update category and Update goal. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mx Technologies to LifterLMS?
Mx Technologies has no triggers in the catalog today, so automations start in LifterLMS. If you need the other direction, ask: your agent reads Mx Technologies's API documentation and adds it.
Do I have to build a connector for LifterLMS or Mx Technologies?
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 Mx Technologies 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.