--- title: "Connect LifterLMS and WeTravel - APIANT.ai" description: "When \"New Course\" fires in LifterLMS, your agent runs \"Get order\" in WeTravel, or \"Lead Updated\" in WeTravel to \"Create a WordPress User\" in LifterLMS." canonical: "https://apiant.ai/connect/lifterlms-to-wetravel" --- # Connect LifterLMS and WeTravel When **New Course** fires in [LifterLMS](https://apiant.ai/connections/lifterlms), your agent runs **Get order** in [WeTravel](https://apiant.ai/connections/wetravel), or **Lead Updated** in WeTravel to **Create a WordPress User** in LifterLMS. Describe the whole flow and it is built, tested on every scenario and kept running. LifterLMS **10** triggers LifterLMS **14** actions WeTravel **3** triggers WeTravel **10** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want LifterLMS and WeTravel 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 LifterLMS and WeTravel can do together ### From LifterLMS to WeTravel - When **New Course** in LifterLMS then **Get order** in WeTravel - When **New Course Enrollment** in LifterLMS then **List leads** in WeTravel ### From WeTravel to LifterLMS - When **Lead Updated** in WeTravel then **Create a WordPress User** in LifterLMS - When **New Lead** in WeTravel then **Enroll in a Course** in 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 WeTravel ## Triggers and actions 13 triggers · 24 actions - Trigger **Course Access Cancelled** Triggers when a student's enrollment in the selected LifterLMS course is cancelled. - Trigger **Course Access Expired** Triggers when a student's access to a LifterLMS course expires. - Trigger **Membership Access Cancelled** Triggers when a student's access to a LifterLMS membership is cancelled. - Trigger **Membership Access Expired** Triggers when a student's access to the selected LifterLMS membership expires. - Trigger **New Course** Triggers when a new course is created in LifterLMS. - Trigger **New Course Enrollment** Triggers when a student enrolls in the selected LifterLMS course. - Trigger **New Membership** Triggers when a new LifterLMS membership is created. - Trigger **New Membership Enrollment** Triggers when a student is enrolled in the selected LifterLMS membership. - Trigger **New Order** Triggers when a new LifterLMS order is placed on your site, optionally limited to a status, student, product or access plan. - Trigger **New Student** Triggers when a new LifterLMS student (a WordPress user with the student role) is created. - Action **Cancel Course Access** Cancels a student's access to a LifterLMS course by setting their course enrollment status to cancelled. - Action **Cancel Membership Access** Cancels a student's access to a LifterLMS membership by setting their membership enrollment status to cancelled. - Action **Create a WordPress User** Creates a new WordPress user (a LifterLMS student) on your site, with the student role unless you choose another. - Action **Enroll in a Course** Enrolls a WordPress user (student) in a LifterLMS course and returns the new enrollment. - Action **Enroll in a Membership** Enrolls a WordPress user in a LifterLMS membership and returns the resulting enrollment. - Action **Expire Course Access** Sets a student's enrollment in a LifterLMS course to expired and returns the updated enrollment. - Action **Expire Membership Access** Sets a student's enrollment in a LifterLMS membership to expired and returns the updated enrollment. - Action **Find Courses** Searches LifterLMS courses by a search term and returns the matching courses. - Action **Get Course** Returns the details of a LifterLMS course, including its title, content, status, enrollment and access dates, and catalog settings. - Action **Get Course Enrollment** Returns a student's enrollment in a LifterLMS course, including its status, dates and what triggered it. - Action **Get Order** Returns the details of a LifterLMS order, including the student, purchased course or membership, access plan, totals and status. - Action **Retrieve a WordPress User** Returns a WordPress user (LifterLMS student) by their user ID, including profile and billing details. - Action **Search WordPress User by Email** Finds the WordPress user (LifterLMS student) whose email address exactly matches the one you supply, and returns their profile. - Action **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. - Trigger **Lead Updated** Triggers when a WeTravel lead is created or updated (for example, when the person requests again or books). - Trigger **New Lead** Triggers when a new lead is captured for one of your WeTravel trips. - Trigger **Transaction Updated** Triggers when a WeTravel transaction is created or updated, such as a payment, refund or payout changing status. - Action **Add payment link** Creates a WeTravel payment link for a trip with its dates, currency, fee handling and price, optionally with a deposit and installment payment plan. - Action **Add trip** Creates a draft trip in WeTravel, which can then be built out and published. - Action **Get order** Returns a single trip order (booking), including amounts paid and due, packages and add-ons, participants and installments. - Action **Get payment link** Returns a WeTravel payment link by its UUID, including its trip and pricing details. - Action **List leads** Returns the leads (trip inquiries) in your WeTravel account, optionally filtered by trip, booking status, lead type and request date. - Action **List orders** Returns the orders (bookings) placed on a trip, with amounts paid and due, buyer and booked packages. - Action **List transactions** Returns the transactions (payments and refunds) on your WeTravel account, optionally filtered. - Action **List trips** Returns all trips in your WeTravel account, with their titles, destinations, dates and listing status. - Action **Publish trip** Publishes a draft trip so its booking page goes live on WeTravel, and returns the published trip. - Action **Update trip** Updates an existing draft trip's details, such as title, dates, group size, pricing currency and booking settings. Only the fields you fill in are changed. ## Each app on its own - [ **LifterLMS** LifterLMS is a WordPress-based LMS solution that makes it easy to create, sell, and protect engaging online...](https://apiant.ai/connections/lifterlms) - [ **WeTravel** WeTravel is an all-in-one operating system for multi-day travel businesses—build itineraries, manage...](https://apiant.ai/connections/wetravel) Reviews ## What our customers say ## More from LifterLMS - [ **LifterLMS to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/lifterlms-to-salesforce) - [ **LifterLMS to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/lifterlms-to-slack) - [ **LifterLMS to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/lifterlms-to-mailchimp) - [ **LifterLMS to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/lifterlms-to-stripe) - [ **LifterLMS to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/lifterlms-to-shopify) - [ **LifterLMS to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/lifterlms-to-quickbooks-online) ## More into WeTravel - [ **HubSpot to WeTravel** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-wetravel) - [ **Salesforce to WeTravel** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-wetravel) - [ **Slack to WeTravel** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-wetravel) - [ **Google Sheets to WeTravel** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-wetravel) - [ **Gmail to WeTravel** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-wetravel) - [ **Google Calendar to WeTravel** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-wetravel) Questions ## LifterLMS and WeTravel, 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 WeTravel when something happens in LifterLMS? Any of WeTravel's 10 actions, including Update trip, Add payment link, Add trip and Get order. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from WeTravel to LifterLMS? Yes. When something happens in WeTravel, your agent can act in LifterLMS too. This page covers both directions: WeTravel's triggers and LifterLMS's actions are listed here as well. ### ### Do I have to build a connector for LifterLMS or WeTravel? 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 WeTravel 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.