Integration
Connect Azurevirtualmachines and Quilia
When New Virtual Machine fires in Azurevirtualmachines, your agent runs Create Contact in Quilia, or Appointment Created in Quilia 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 Quilia 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 Quilia can do together
From Azurevirtualmachines to Quilia
When New Virtual Machine in Azurevirtualmachines
then Create Contact in Quilia
From Quilia 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 Quilia
Triggers and actions 4 triggers · 29 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.
- Appointment Created
Triggers when a new appointment is created in Quilia.
- Appointment Updated
Triggers when an appointment is updated in Quilia.
- New Client Activity
Triggers when a client performs an activity in Quilia, such as uploading a document to their case.
- Add New Client
Creates a new client in Quilia with their name, phone, email, address and date of birth.
- Create Contact
Creates a contact (such as a witness, adjustor, employer or medical provider) attached to a case or a client.
- Delete a Contact
Permanently deletes a company or people contact from your Quilia organization.
- Delete Case
Permanently deletes a case, including its members, documents and chat history.
- Delete Client
Permanently deletes a client from your firm, including their case memberships.
- Delete Documents
Deletes one or more Quilia documents, removing both the records and their stored files.
- Find a Document
Finds a document by its id and returns its type plus a secure download link that expires after 30 minutes.
- Find Client by Phone
Finds a client in your firm by phone number and returns the client record with the cases they belong to.
- Invite Clients to Case
Invites clients or staff to a Quilia case. Clients are texted an invite; staff are added as invited. Returns who was invited and who was skipped.
- List Clients
Returns the firm's clients, optionally filtered by name, email or phone.
- List Webhook Events
Returns the webhook events your Quilia firm can subscribe to, with their descriptions and payload schemas.
- Retrieve a Single Client
Returns a single client by id, including the cases the client belongs to.
- Retrieve Individual Case
Returns one case by its ID, including its status, type, dates, client, organization and case members.
- Simulate Webhook Event
Sends a sample Quilia webhook event to an endpoint URL so you can test a webhook integration.
- Update a Contact
Updates an existing Quilia contact (a company or a person). Only the fields you fill in are changed.
- Update Case
Updates an existing case's status, type, opening date or custom CMS data. Only the fields you fill in are changed.
- Update Client Information
Updates an existing client's contact details, address and demographic information. Only the fields you fill in are changed.
- Upload Documents
Uploads a document file to a client's case in Quilia and returns the new document ids.
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 Quilia
Google Drive to QuiliaGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to QuiliaMailchimp marketing automation and email platform.
Questions
Azurevirtualmachines and Quilia, 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 Quilia when something happens in Azurevirtualmachines?
Any of Quilia's 18 actions, including Create Contact, Update a Contact, Update Case and Update Client Information. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Quilia to Azurevirtualmachines?
Yes. When something happens in Quilia, your agent can act in Azurevirtualmachines too. This page covers both directions: Quilia's triggers and Azurevirtualmachines's actions are listed here as well.
Do I have to build a connector for Azurevirtualmachines or Quilia?
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 Quilia 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.