--- title: "Connect incident.io and LifterLMS - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Create a WordPress User\" in LifterLMS." canonical: "https://apiant.ai/connect/incident-io-to-lifterlms" --- # Connect incident.io and LifterLMS When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Create a WordPress User** in [LifterLMS](https://apiant.ai/connections/lifterlms), or **New Course** in LifterLMS to **Find Users On-Call** in incident.io. Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions LifterLMS **10** triggers LifterLMS **14** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want incident.io and LifterLMS 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 incident.io and LifterLMS can do together ### From incident.io to LifterLMS - When **New Incident** in incident.io then **Create a WordPress User** in LifterLMS - When **New Incident** in incident.io then **Enroll in a Course** in LifterLMS ### From LifterLMS to incident.io - When **New Course** in LifterLMS then **Find Users On-Call** in incident.io - When **New Course Enrollment** in LifterLMS then **Add follow-up** in incident.io 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 incident.io and LifterLMS ## Triggers and actions 11 triggers · 24 actions - Trigger **New Incident** Triggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode. - Action **Add follow-up** Creates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels. - Action **Add incident update** Shares an update on an incident: a message, a move to a new status, a new severity, or any combination. - Action **Create Incident** Creates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields. - Action **Find Users On-Call** Finds the users on-call for a schedule over a window of time (or right now), returning each effective shift with its user after overrides are applied. - Action **Get incident** Returns a single incident, including its status, severity, role assignments, timestamps and custom field values. - Action **Get Schedule** Returns a single on-call schedule, including its rotations, time zone and current shifts. - Action **List actions** Returns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date. - Action **List schedules** Returns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift. - Action **List severities** Returns every incident severity configured for your incident.io organisation. - Action **List users** Returns the users in your incident.io account, optionally filtered by email address or Slack user ID. - 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. ## Each app on its own - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) - [ **LifterLMS** LifterLMS is a WordPress-based LMS solution that makes it easy to create, sell, and protect engaging online...](https://apiant.ai/connections/lifterlms) Reviews ## What our customers say ## More from incident.io - [ **incident.io to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/incident-io-to-salesforce) - [ **incident.io to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/incident-io-to-slack) - [ **incident.io to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/incident-io-to-mailchimp) - [ **incident.io to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/incident-io-to-stripe) - [ **incident.io to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/incident-io-to-shopify) - [ **incident.io to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/incident-io-to-quickbooks-online) ## More into LifterLMS - [ **HubSpot to LifterLMS** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-lifterlms) - [ **Google Sheets to LifterLMS** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-lifterlms) - [ **Gmail to LifterLMS** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-lifterlms) - [ **Google Calendar to LifterLMS** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-lifterlms) - [ **Google Drive to LifterLMS** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-lifterlms) - [ **ActiveCampaign to LifterLMS** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-lifterlms) Questions ## incident.io and LifterLMS, answered ### ### What can start an automation from incident.io? Any of incident.io's 1 trigger in the catalog, including New Incident. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in LifterLMS when something happens in incident.io? Any of LifterLMS's 14 actions, including Create a WordPress User, Enroll in a Course, Enroll in a Membership and Expire Course Access. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from LifterLMS to incident.io? Yes. When something happens in LifterLMS, your agent can act in incident.io too. This page covers both directions: LifterLMS's triggers and incident.io's actions are listed here as well. ### ### Do I have to build a connector for incident.io or LifterLMS? 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 incident.io and LifterLMS 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.