Integration
Connect Azurevirtualmachines to Dwolla
When New Virtual Machine fires in Azurevirtualmachines, your agent runs Add customer in Dwolla. 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 Dwolla 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 Dwolla
When New Virtual Machine in Azurevirtualmachines
then Add customer in Dwolla
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 Dwolla
Triggers and actions 1 trigger · 30 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.
- Add beneficial owner
Adds a beneficial owner (an individual owning 25% or more) to a verified business customer, identified by SSN for US owners or by passport for non-US owners.
- Add customer
Creates a Dwolla customer — receive-only, unverified, verified personal, or verified business.
- Add document
Uploads an identity verification document (passport, license, ID card) for a Dwolla customer.
- Add funding source
Creates a bank account, virtual account number or debit card funding source for a Dwolla customer.
- Add mass payment
Creates a mass payment that sends up to 5,000 individual payments from one Dwolla funding source in a single batch.
- Add transfer
Initiates a Dwolla transfer of money from one funding source to another, returning the new transfer's id and link.
- Cancel transfer
Cancels a pending Dwolla transfer and returns the updated transfer.
- Delete funding source
Removes a bank or debit card funding source in Dwolla. The funding source is soft deleted and stays readable, marked as removed.
- Find customers
Searches Dwolla customers by name, business name or email, optionally filtered by verification status.
- Get customer
Returns a Dwolla customer's details, including name, email, type and verification status.
- Get funding source
Returns a Dwolla funding source (bank account or balance) by its ID, including its type, status and bank details.
- Get funding source balance
Returns the current balance of a Dwolla funding source — balance and total for a Dwolla balance, available and closing for a bank account, available for a settlement account.
- Get mass payment
Returns a Dwolla mass payment by its ID, including its processing status (pending, processing or complete), creation date, totals and metadata.
- List beneficial owners
Returns all beneficial owners associated with a business verified Dwolla customer.
- List documents
Returns all identity verification documents submitted for a Dwolla customer, including their type, review status and verification result.
- List events
Returns the recent events (state changes to customers, transfers, funding sources and more) in your Dwolla application, newest first.
- List funding sources
Returns all funding sources for a Dwolla customer, including bank accounts, debit cards and the Dwolla balance, with their verification status.
- List transfers
Returns the transfers for a Dwolla customer, optionally filtered by amount range, date range, status, correlation ID or a name/email search.
- Update customer
Updates a Dwolla customer's information, upgrades or retries verification, or suspends, deactivates or reactivates 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 Dwolla
Questions
Azurevirtualmachines and Dwolla, 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 Dwolla when something happens in Azurevirtualmachines?
Any of Dwolla's 19 actions, including Update customer, Add beneficial owner, Add customer and Add document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Dwolla to Azurevirtualmachines?
Dwolla has no triggers in the catalog today, so automations start in Azurevirtualmachines. If you need the other direction, ask: your agent reads Dwolla's API documentation and adds it.
Do I have to build a connector for Azurevirtualmachines or Dwolla?
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 Dwolla 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.