Integration
Connect Azurevirtualmachines and Vitally
When New Virtual Machine fires in Azurevirtualmachines, your agent runs Create Task in Vitally, or Customer Created in Vitally to Deallocate Virtual Machine in Azurevirtualmachines. 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 Vitally 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 and Vitally can do together
From Azurevirtualmachines to Vitally
When New Virtual Machine in Azurevirtualmachines
then Create Task in Vitally
From Vitally to Azurevirtualmachines
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 Vitally
Triggers and actions 9 triggers · 30 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.
- Customer Created
Triggers when a new account (customer) is created in Vitally.
- Custom Object Instance Created
Triggers when a new instance of a custom object is created.
- Custom Object Instance Updated
Triggers when an instance of a custom object is created or updated.
- Note Created
Triggers when a new note is created in Vitally.
- NPS Response Created
Triggers when a new NPS response is recorded in Vitally.
- Organization Created
Triggers when a new organization is created in Vitally.
- Project Created
Triggers when a new project is created in Vitally.
- Task Created
Triggers when a new task is created in Vitally.
- Create Account
Creates an account (customer) in Vitally, identified by your own external ID.
- Create Note
Creates a note on an account or organization in Vitally.
- Create NPS Response
Records an NPS survey response from a user in Vitally.
- Create Organization
Creates an organization in Vitally, identified by your own external ID.
- Create Project From Template
Creates a project for an account or organization from a project template.
- Create Task
Creates a task on an account or organization in Vitally.
- Find a Customer
Returns a account by its Vitally ID or external ID.
- Find a Custom Object Instance
Finds a custom object instance by ID, external ID, linked account or a custom field value.
- Find a Note
Returns a note by its Vitally ID or external ID.
- Find a Organization
Returns a organization by its Vitally ID or external ID.
- Find a Task
Returns a task by its Vitally ID or external ID.
- Find a Teammate
Finds a Vitally team member by email address.
- Find a User
Finds a user by email address, external ID or email domain.
- Get Account Health Scores
Returns an account's health score and its breakdown.
- Update Customer Traits
Updates the name or traits of a account in Vitally; traits are merged with existing ones.
- Update Organization Traits
Updates the name or traits of a organization in Vitally; traits are merged with existing ones.
- Update Project Status
Changes a project's status in Vitally.
- Update Task
Updates a task in Vitally, for example to reassign or complete it.
- Update User Traits
Updates the name or traits of a user in Vitally; traits are merged with existing ones.
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 Vitally
Questions
Azurevirtualmachines and Vitally, 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 Vitally when something happens in Azurevirtualmachines?
Any of Vitally's 19 actions, including Create Account, Create Note, Create NPS Response and Create Organization. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Vitally to Azurevirtualmachines?
Yes. When something happens in Vitally, your agent can act in Azurevirtualmachines too. This page covers both directions: Vitally's triggers and Azurevirtualmachines's actions are listed here as well.
Do I have to build a connector for Azurevirtualmachines or Vitally?
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 Vitally 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.