Integration
Connect Azurevirtualmachines and Whippy
When New Virtual Machine fires in Azurevirtualmachines, your agent runs Add Contacts to a Sequence in Whippy, or Channels in Whippy 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 Whippy 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 Azurevirtualmachines and Whippy can do together
From Azurevirtualmachines to Whippy
When New Virtual Machine in Azurevirtualmachines
then Add Contacts to a Sequence in Whippy
From Whippy 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 Whippy
Triggers and actions 5 triggers · 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.
- Channels
Triggers when a new channel is added to your Whippy organization.
- List Agents
Triggers when a new AI agent is added to your Whippy organization.
- List Calls
Triggers when a new call is logged in Whippy.
- List Users
Triggers when a new user is added to your Whippy organization.
- Add Contacts to a Sequence
Adds contacts to a Whippy sequence, creating any contact that does not exist yet.
- Create a Contact
Creates a new contact in Whippy from a phone number, with optional name, email and opt-in preferences.
- Delete a Contact
Deletes a contact from Whippy by its ID.
- Get Agent by ID
Returns one Whippy AI agent by its ID, including its current version and settings.
- Get All Campaigns
Returns the campaigns in your Whippy organization, optionally filtered by title.
- Get All Channels
Returns the channels (phone numbers, email addresses and other locations) in your Whippy organization.
- Get All Contacts
Returns the contacts in your Whippy organization, optionally filtered by name, email or phone.
- Get All Sequences
Returns the sequences in your Whippy organization, optionally filtered by title.
- Get All Sequence Steps
Returns all the steps of a Whippy sequence, including each step's message and delivery stats.
- Get Call by ID
Returns one Whippy call by its ID, including its recording and transcript links.
- Get Campaign by ID
Returns one Whippy campaign by its ID.
- Get Campaign Contacts
Returns the contacts a Whippy campaign was sent to, with optional filters for delivery, responses, unsubscribes and link clicks.
- Get Contact by ID
Returns one Whippy contact by its ID.
- Get Contacts in a Sequence
Returns the contacts enrolled in a Whippy sequence, with optional filters for status, step, responses, unsubscribes and link clicks.
- Get Sequence by ID
Returns one Whippy sequence by its ID.
- List Agents
Returns the AI agents in your Whippy organization, optionally filtered by name.
- List Calls
Returns calls in your Whippy organization, optionally limited to a date range.
- List Users
Returns the users in your Whippy organization, optionally filtered by name, email, phone, role or state.
- Send an SMS
Sends an SMS text message from one of your Whippy channels to a phone number.
- Update a Contact
Updates an existing Whippy contact's details such as name, email, phone or opt-in preferences.
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 Whippy
Questions
Azurevirtualmachines and Whippy, 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 Whippy when something happens in Azurevirtualmachines?
Any of Whippy's 20 actions, including Create a Contact, Send an SMS, Update a Contact and Add Contacts to a Sequence. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Whippy to Azurevirtualmachines?
Yes. When something happens in Whippy, your agent can act in Azurevirtualmachines too. This page covers both directions: Whippy's triggers and Azurevirtualmachines's actions are listed here as well.
Do I have to build a connector for Azurevirtualmachines or Whippy?
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 Whippy 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.