Integration
Connect BotStar and Gleantap
When New CMS Entity Item fires in BotStar, your agent runs Add Contact Event in Gleantap, or New Contact in Gleantap 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 Gleantap 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 Gleantap can do together
From BotStar to Gleantap
When New CMS Entity Item in BotStar
then Add Contact Event in Gleantap
When New CMS Entity Item in BotStar
then Add Customer in Gleantap
From Gleantap to BotStar
When New Contact in Gleantap
then Send Message in BotStar
When New Contact in Gleantap
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 Gleantap
Triggers and actions 2 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 ContactTriggers when a new contact is added in Gleantap.
Action
Add Contact EventRecords an event (such as a purchase or class check-in) on a Gleantap contact.
Action
Add CustomerCreates a contact (lead or customer) in Gleantap, or updates the existing contact with the same email.
Action
Add tagCreates a tag in Gleantap, or returns the existing tag when one with the same name already exists.
Action
Delete ContactDeletes a Gleantap contact (a soft delete that removes it from the dashboard, segments and sends).
Action
Enroll contact in flowEnrolls a contact into a Gleantap flow, starting the flow's steps (including its messages) for that contact. Returns the new flow run.
Action
Find Contact by EmailFinds the Gleantap contact with the given email address.
Action
Get ContactReturns one Gleantap contact by its ID.
Action
List campaignsReturns the campaigns in a Gleantap workroom, optionally filtered by status or channel.
Action
List contactsReturns contacts in a Gleantap workroom, optionally filtered by email, phone, tags, lifecycle stage, location, consent or creation date.
Action
List segmentsReturns the segments (static and dynamic contact lists) in a Gleantap workroom, optionally filtered by type, name or creation date.
Action
List tagsReturns the tags in a Gleantap workroom with how many contacts carry each one.
Action
Opt in contactRecords a contact's marketing consent (opt-in) for SMS or email, with optional source and timestamp evidence. Returns the updated contact.
Action
Opt out contactRecords that a Gleantap contact has opted out of SMS, email, or all marketing channels, and returns the updated contact.
Action
Remove contact from segmentRemoves a contact from a static segment in Gleantap.
Action
Send emailSends a single transactional or marketing email to one Gleantap contact, using a template or your own subject and body.
Action
Send SMSSends a transactional SMS to one Gleantap contact.
Action
Update CustomerUpdates an existing Gleantap contact. Only the fields you fill in are 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 Gleantap
ActiveCampaign to GleantapActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to GleantapOrganize anything with Airtable, a modern database created for everyone.
Asana to GleantapAsana is a collaborative information manager for workspace.
ClickUp to GleantapClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to GleantapDiscord is an all-in-one voice and text chat for gamers.
Freshdesk to GleantapFreshdesk is a cloud-based customer support and helpdesk platform.
Questions
BotStar and Gleantap, 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 Gleantap when something happens in BotStar?
Any of Gleantap's 17 actions, including Send email, Send SMS, Update Customer and Add Contact Event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Gleantap to BotStar?
Yes. When something happens in Gleantap, your agent can act in BotStar too. This page covers both directions: Gleantap's triggers and BotStar's actions are listed here as well.
Do I have to build a connector for BotStar or Gleantap?
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 Gleantap 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.