Integration
Connect Azure Key Vault to Omise
When New Secret fires in Azure Key Vault, 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 Azure Key Vault 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 Azure Key Vault can start in Omise
When New Secret in Azure Key Vault
then Add customer 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 Azure Key Vault and Omise
Triggers and actions 1 trigger · 34 actions
- New Secret
Triggers when a new secret is added to your key vault.
- Delete Secret
Deletes a secret and all its versions. If the vault has soft-delete on, the secret can still be recovered until it is purged.
- Get Deleted Secret
Returns the details of a secret that was deleted but not yet purged, including when it will be permanently removed.
- Get Secret
Returns a secret's value and details, either the latest version or a specific one.
- List Secrets
Returns the secrets in your key vault with their details (not their values).
- Purge Deleted Secret
Permanently removes a deleted secret so it cannot be recovered and its name can be reused.
- Recover Deleted Secret
Restores a deleted secret, with all its versions, before it is purged.
- Set Secret
Stores a secret in your key vault. If a secret with that name already exists, a new version of it is created.
- Update Secret Properties
Changes a secret's settings (enabled, content type, expiry, tags) without changing its value.
- Add charge
Create a charge for an amount/currency against a card, customer, or source.
- Add customer
Create a customer, optionally attaching a card via token.
- Add recipient
Creates a new transfer recipient (individual or corporation) with a destination bank account.
- Add refund
Create a refund on a captured charge.
- Add source
Creates a payment source (PromptPay, internet banking, mobile banking, Alipay, installments, TrueMoney and other non-card methods) that can then be charged with Add charge.
- Add token
Creates 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.
- Add transfer
Creates a transfer from your Omise balance to your own bank account or to a verified third-party recipient.
- Delete card
Permanently removes a saved card from an Omise customer.
- Delete customer
Destroy a customer.
- Delete recipient
Destroy a recipient.
- Get charge
Retrieves a single Omise charge by its ID.
- Get customer
Retrieve a customer by id.
- Get dispute
Retrieve a dispute by id.
- Get recipient
Retrieve a recipient by id.
- Get refund
Retrieve a refund by id.
- Get source
Retrieve a payment source by id.
- Get token
Retrieves a card token by its ID, including the card it represents and whether it has been used.
- Get transfer
Retrieves a single Omise transfer by its ID.
- List cards
Returns the list of cards saved on an Omise customer.
- List customers
List all customers.
- List recipients
List all recipients.
- List transfers
List all transfers.
- Update charge
Updates the description and/or metadata of an existing Omise charge.
- Update customer
Update a customer's details.
- Update dispute
Update a dispute's message/status.
- Update recipient
Update 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 Azure Key Vault
Azure Key Vault to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Azure Key Vault to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Azure Key Vault to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Azure Key Vault to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Azure Key Vault to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Azure Key Vault to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Omise
Questions
Azure Key Vault and Omise, answered
What can start an automation from Azure Key Vault?
Any of Azure Key Vault's 1 trigger in the catalog, including New Secret. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Omise when something happens in Azure Key Vault?
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 Azure Key Vault?
Omise has no triggers in the catalog today, so automations start in Azure Key Vault. 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 Azure Key Vault 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 Azure Key Vault 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.