Integration
Connect BotStar and Groove
When New CMS Entity Item fires in BotStar, your agent runs Add label to ticket in Groove, or Customer Added in Groove 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 Groove 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 Groove can do together
From BotStar to Groove
When New CMS Entity Item in BotStar
then Add label to ticket in Groove
When New CMS Entity Item in BotStar
then Add message in Groove
From Groove to BotStar
When Customer Added in Groove
then Send Message in BotStar
When Note Added in Groove
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 Groove
Triggers and actions 10 triggers · 33 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
Agent RepliedTriggers when an agent replies to a ticket.
Trigger
Customer AddedTriggers when a customer is created.
Trigger
Customer RepliedTriggers when a customer replies to a ticket.
Trigger
Note AddedTriggers when a note is added to a ticket.
Trigger
Ticket AssignedTriggers when a ticket is assigned.
Trigger
Ticket ClosedTriggers when a ticket is closed.
Trigger
Ticket OpenedTriggers when a ticket is opened.
Trigger
Ticket StartedTriggers when a new ticket is created.
Trigger
Ticket TaggedTriggers when a ticket is tagged.
Action
Add label to ticketAdds one or more labels to a Groove ticket, keeping its existing labels, and returns the updated ticket.
Action
Add messageAdds a new message (reply or private note) to an existing Groove ticket.
Action
Add NoteAdds a private note to a Groove ticket, visible only to agents.
Action
Change Assigned AgentAssigns a Groove ticket to a different agent, identified by the agent's email address.
Action
Change Ticket MailboxMoves a ticket into a different mailbox.
Action
Change Ticket StateChanges the state of a Groove ticket (unread, opened, pending, closed or spam).
Action
Close TicketCloses a Groove ticket by setting its state to closed.
Action
Create New TicketCreates a new ticket in Groove from a customer or agent, with its first message.
Action
Get customerReturns one Groove customer, looked up by email address, including their contact details and custom attributes.
Action
Get ticketReturns a single Groove ticket by its ticket number.
Action
List agentsReturns the agents on your Groove account, optionally limited to one group.
Action
List mailboxesReturns all mailboxes in the Groove account, with each mailbox's name and email address.
Action
List messagesReturns the messages and notes on a Groove ticket.
Action
Reopen TicketReopens a Groove ticket by setting its state to opened.
Action
Update customerUpdates a customer's profile details, such as name, company, title and contact info, identified by their email address.
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 Groove
Google Sheets to GrooveGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to GrooveGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to GrooveGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to GrooveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to GrooveActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to GrooveOrganize anything with Airtable, a modern database created for everyone.
Questions
BotStar and Groove, 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 Groove when something happens in BotStar?
Any of Groove's 15 actions, including Create New Ticket, Update customer, Add label to ticket and Add message. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Groove to BotStar?
Yes. When something happens in Groove, your agent can act in BotStar too. This page covers both directions: Groove's triggers and BotStar's actions are listed here as well.
Do I have to build a connector for BotStar or Groove?
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 Groove 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.