Integration
Connect Azurevirtualmachines to Apify
When New Virtual Machine fires in Azurevirtualmachines, your agent runs Run Task in Apify. 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 Apify 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 Apify
When New Virtual Machine in Azurevirtualmachines
then Run Task in Apify
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 Apify
Triggers and actions 1 trigger · 31 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.
- Abort Actor build
Aborts an Actor build that is starting or running and returns the build's details. Builds that already finished, failed, timed out or are aborting are left unchanged.
- Abort Actor run
Aborts a running or starting Apify Actor run and returns the run's details, including its updated status. Runs that already finished, failed or timed out are left unchanged.
- Add dataset items
Appends one or more items to the end of an Apify dataset.
- Add request to request queue
Adds a URL request to an Apify request queue, or returns the existing request if one with the same unique key is already queued.
- Delete key-value store record
Deletes a record, identified by its key, from an Apify key-value store.
- Fetch Dataset Items
Returns all items stored in an Apify dataset, such as the results scraped by an Actor run, with optional field selection and cleanup.
- Find Last Actor Run
Returns the most recent run of an Actor, optionally limited to runs with a given status or started a given way, including its status, timing and the ids of its default dataset and key-value store.
- Find Last Task Run
Returns the most recent run of an Apify Actor task, optionally limited to runs with a given status or origin.
- Get Actor
Returns all the details of an Apify Actor, including its versions, default run options, statistics and pricing.
- Get Actor run
Returns the details of one Actor run, including its status, timing, statistics, costs and the IDs of its default dataset, key-value store and request queue. Can optionally wait up to 60 seconds for the run to finish.
- Get Key-Value Store Record
Returns the value stored under a key in an Apify key-value store, such as an Actor run's output or input record.
- Get task
Returns the details of an Apify Actor task, including its saved input, run options, and run statistics.
- List Actor runs
Returns the runs of one of your Apify Actors, with each run's status, start and finish times, cost and the IDs of its default dataset and key-value store. Can be filtered by status and start date.
- List Actors
Returns the Actors you created or have used in your Apify account, with each Actor's ID, name, owner username, title and usage stats.
- List datasets
Returns the datasets in your Apify account, with each dataset's id, name, item count and timestamps.
- List tasks
Returns the Actor tasks you have created or used, with each task's id, name, Actor and run stats.
- Run Actor
Starts a run of an Apify Actor with the input you provide and returns the new run, including its status and the IDs of its default dataset and key-value store.
- Run Task
Starts a run of one of your saved Apify Actor tasks, optionally overriding parts of its input, and returns the new run with its status and storage IDs.
- Scrape Single URL
Scrapes one web page with Apify's Website Content Crawler and returns its cleaned text, Markdown, title and metadata. Waits for the scrape to finish (up to 5 minutes).
- Set Key-Value Store Record
Saves a value under a key in an Apify key-value store, replacing any existing record with the same key.
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 Apify
Questions
Azurevirtualmachines and Apify, 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 Apify when something happens in Azurevirtualmachines?
Any of Apify's 20 actions, including Abort Actor build, Abort Actor run, Add dataset items and Add request to request queue. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Apify to Azurevirtualmachines?
Apify has no triggers in the catalog today, so automations start in Azurevirtualmachines. If you need the other direction, ask: your agent reads Apify's API documentation and adds it.
Do I have to build a connector for Azurevirtualmachines or Apify?
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 Apify 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.