Integration
Connect BotStar to Mx Technologies
When New CMS Entity Item fires in BotStar, 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 BotStar 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)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 can start in Mx Technologies
When New CMS Entity Item in BotStar
then Add user in Mx Technologies
When New CMS Entity Item in BotStar
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 BotStar and Mx Technologies
Triggers and actions 1 trigger · 53 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.
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 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 Mx Technologies
Felt to Mx TechnologiesCloud-based GIS platform for creating interactive maps and dashboards from geospatial and database data.
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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Mx TechnologiesGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
BotStar and Mx Technologies, 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 Mx Technologies when something happens in BotStar?
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 BotStar?
Mx Technologies has no triggers in the catalog today, so automations start in BotStar. 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 BotStar 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 BotStar 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.