Integration
Connect BotStar to Avoma
When New CMS Entity Item fires in BotStar, your agent runs Update call in Avoma. 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 Avoma 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 Avoma
When New CMS Entity Item in BotStar
then Update call in Avoma
When New CMS Entity Item in BotStar
then Upload Audio Call in Avoma
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 Avoma
Triggers and actions 1 trigger · 30 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
Get callReturns a single Avoma call by its external ID, including its CRM links, recording URL, processing state and linked meeting.
Action
Get meetingReturns a single Avoma meeting by its UUID, including its attendees, schedule, state, and recording and transcription details.
Action
Get meeting insightsReturns the AI notes, keyword occurrences, popular keywords and speakers for a completed Avoma meeting.
Action
Get recordingReturns the signed audio and video download links for the recording of an Avoma meeting. If the video is still being processed, returns a message instead of the links.
Action
Get transcriptionReturns the transcript of a meeting's recording, including the speakers, the timed transcript text and a link to the VTT file.
Action
List callsReturns the calls in your Avoma organization that started within a date range, optionally narrowed to inbound or outbound calls.
Action
List meetingsReturns the meetings in your Avoma organization that started within a date range, optionally filtered by attendee, CRM record, recording length or meeting type.
Action
List notesReturns the AI-generated notes for meetings in a date range, optionally narrowed to one meeting or custom category.
Action
List scorecard evaluationsReturns completed scorecard evaluations for meetings, optionally narrowed by date range, scorecard template, meeting or evaluated user.
Action
List usersReturns the users in your Avoma organization, including each user's name, email, role, teams and status.
Action
Update callUpdates an existing call's details in Avoma, such as its subject, participant names, meeting purpose and outcome, or linked CRM records, and returns the updated call.
Action
Upload Audio CallCreates a call in Avoma from a publicly reachable audio recording. Avoma downloads the recording and processes it into a transcript and notes, or uses a transcript you supply.
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 Avoma
HubSpot to AvomaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to AvomaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to AvomaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to AvomaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to AvomaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to AvomaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
BotStar and Avoma, 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 Avoma when something happens in BotStar?
Any of Avoma's 12 actions, including Update call, Upload Audio Call, Get call and Get meeting. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Avoma to BotStar?
Avoma has no triggers in the catalog today, so automations start in BotStar. If you need the other direction, ask: your agent reads Avoma's API documentation and adds it.
Do I have to build a connector for BotStar or Avoma?
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 Avoma 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.