Integration
Connect LifterLMS to CORE
When New Course fires in LifterLMS, your agent runs Discover full text links in CORE. 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 CORE to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 CORE
When New Course in LifterLMS
then Discover full text links in CORE
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 CORE
Triggers and actions 10 triggers · 24 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.
- Discover full text links
Finds a link to the full text of a research paper from its DOI, searching CORE and other external sources for the best match.
- Find data providers
Searches CORE's data providers (repositories and journals that supply research papers) and returns the matching providers.
- Find outputs
Searches CORE research outputs (papers and other repository records) by title, author, DOI or a field query and returns the matching outputs.
- Find works
Searches CORE works (deduplicated research papers grouped across repositories) and returns the matching works.
- Get data provider
Returns the details of one CORE data provider (repository or journal), looked up by its CORE id or OpenDOAR id.
- Get journal
Returns a single CORE journal, looked up by its CORE identifier or by ISSN.
- Get output
Returns a single research output (paper) from CORE by its CORE ID, including its metadata, authors, abstract and links.
- Get work
Returns a single research work from CORE, including its title, authors, abstract, DOI, download link and full text.
- List outputs of data provider
Returns the research outputs harvested from a CORE data provider, optionally narrowed by a search query.
- Recommend similar outputs
Returns research outputs in CORE similar to a given paper, identified by its CORE ID or DOI, or described by its title, abstract, authors or free text.
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 CORE
HubSpot to COREHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to COREGoogle Sheets
Gmail to COREGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to COREGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
LifterLMS and CORE, 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 CORE when something happens in LifterLMS?
Any of CORE's 10 actions, including Discover full text links, Find data providers, Find outputs and Find works. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from CORE to LifterLMS?
CORE has no triggers in the catalog today, so automations start in LifterLMS. If you need the other direction, ask: your agent reads CORE's API documentation and adds it.
Do I have to build a connector for LifterLMS or CORE?
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.
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.