Integration
Connect BotStar and Cling
When New CMS Entity Item fires in BotStar, your agent runs Add project in Cling, or New Document in Cling 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 Cling 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 Cling can do together
From BotStar to Cling
When New CMS Entity Item in BotStar
then Add project in Cling
When New CMS Entity Item in BotStar
then Create Client in Cling
From Cling to BotStar
When New Document in Cling
then Send Message in BotStar
When Document Accepted in Cling
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 Cling
Triggers and actions 6 triggers · 39 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
Document AcceptedTriggers when a Cling document is fully accepted (signed by all clients).
Trigger
Document DeniedTriggers when a client denies a Cling document.
Trigger
Document ExpiredTriggers when a Cling document passes its expiration date.
Trigger
Document SentTriggers when a Cling document is sent to its clients.
Trigger
New DocumentTriggers when a new document is created in Cling.
Action
Add projectCreates a new project in Cling to group documents.
Action
Add templateCreates a new document template in your Cling company.
Action
Create ClientCreates a new client (end customer) in Cling that documents can be sent to.
Action
Create DocumentCreates a new Cling document from a template for one signing client. The document is created as a draft; use Send Document to deliver it.
Action
Delete clientDeletes a client (end customer) from your Cling account.
Action
Delete DocumentDeletes a Cling document by its ID.
Action
Delete projectDeletes a project in Cling by its ID.
Action
Delete templateDeletes a template from your Cling account.
Action
Get clientReturns a single client (end customer) by its ID, including contact details, addresses and notes.
Action
Get DocumentReturns one Cling document by its ID, including its status and dates.
Action
Get projectReturns a single Cling project by its ID, including its status, totals, clients and main document summary.
Action
Get templateReturns a single Cling template by its ID.
Action
List ClientsReturns the clients (end customers) in your Cling account.
Action
List documentsReturns documents in your Cling account, optionally filtered by status or an advanced filter and sorted.
Action
List projectsReturns the projects in your Cling account, optionally filtered and sorted.
Action
List TemplatesReturns the document templates in your Cling account.
Action
Send DocumentSends an existing Cling document to its clients for signing.
Action
Update clientUpdates an existing client's details in Cling, such as name, contact information and addresses. Fields left blank are not changed.
Action
Update documentUpdates a Cling document's status or assigned company user. Only the values you fill in are changed.
Action
Update projectUpdates an existing project's name or status in Cling.
Action
Update templateRenames an existing Cling template.
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 Cling
ActiveCampaign to ClingActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to ClingOrganize anything with Airtable, a modern database created for everyone.
Asana to ClingAsana is a collaborative information manager for workspace.
ClickUp to ClingClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to ClingBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to ClingCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
BotStar and Cling, 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 Cling when something happens in BotStar?
Any of Cling's 21 actions, including Create Client, Create Document, Send Document and Update client. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Cling to BotStar?
Yes. When something happens in Cling, your agent can act in BotStar too. This page covers both directions: Cling's triggers and BotStar's actions are listed here as well.
Do I have to build a connector for BotStar or Cling?
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 Cling 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.