Integration
Connect Angaza and BotStar
When New Account fires in Angaza, your agent runs Send Message in BotStar, or New CMS Entity Item in BotStar to Create Client in Angaza. 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 Angaza and BotStar 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 Angaza and BotStar can do together
From Angaza to BotStar
When New Account in Angaza
then Send Message in BotStar
When New Payment in Angaza
then Create CMS Entity Item in BotStar
From BotStar to Angaza
When New CMS Entity Item in BotStar
then Create Client in Angaza
When New CMS Entity Item in BotStar
then Create Payment in Angaza
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 Angaza and BotStar
Triggers and actions 6 triggers · 33 actions
Trigger
Account Paid OffTriggers when an Angaza account is paid off (its status becomes Unlocked).
Trigger
New AccountTriggers when a new account is registered in Angaza.
Trigger
New PaymentTriggers when a new payment is recorded in Angaza.
Trigger
New ProspectTriggers when a new prospective account is submitted in Angaza.
Trigger
Updated Prospect StatusTriggers when an Angaza prospective account changes status (for example approved or rejected).
Action
Create AccountRegisters a new Angaza account: attaches a unit to an existing or new client on a pricing group.
Action
Create ClientCreates a client (customer) in Angaza with a phone number and optional name, external reference and attributes.
Action
Create PaymentRecords a payment toward an Angaza account.
Action
Create Prospective AccountSubmits a prospective account (a customer application awaiting approval) for an existing or new client.
Action
Find AccountsSearches Angaza accounts by client, responsible user, unit number or status and returns the matches.
Action
Find ClientsSearches Angaza clients by phone number or external reference and returns the matches.
Action
Get AccountReturns one Angaza account by its QID, with status, amounts paid and due date.
Action
Get Account by Unit NumberReturns the Angaza account currently attached to a unit (device) number.
Action
Get ClientReturns one Angaza client (customer) by its QID, with name, phone and attribute values.
Action
Get PaymentReturns one Angaza payment by its QID.
Action
Get Prospective AccountReturns one Angaza prospective account by its QID, with its approval status.
Action
Get UserReturns one Angaza user (agent or staff member) by QID.
Action
List Pricing GroupsReturns your organization's Angaza pricing groups (the payment plans accounts are registered on).
Action
Update ClientUpdates an existing Angaza client's name, phone, external reference or attributes.
Action
Update Prospective AccountChanges the status of an Angaza prospective account, e.g. approves or rejects it.
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.
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 Angaza
Angaza to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Angaza to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Angaza to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Angaza to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Angaza to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Angaza to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into BotStar
ActiveCampaign to BotStarActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to BotStarOrganize anything with Airtable, a modern database created for everyone.
Asana to BotStarAsana is a collaborative information manager for workspace.
100Hires ATS to BotStar100Hires ATS is a recruitment software that includes talent sourcing, and applicant tracking to accelerate...
1ClickImpact to BotStarUse 1ClickImpact APIs to plant trees, capture carbon, remove waste, donate to causes, and track these...
1CRM to BotStar1CRM allows you to organize a large part of your business within a single web application, and access that...
Questions
Angaza and BotStar, answered
What can start an automation from Angaza?
Any of Angaza's 5 triggers in the catalog, including New Account, New Payment, New Prospect and Updated Prospect Status. Describe the moment in plain language and your agent picks the right one.
What can your agent do in BotStar when something happens in Angaza?
Any of BotStar's 18 actions, including Create Bot Attribute, Create CMS Entity Item, Create Custom User Attribute and Send Message. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from BotStar to Angaza?
Yes. When something happens in BotStar, your agent can act in Angaza too. This page covers both directions: BotStar's triggers and Angaza's actions are listed here as well.
Do I have to build a connector for Angaza or BotStar?
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 Angaza and BotStar 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.