Integration
Connect Azurevirtualmachines to Omise
When New Virtual Machine fires in Azurevirtualmachines, your agent runs Add customer in Omise. 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 Omise 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 Omise
When New Virtual Machine in Azurevirtualmachines
then Add customer in Omise
When New Virtual Machine in Azurevirtualmachines
then Add charge in Omise
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 Omise
Triggers and actions 1 trigger · 37 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
Add chargeCreate a charge for an amount/currency against a card, customer, or source.
Action
Add customerCreate a customer, optionally attaching a card via token.
Action
Add recipientCreates a new transfer recipient (individual or corporation) with a destination bank account.
Action
Add refundCreate a refund on a captured charge.
Action
Add sourceCreates a payment source (PromptPay, internet banking, mobile banking, Alipay, installments, TrueMoney and other non-card methods) that can then be charged with Add charge.
Action
Add tokenCreates a single-use card token in Omise using the account's public key. Use the token to create one charge or to attach the card to a customer.
Action
Add transferCreates a transfer from your Omise balance to your own bank account or to a verified third-party recipient.
Action
Delete cardPermanently removes a saved card from an Omise customer.
Action
Delete customerDestroy a customer.
Action
Delete recipientDestroy a recipient.
Action
Get chargeRetrieves a single Omise charge by its ID.
Action
Get customerRetrieve a customer by id.
Action
Get disputeRetrieve a dispute by id.
Action
Get recipientRetrieve a recipient by id.
Action
Get refundRetrieve a refund by id.
Action
Get sourceRetrieve a payment source by id.
Action
Get tokenRetrieves a card token by its ID, including the card it represents and whether it has been used.
Action
Get transferRetrieves a single Omise transfer by its ID.
Action
List cardsReturns the list of cards saved on an Omise customer.
Action
List customersList all customers.
Action
List recipientsList all recipients.
Action
List transfersList all transfers.
Action
Update chargeUpdates the description and/or metadata of an existing Omise charge.
Action
Update customerUpdate a customer's details.
Action
Update disputeUpdate a dispute's message/status.
Action
Update recipientUpdate a recipient's details.
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 Omise
HubSpot to OmiseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to OmiseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to OmiseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to OmiseGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to OmiseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to OmiseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Azurevirtualmachines and Omise, 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 Omise when something happens in Azurevirtualmachines?
Any of Omise's 26 actions, including Update charge, Update customer, Update dispute and Update recipient. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Omise to Azurevirtualmachines?
Omise has no triggers in the catalog today, so automations start in Azurevirtualmachines. If you need the other direction, ask: your agent reads Omise's API documentation and adds it.
Do I have to build a connector for Azurevirtualmachines or Omise?
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 Omise 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.