Integration
Connect Angaza to Pylon
When New Account fires in Angaza, your agent runs Create Account in Pylon. 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 Pylon 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 Pylon
When New Account in Angaza
then Create Account in Pylon
When New Payment in Angaza
then Add internal note to issue in Pylon
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 Pylon
Triggers and actions 5 triggers · 43 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 internal note to issueAdds an internal note to a Pylon issue. Internal notes are not visible to the requester.
Action
Add tagCreates a new tag in Pylon that can be applied to accounts, articles or issues.
Action
Add taskCreates a task in Pylon with a title and optional details such as assignee, due date, account, project and status. Returns the new task.
Action
Create AccountCreates a new customer account in Pylon with its name, domains, owner, tags and other details.
Action
Create Account ActivityCreates a custom activity on a Pylon account's timeline.
Action
Create Call RecordingCreates a call recording in Pylon from your own call recorder, including its transcript, and returns the new recording. Requires the Custom Call Recorder integration to be enabled in Pylon.
Action
Create ContactCreates a new contact in Pylon with a name and optional email, account, phone numbers and portal role.
Action
Create IssueCreates a new issue in Pylon with its first message, either as an internal note or delivered to the customer over a channel you choose. Returns the created issue.
Action
Delete accountPermanently deletes a Pylon account by its ID or external ID.
Action
Delete issuePermanently deletes an issue in Pylon.
Action
Find Account by NameFinds Pylon accounts by name, by exact or partial match, returning the matching accounts.
Action
Find contacts by criteriaReturns the contacts that match the specified search text and/or filter.
Action
Find issues by criteriaReturns Pylon issues matching a text search and/or a filter on fields such as state, assignee, account, tags or dates.
Action
Get accountReturns a single Pylon account by its ID or external ID, including its domains, owner, tags, channels and custom fields.
Action
Get contactReturns a single contact, including its emails, phone numbers, account and custom field values, by its ID or external ID.
Action
Get issueReturns a single Pylon issue by its ID or issue number, including its custom field values. An error occurs if the issue is not found.
Action
Get userReturns a single Pylon team member by ID, including their name, email addresses, status, and assigned roles.
Action
Get UsersReturns the users in your Pylon organization, optionally including deactivated users.
Action
List accountsReturns all accounts in your Pylon organization, including their domains, owner, tags and custom field values.
Action
List contactsReturns all contacts in the Pylon organization, including their emails, phone numbers, account and custom field values.
Action
List issuesReturns the issues created within a time range of up to 365 days, newest first.
Action
List tagsReturns all tags in the Pylon organization, with each tag's name, color and the type of object it applies to.
Action
List teamsReturns all teams in the Pylon organization, with their members, how each team assigns issues, and any recurring assignment schedule.
Action
Reply to issueSends a customer-facing reply on a Pylon issue, continuing an existing conversation or thread. Returns the ID of the new message and its issue.
Action
Update AccountUpdates an existing Pylon account. Only the fields you fill in are changed.
Action
Update contactUpdates an existing Pylon contact by its ID or external ID. Only the fields you fill in are changed.
Action
Update issueUpdates an existing Pylon issue — its title, state, assignee, team, account, requester, tags, type, portal visibility and custom fields. Only the fields you fill in are changed.
Action
Update Issue FollowersAdds or removes users and contacts as followers of a Pylon issue, and returns the issue's resulting followers.
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 Pylon
HubSpot to PylonHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PylonSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PylonSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PylonGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PylonGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PylonGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Angaza and Pylon, 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 Pylon when something happens in Angaza?
Any of Pylon's 28 actions, including Create Account, Create Account Activity, Create Call Recording and Create Contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pylon to Angaza?
Pylon has no triggers in the catalog today, so automations start in Angaza. If you need the other direction, ask: your agent reads Pylon's API documentation and adds it.
Do I have to build a connector for Angaza or Pylon?
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 Pylon 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.