Integration
Connect Azurevirtualmachines and Skyvern
When New Virtual Machine fires in Azurevirtualmachines, your agent runs Create and Run a Task in Skyvern, or New or Updated Skyvern Workflow in Skyvern 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 Skyvern 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 Skyvern can do together
From Azurevirtualmachines to Skyvern
When New Virtual Machine in Azurevirtualmachines
then Create and Run a Task in Skyvern
From Skyvern 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 Skyvern
Triggers and actions 2 triggers · 26 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.
- New or Updated Skyvern Workflow
Triggers when a Skyvern workflow (agent) is created or a new version of it is saved.
- Add browser session
Creates a Skyvern browser session that persists across multiple task and workflow runs, and returns its session id and live-view link.
- Add credential
Creates a new stored credential (login, credit card or secret) in your Skyvern organization for use by tasks and agents.
- Add workflow
Creates a new Skyvern workflow (agent) from a JSON or YAML definition and returns the saved workflow.
- Cancel run
Cancels a running Skyvern task run or workflow run by its id.
- Create and Run a Task
Starts a Skyvern browser-automation task from a plain-language prompt and returns the new run, including its id, status and link in the Skyvern app.
- Create and Run Task V2
Starts a Skyvern 2.0 browser task from a natural-language prompt and returns the new run's id and status.
- Delete workflow
Deletes a Skyvern workflow (agent) by its ID.
- Get a Browser Session
Returns the details of a Skyvern browser session, including its status, browser address for connecting, downloaded files and recordings.
- Get a Task
Returns a Skyvern task run by its id, including its status, extracted output, downloaded files, recording and screenshots.
- Get a Task V2
Returns the status, output, recording and screenshots of a Skyvern task run.
- Get a Workflow
Returns a Skyvern workflow (agent) by its permanent id, including its blocks, parameters and settings.
- List credentials
Returns the credentials stored in your Skyvern organization, optionally filtered by vault, type or search text. Secrets are never included.
- List runs
Returns your organization's task and agent runs, newest first, optionally filtered by status, run type, agent, tags, failure category or a search term.
- List workflows
Returns the workflows (agents) in your Skyvern organization, optionally filtered by search text, folder, status or tags. Returns up to 100 workflows.
- Run a Workflow
Starts a run of one of your Skyvern workflows (agents) with the parameters you supply, and returns the new run's id, status and link.
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 Skyvern
Google Drive to SkyvernGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Azurevirtualmachines and Skyvern, 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 Skyvern when something happens in Azurevirtualmachines?
Any of Skyvern's 15 actions, including Create and Run a Task, Create and Run Task V2, Add browser session and Add credential. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Skyvern to Azurevirtualmachines?
Yes. When something happens in Skyvern, your agent can act in Azurevirtualmachines too. This page covers both directions: Skyvern's triggers and Azurevirtualmachines's actions are listed here as well.
Do I have to build a connector for Azurevirtualmachines or Skyvern?
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 Skyvern 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.