Integration
Connect Azurevirtualmachines and Trengo
When New Virtual Machine fires in Azurevirtualmachines, your agent runs Add internal note to ticket in Trengo, or New Internal Note in Trengo 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 Trengo 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 Trengo can do together
From Azurevirtualmachines to Trengo
When New Virtual Machine in Azurevirtualmachines
then Add internal note to ticket in Trengo
When New Virtual Machine in Azurevirtualmachines
then Add ticket in Trengo
From Trengo to Azurevirtualmachines
When New Internal Note in Trengo
then Deallocate Virtual Machine in Azurevirtualmachines
When New Outbound Message in Trengo
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 Trengo
Triggers and actions 4 triggers · 26 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
New Internal NoteFires when an internal note is added to a Trengo ticket.
Trigger
New Outbound MessageTriggers when an outbound message is created.
Trigger
Ticket Label AddedTriggers when a label is added to a conversation.
Action
Add internal note to ticketAdds an internal note (visible only to agents) to a Trengo ticket.
Action
Add ticketCreate a new support ticket.
Action
Add ticket labelAttaches an existing label to a Trengo ticket.
Action
Create a ContactCreates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.
Action
Create webhookSubscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.
Action
Delete contactDelete a contact by id.
Action
Delete ticketDelete a ticket by id.
Action
Find a ContactReturns the Trengo contacts that match the search term.
Action
Get contactRetrieve a single Trengo contact by its id.
Action
Get webhookFetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.
Action
List contactsList all contacts.
Action
List labelsLists the ticket labels defined in the Trengo account (first page).
Action
List ticketsReturns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.
Action
Send a MessageSends a reply message on an existing Trengo ticket, over the ticket's own channel.
Action
Update contactUpdate an existing contact by id.
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 Trengo
OpenAI to TrengoOpenAI's platform for text generation (Responses + Chat Completions), image generation (gpt-image-1 /...
CloudConvert to TrengoCloudConvert converts files between more than 200 supported formats: documents, image, spreadsheet...
elmah.io to TrengoCloud logging for .NET web applications using ELMAH.
Postman to TrengoPostman is a platform for building and testing APIs.
HubSpot to TrengoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TrengoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Questions
Azurevirtualmachines and Trengo, 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 Trengo when something happens in Azurevirtualmachines?
Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Trengo to Azurevirtualmachines?
Yes. When something happens in Trengo, your agent can act in Azurevirtualmachines too. This page covers both directions: Trengo's triggers and Azurevirtualmachines's actions are listed here as well.
Do I have to build a connector for Azurevirtualmachines or Trengo?
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 Trengo 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.