Integration
Connect Azurevirtualmachines and Callingly
When New Virtual Machine fires in Azurevirtualmachines, your agent runs Update or Tag Lead in Callingly, or Call Completed in Callingly 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 Callingly 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 Callingly can do together
From Azurevirtualmachines to Callingly
When New Virtual Machine in Azurevirtualmachines
then Update or Tag Lead in Callingly
When New Virtual Machine in Azurevirtualmachines
then Call Lead in Callingly
From Callingly to Azurevirtualmachines
When Call Completed in Callingly
then Deallocate Virtual Machine in Azurevirtualmachines
When Lead Created in Callingly
then Power Off Virtual Machine in 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 Callingly
Triggers and actions 5 triggers · 23 actions
Trigger
New Virtual MachineTriggers when a new virtual machine appears in an Azure subscription.
Action
Deallocate Virtual MachineShuts down an Azure virtual machine and releases its compute resources, so compute charges stop until it is started again.
Action
Get Virtual MachineReturns a virtual machine's details and its current power state (running, stopped or deallocated).
Action
List Available VM SizesReturns the virtual machine sizes offered in an Azure region, with CPU and memory, and whether each is available to the subscription.
Action
List LocationsReturns the Azure regions available to a subscription.
Action
List Resource GroupsReturns the resource groups in an Azure subscription.
Action
List SubscriptionsReturns the Azure subscriptions the connected app registration can access.
Action
List Virtual MachinesReturns every virtual machine in an Azure subscription, with its size, region and resource group.
Action
List Virtual Machines in Resource GroupReturns the virtual machines in one Azure resource group, with their size and region.
Action
Power Off Virtual MachinePowers off an Azure virtual machine. The machine stops running but stays allocated, so compute charges continue; use Deallocate Virtual Machine to stop them.
Action
Restart Virtual MachineRestarts a running Azure virtual machine. Azure accepts the request and reboots the machine in the background.
Action
Start Virtual MachineStarts a stopped or deallocated Azure virtual machine. Azure accepts the request and powers the machine on in the background.
Trigger
Call CompletedTriggers when a call to a lead is made and completes in Callingly.
Trigger
Lead CreatedTriggers when a new lead is added to Callingly.
Trigger
Lead Updated or TaggedTriggers when a Callingly lead is tagged or its status, stage or result changes.
Trigger
New SMSTriggers when a text message is sent or received in Callingly.
Action
Call LeadCreates or updates a lead and immediately calls your team, connecting the first rep who answers to the lead.
Action
Delete LeadDeletes a Callingly lead.
Action
Find LeadFinds a Callingly lead by phone number and returns the first match.
Action
Get CallReturns one Callingly call by its ID, with its outcome, duration, recording and transcript.
Action
Get LeadReturns one Callingly lead by its ID, with its contact details and status.
Action
List SequencesReturns the follow-up sequences in the Callingly account.
Action
List TeamsReturns the teams in the Callingly account.
Action
List UsersReturns the users (agents) in the Callingly account.
Action
Schedule CallCreates or updates a lead and schedules a call from your team to the lead at the time you choose.
Action
Schedule SMSSchedules a text message to an existing Callingly lead for a future time.
Action
Send SMSSends a text message from one of your Callingly numbers to a lead.
Action
Update or Tag LeadUpdates a Callingly lead's details, status, stage or tags.
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 Callingly
ActiveCampaign to CallinglyActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to CallinglyOrganize anything with Airtable, a modern database created for everyone.
Asana to CallinglyAsana is a collaborative information manager for workspace.
Brevo to CallinglyBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to CallinglyCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
2Chat to Callingly2Chat is a conversational commerce automation tool for WhatsApp, Instagram, Messenger, and SMS.
Questions
Azurevirtualmachines and Callingly, 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 Callingly when something happens in Azurevirtualmachines?
Any of Callingly's 12 actions, including Send SMS, Update or Tag Lead, Call Lead and Find Lead. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Callingly to Azurevirtualmachines?
Yes. When something happens in Callingly, your agent can act in Azurevirtualmachines too. This page covers both directions: Callingly's triggers and Azurevirtualmachines's actions are listed here as well.
Do I have to build a connector for Azurevirtualmachines or Callingly?
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 Callingly 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.