Integration
Connect Angaza to Instatus
When New Account fires in Angaza, your agent runs Add component in Instatus. 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 Instatus 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 can start in Instatus
When New Account in Angaza
then Add component in Instatus
When New Payment in Angaza
then Add incident update in Instatus
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 Instatus
Triggers and actions 5 triggers · 29 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.
Action
Add componentCreates a new component on an Instatus status page and returns the created component.
Action
Add incident updatePosts a new update to an existing incident on an Instatus status page, optionally changing the incident status and affected component statuses.
Action
Add maintenanceSchedules a new maintenance on an Instatus status page, with its affected components, timing and subscriber notification options.
Action
Add subscriberAdds a subscriber (by email or phone) to a status page, subscribed to all components or to specific ones.
Action
Create IncidentCreates a new incident on an Instatus status page, optionally marking affected components and notifying subscribers.
Action
Delete incidentDeletes an incident from an Instatus status page.
Action
Get componentReturns one component on an Instatus status page, including its name, current status, description and group.
Action
Get incidentReturns a single incident on a status page, including its updates, affected components and the teammate who created it.
Action
Get maintenanceReturns one scheduled maintenance on a status page, including its updates and affected components.
Action
List componentsReturns the components on an Instatus status page, with each component's name, status and group.
Action
List maintenancesReturns the scheduled, in-progress and completed maintenances on an Instatus status page.
Action
List status pagesReturns the status pages in your Instatus account, including each page's id, name, subdomain and current status.
Action
List subscribersReturns the subscribers of an Instatus status page, optionally filtered by email/phone search or subscription status.
Action
Update componentUpdates a component on an Instatus status page, such as its name, description, status, order or group.
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 Instatus
HubSpot to InstatusHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to InstatusSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to InstatusSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to InstatusGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to InstatusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to InstatusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Angaza and Instatus, 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 Instatus when something happens in Angaza?
Any of Instatus's 14 actions, including Create Incident, Update component, Add component and Add incident update. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Instatus to Angaza?
Instatus has no triggers in the catalog today, so automations start in Angaza. If you need the other direction, ask: your agent reads Instatus's API documentation and adds it.
Do I have to build a connector for Angaza or Instatus?
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 Instatus 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.