Integration
Connect Azurevirtualmachines to Pylon
When New Virtual Machine fires in Azurevirtualmachines, your agent runs Add internal note to issue 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 Azurevirtualmachines 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)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 Azurevirtualmachines can start in Pylon
When New Virtual Machine in Azurevirtualmachines
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 Azurevirtualmachines and Pylon
Triggers and actions 1 trigger · 36 actions
- New Virtual Machine
Triggers when a new virtual machine appears in an Azure subscription.
- Deallocate Virtual Machine
Shuts down an Azure virtual machine and releases its compute resources, so compute charges stop until it is started again.
- Get Virtual Machine
Returns a virtual machine's details and its current power state (running, stopped or deallocated).
- List Available VM Sizes
Returns the virtual machine sizes offered in an Azure region, with CPU and memory, and whether each is available to the subscription.
- List Locations
Returns the Azure regions available to a subscription.
- List Resource Groups
Returns the resource groups in an Azure subscription.
- List Subscriptions
Returns the Azure subscriptions the connected app registration can access.
- List Virtual Machines
Returns every virtual machine in an Azure subscription, with its size, region and resource group.
- List Virtual Machines in Resource Group
Returns the virtual machines in one Azure resource group, with their size and region.
- Power Off Virtual Machine
Powers off an Azure virtual machine. The machine stops running but stays allocated, so compute charges continue; use Deallocate Virtual Machine to stop them.
- Restart Virtual Machine
Restarts a running Azure virtual machine. Azure accepts the request and reboots the machine in the background.
- Start Virtual Machine
Starts a stopped or deallocated Azure virtual machine. Azure accepts the request and powers the machine on in the background.
- Add internal note to issue
Adds an internal note to a Pylon issue. Internal notes are not visible to the requester.
- Add tag
Creates a new tag in Pylon that can be applied to accounts, articles or issues.
- Add task
Creates a task in Pylon with a title and optional details such as assignee, due date, account, project and status. Returns the new task.
- Create Account
Creates a new customer account in Pylon with its name, domains, owner, tags and other details.
- Create Account Activity
Creates a custom activity on a Pylon account's timeline.
- Create Call Recording
Creates 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.
- Delete account
Permanently deletes a Pylon account by its ID or external ID.
- Delete issue
Permanently deletes an issue in Pylon.
- Find Account by Name
Finds Pylon accounts by name, by exact or partial match, returning the matching accounts.
- Find contacts by criteria
Returns the contacts that match the specified search text and/or filter.
- Find issues by criteria
Returns Pylon issues matching a text search and/or a filter on fields such as state, assignee, account, tags or dates.
- Get account
Returns a single Pylon account by its ID or external ID, including its domains, owner, tags, channels and custom fields.
- Get contact
Returns a single contact, including its emails, phone numbers, account and custom field values, by its ID or external ID.
- Get issue
Returns a single Pylon issue by its ID or issue number, including its custom field values. An error occurs if the issue is not found.
- Get user
Returns a single Pylon team member by ID, including their name, email addresses, status, and assigned roles.
- Get Users
Returns the users in your Pylon organization, optionally including deactivated users.
- List accounts
Returns all accounts in your Pylon organization, including their domains, owner, tags and custom field values.
- List contacts
Returns all contacts in the Pylon organization, including their emails, phone numbers, account and custom field values.
- List tags
Returns all tags in the Pylon organization, with each tag's name, color and the type of object it applies to.
- List teams
Returns all teams in the Pylon organization, with their members, how each team assigns issues, and any recurring assignment schedule.
- Reply to issue
Sends a customer-facing reply on a Pylon issue, continuing an existing conversation or thread. Returns the ID of the new message and its issue.
- Update Account
Updates an existing Pylon account. Only the fields you fill in are changed.
- Update contact
Updates an existing Pylon contact by its ID or external ID. Only the fields you fill in are changed.
- Update issue
Updates 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.
- Update Issue Followers
Adds 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 Azurevirtualmachines
Azurevirtualmachines to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Azurevirtualmachines to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Azurevirtualmachines to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Azurevirtualmachines to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Azurevirtualmachines to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Azurevirtualmachines to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Pylon
Questions
Azurevirtualmachines and Pylon, answered
What can start an automation from Azurevirtualmachines?
Any of Azurevirtualmachines's 1 trigger in the catalog, including New Virtual Machine. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pylon when something happens in Azurevirtualmachines?
Any of Pylon's 25 actions, including Create Account, Create Account Activity, Create Call Recording and Update Account. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pylon to Azurevirtualmachines?
Pylon has no triggers in the catalog today, so automations start in Azurevirtualmachines. 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 Azurevirtualmachines 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 Azurevirtualmachines 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.