Integration
Connect BotStar and Enchant
When New CMS Entity Item fires in BotStar, your agent runs Add Labels to Ticket in Enchant, or New Customer in Enchant 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 Enchant 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 Enchant can do together
From BotStar to Enchant
When New CMS Entity Item in BotStar
then Add Labels to Ticket in Enchant
When New CMS Entity Item in BotStar
then Create Contact in Enchant
From Enchant to BotStar
When New Customer in Enchant
then Send Message in BotStar
When New or Updated Ticket in Enchant
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 Enchant
Triggers and actions 4 triggers · 35 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
New CustomerTriggers when a new customer is added to the help desk.
Trigger
New or Updated TicketTriggers when a ticket is created or changes (new message, state, assignee, labels).
Trigger
New Ticket CreatedTriggers when a new ticket is created, optionally only in the inboxes you choose.
Action
Add Labels to TicketAdds one or more labels to a ticket, keeping its existing labels.
Action
Create AttachmentUploads a file as an attachment so its id can be added to a note or reply.
Action
Create ContactAdds an email address, phone number or Twitter handle to a customer.
Action
Create CustomerCreates a customer in your Enchant help desk, optionally with an email address.
Action
Create TicketCreates an email ticket for a customer, matched or created by email, with the customer's first message.
Action
Delete ContactDeletes one contact (email, phone or Twitter handle) from a customer.
Action
Find Customer by EmailFinds the customer with a given email address.
Action
Get AttachmentReturns an attachment's file name, MIME type and size.
Action
Get CustomerReturns one customer with their name, summary and contacts.
Action
Get TicketReturns one ticket by its id.
Action
List customersReturns customers from your Enchant help desk, optionally filtered by contact or creation date.
Action
List messagesReturns all replies and notes on a ticket, oldest to newest as Enchant lists them.
Action
List TicketsReturns up to 100 tickets, newest first, optionally filtered by state, inbox or assigned user.
Action
List UsersReturns the help desk's users (agents) with their names and email addresses.
Action
Remove Labels from TicketRemoves one or more labels from a ticket.
Action
Update CustomerUpdates a customer's name or summary. Only the fields you fill in change.
Action
Update TicketUpdates a ticket's state, assigned user, inbox or subject. Only the fields you fill in change.
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 Enchant
ActiveCampaign to EnchantActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to EnchantOrganize anything with Airtable, a modern database created for everyone.
Asana to EnchantAsana is a collaborative information manager for workspace.
ClickUp to EnchantClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to EnchantDiscord is an all-in-one voice and text chat for gamers.
Brevo to EnchantBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Questions
BotStar and Enchant, 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 Enchant when something happens in BotStar?
Any of Enchant's 17 actions, including Create Attachment, Create Contact, Create Customer and Create Ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Enchant to BotStar?
Yes. When something happens in Enchant, your agent can act in BotStar too. This page covers both directions: Enchant's triggers and BotStar's actions are listed here as well.
Do I have to build a connector for BotStar or Enchant?
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 Enchant 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.