Integration
Connect BotStar and TalentLMS
When New CMS Entity Item fires in BotStar, your agent runs Add User in TalentLMS, or New Branch in TalentLMS to Send Message in BotStar. 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 BotStar and TalentLMS 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 BotStar and TalentLMS can do together
From BotStar to TalentLMS
When New CMS Entity Item in BotStar
then Add User in TalentLMS
When New CMS Entity Item in BotStar
then Add User to Branch in TalentLMS
From TalentLMS to BotStar
When New Branch in TalentLMS
then Send Message in BotStar
When New Category in TalentLMS
then Create CMS Entity Item in BotStar
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 BotStar and TalentLMS
Triggers and actions 8 triggers · 34 actions
Trigger
New CMS Entity ItemTriggers when a new item is added to a CMS entity.
Action
Create Bot AttributeCreates a bot attribute (a bot-wide variable) on a bot.
Action
Create CMS Entity ItemCreates an item in a CMS entity.
Action
Create Custom User AttributeCreates a custom user attribute that every user of the bot can carry.
Action
Delete Bot AttributeDeletes a bot attribute from a bot.
Action
Delete CMS Entity ItemDeletes an item from a CMS entity.
Action
Get BotReturns one BotStar bot by its ID.
Action
Get CMS EntityReturns one CMS entity with its field definitions.
Action
Get CMS Entity ItemReturns one CMS entity item with its field values.
Action
Get UserReturns a bot user's profile, tags and custom attributes.
Action
List Bot AttributesReturns all bot attributes of a bot, with their names, types and values.
Action
List BotsReturns the bots in your BotStar account, each with its ID, name and team name.
Action
List CMS EntitiesReturns the CMS entities of a bot with their fields.
Action
List CMS Entity ItemsReturns the items of a CMS entity, optionally filtered by name or status.
Action
Publish BotPublishes a bot's draft changes to live.
Action
Send MessageSends a text message to a Facebook Messenger user of your bot.
Action
Update Bot AttributeUpdates a bot attribute's name, description or value.
Action
Update CMS Entity ItemUpdates an item in a CMS entity.
Action
Update User AttributesUpdates a bot user's standard and custom attributes.
Trigger
Custom FieldsTriggers when a new custom user field is created in your TalentLMS portal.
Trigger
New BranchTriggers when a new branch is added to your TalentLMS portal.
Trigger
New CategoryTriggers when a new course category is created in your TalentLMS portal.
Trigger
New CourseTriggers when a new course is added to your TalentLMS portal.
Trigger
New EventTriggers when a new timeline event of the chosen type (e.g. a user completing a course) occurs in your TalentLMS portal.
Trigger
New GroupTriggers when a new group is added to your TalentLMS portal.
Trigger
New UserTriggers when a new user is added to your TalentLMS portal.
Action
Add branchCreates a branch in the TalentLMS portal.
Action
Add CourseCreates a course in the TalentLMS portal.
Action
Add groupCreates a user group in the TalentLMS portal.
Action
Add UserCreates a user in the TalentLMS portal.
Action
Add User to BranchAdds a TalentLMS user to a branch.
Action
Add User to CourseEnrolls a TalentLMS user in a course as a learner or instructor.
Action
Add User to GroupAdds a user to a group.
Action
Delete courseDeletes a course.
Action
Delete userDeletes a user.
Action
Find UserFinds a TalentLMS user by email address and returns their details.
Action
Get courseReturns a TalentLMS course by its ID, including its enrolled users, units, rules, prerequisites and custom course field values.
Action
Get user status in courseReturns a user's progress in a course: role, enrollment and completion dates, completion status and percentage, time spent, and per-unit status and scores.
Action
List coursesReturns every course in your TalentLMS account.
Action
List usersReturns every user in your TalentLMS account with their profile details.
Action
Remove user from courseUn-enrolls a user from a course in TalentLMS.
Action
Remove User From GroupRemoves a TalentLMS user from a group.
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 BotStar
BotStar to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
BotStar to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
BotStar to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
BotStar to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
BotStar to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
BotStar to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into TalentLMS
HubSpot to TalentLMSHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TalentLMSSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TalentLMSSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TalentLMSGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TalentLMSGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TalentLMSGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
BotStar and TalentLMS, answered
What can start an automation from BotStar?
Any of BotStar's 1 trigger in the catalog, including New CMS Entity Item. Describe the moment in plain language and your agent picks the right one.
What can your agent do in TalentLMS when something happens in BotStar?
Any of TalentLMS's 16 actions, including Add branch, Add Course, Add group and Add User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from TalentLMS to BotStar?
Yes. When something happens in TalentLMS, your agent can act in BotStar too. This page covers both directions: TalentLMS's triggers and BotStar's actions are listed here as well.
Do I have to build a connector for BotStar or TalentLMS?
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 BotStar and TalentLMS 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.