Integration
Connect Azurevirtualmachines to Landbot
When New Virtual Machine fires in Azurevirtualmachines, your agent runs Send text message in Landbot. 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 Landbot 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 Landbot
When New Virtual Machine in Azurevirtualmachines
then Send text message in Landbot
When New Virtual Machine in Azurevirtualmachines
then Update customer field in Landbot
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 Landbot
Triggers and actions 1 trigger · 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.
Action
Archive customerArchives a Landbot customer so their conversation moves out of the active inbox.
Action
Assign customer to agentAssigns a Landbot customer conversation to a specific agent.
Action
Assign customer to botAssigns a Landbot customer to a bot, optionally starting the bot right away or from a specific node.
Action
Delete customerDeletes a Landbot customer.
Action
Find customers by name, email or phoneFinds customers whose name, email or phone starts with the text you give. Returns up to 100 matching customers.
Action
Get channelReturns a Landbot channel's details, including its name, type, active status and appearance settings.
Action
Get customerReturns a Landbot customer's profile, including name, channel, assigned agent, archive status and custom field values.
Action
Get customer fieldReturns the name, type and current value of one custom field stored on a Landbot customer.
Action
List channelsReturns the channels in your Landbot workspace, optionally filtered by type and active status.
Action
List customer messagesReturns the full conversation transcript for a Landbot customer — every message exchanged with them.
Action
List customersReturns the customers in your Landbot workspace, optionally filtered by channel, assigned agent, archive or WhatsApp opt-in status, or a name/email/phone prefix.
Action
List WhatsApp templatesReturns the WhatsApp message templates available to send to customers, optionally limited to one channel.
Action
Send text messageSends a text message to a Landbot customer on their channel.
Action
Send WhatsApp templateSends an approved WhatsApp template message to a Landbot customer, filling in its placeholders. Use it to reach a customer outside WhatsApp's 24-hour messaging window.
Action
Update customer fieldChanges the value of an existing custom field on a Landbot customer. The field must already exist on the customer.
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 Landbot
HubSpot to LandbotHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LandbotSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LandbotSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LandbotGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LandbotGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LandbotGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Azurevirtualmachines and Landbot, 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 Landbot when something happens in Azurevirtualmachines?
Any of Landbot's 15 actions, including Send text message, Send WhatsApp template, Update customer field and Assign customer to agent. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Landbot to Azurevirtualmachines?
Landbot has no triggers in the catalog today, so automations start in Azurevirtualmachines. If you need the other direction, ask: your agent reads Landbot's API documentation and adds it.
Do I have to build a connector for Azurevirtualmachines or Landbot?
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 Landbot 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.