Integration
Connect BotStar and Hubhus
When New CMS Entity Item fires in BotStar, your agent runs Create User in Hubhus, or New Calendar Event in Hubhus 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 Hubhus 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 Hubhus can do together
From BotStar to Hubhus
When New CMS Entity Item in BotStar
then Create User in Hubhus
When New CMS Entity Item in BotStar
then Update calendar event in Hubhus
From Hubhus to BotStar
When New Calendar Event in Hubhus
then Send Message in BotStar
When New Contact in Hubhus
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 Hubhus
Triggers and actions 4 triggers · 38 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 Calendar EventTriggers when a new calendar event (booking or meeting) is created.
Trigger
New ContactTriggers when a new contact is created in Hubhus.
Trigger
New LeadTriggers when a new lead is added to a Hubhus campaign.
Action
Add calendar resourceCreates a calendar resource in Hubhus — either a user's calendar or a standalone calendar such as a vehicle or meeting room.
Action
Add consentRecords a person's consent to a consent declaration, identified by email and/or phone.
Action
Book time slotBooks a time slot through a Hubhus booking form, creating a calendar event for the chosen calendar resources.
Action
Create UserCreates a user with a name, email, phone, department and role.
Action
Delete Calendar EventDeletes a calendar event.
Action
Delete LeadDeletes a lead.
Action
Find absencesReturns absences matching the given filters, such as type, status, user or date period.
Action
Find Calendar EventsReturns calendar events, optionally filtered by creation or update time, ID or an expression filter.
Action
Find calendar resourcesReturns calendar resources (user calendars and other resources such as rooms or vehicles) matching the given filters.
Action
Find CampaignsReturns the campaigns in the account.
Action
Find ContactsReturns contacts, optionally filtered by creation or update time, ID or an expression filter.
Action
Find LeadsReturns leads in a campaign, optionally filtered by creation or update time, ID or a lead expression filter.
Action
Find ProductsReturns products, optionally filtered.
Action
Find UsersReturns users in the account, optionally filtered.
Action
Get CampaignReturns one campaign by ID.
Action
Get ContactReturns one contact by ID.
Action
Get productReturns a single product from the product catalogue, optionally with its category, image, tags and custom product fields.
Action
Get UserReturns one user by ID.
Action
Update calendar eventUpdates an existing calendar event in Hubhus; fields left blank are not changed.
Action
Update userUpdates an existing Hubhus user's name, contact details, department, role, tags or active status. Fields left blank are not changed.
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 Hubhus
Google Sheets to HubhusGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to HubhusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to HubhusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to HubhusGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to HubhusActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to HubhusOrganize anything with Airtable, a modern database created for everyone.
Questions
BotStar and Hubhus, 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 Hubhus when something happens in BotStar?
Any of Hubhus's 20 actions, including Create User, Update calendar event, Update user and Add calendar resource. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hubhus to BotStar?
Yes. When something happens in Hubhus, your agent can act in BotStar too. This page covers both directions: Hubhus's triggers and BotStar's actions are listed here as well.
Do I have to build a connector for BotStar or Hubhus?
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 Hubhus 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.