Integration
Connect Hyros to Azure Cosmos Db
When New Call fires in Hyros, your agent runs Create Document in Azure Cosmos Db. 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 Hyros and Azure Cosmos Db 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 Hyros can start in Azure Cosmos Db
When New Call in Hyros
then Create Document in Azure Cosmos Db
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 Hyros and Azure Cosmos Db
Triggers and actions 5 triggers · 47 actions
- New Call
Triggers when a new call is recorded in HYROS.
- New Lead
Triggers when a new lead is created in HYROS.
- New Sale
Triggers when a new sale is recorded in HYROS.
- New Sale Attributed
Triggers when a new sale is recorded and attributed in Hyros.
- New Subscription
Triggers when a new subscription is recorded in HYROS.
- Create Call
Records a call for a lead.
- Create Cart
Creates a cart for a lead.
- Create Click
Records a tracked click for a lead, for attribution.
- Create Custom Cost
Adds a custom cost, such as a recurring fee, to the sources it applies to.
- Create Lead
Creates a lead in HYROS, or updates it if it already exists, and applies tags and a stage.
- Create Order
Creates an order with one or more items for a lead, which records the sale in HYROS.
- Create Product
Creates a product, so sales tagged with it are tracked.
- Create Source
Creates a traffic source.
- Create Subscription
Creates a subscription for a lead.
- Delete Call
Deletes a call.
- Delete Sale
Deletes a sale.
- Find Lead Clicks
Returns the tracked clicks of a lead.
- Find Leads
Finds leads by ID, email or creation date.
- Find Sales
Finds sales by ID, email, lead, product tag or date.
- Find Subscriptions
Finds subscriptions by ID, email, lead, product tag, status or date.
- Get Ad Accounts Attribution Report
Returns sales, revenue, cost and other attribution figures per ad account.
- Get Ads Attribution Report
Returns sales, revenue, cost and other attribution figures per ad, ad set or campaign.
- Get Lead Journey
Returns the attribution journey of one or more leads: their sales and the sources that led to them.
- Get User Info
Returns the profile of the account the API key belongs to.
- List Ads
Returns the ads HYROS tracks for an ad platform.
- List Domains
Returns the domains configured in the account.
- List Keywords
Returns the keywords of a Google ad group.
- List Lead Stages
Returns the lead stages in the account.
- List Sources
Returns the traffic sources in the account.
- List Tags
Returns every tag in the account.
- Refund Order
Refunds an order and updates the income of its lead.
- Retrieve Calls
Finds calls by ID, email, lead, product tag, qualification or date.
- Update Call
Updates the name, state or qualification of calls.
- Update Cart
Updates a cart and the lead it belongs to.
- Update Lead
Updates a lead, found by its ID, email or phone, including its tags and stage.
- Update Order
Updates the items and totals of an order.
- Update Sale
Marks sales as refunded or recurring.
- Update Subscription
Updates the status, dates or name of subscriptions.
- Create Container
Creates a new container in a Cosmos DB database, partitioned on the property you choose.
- Create Database
Creates a new database in the Azure Cosmos DB account, optionally with shared provisioned throughput.
- Create Document
Creates a new document in a Cosmos DB container, or replaces an existing one with the same id when upsert is on.
- Delete Container
Deletes a container, and every document in it, from a Cosmos DB database.
- Delete Database
Deletes a database, and every container and document in it, from the Azure Cosmos DB account.
- Delete Document
Deletes one document from a Cosmos DB container.
- Get Container
Returns one container in a Cosmos DB database, including its partition key and indexing policy.
- Get Database
Returns one database in the Azure Cosmos DB account by its name.
- Get Document
Returns one document from a Cosmos DB container by its id and partition key.
- List Containers
Returns every container in a Cosmos DB database.
- List Databases
Returns every database in the Azure Cosmos DB account.
- List Documents
Returns the documents in a Cosmos DB container.
- Query Documents
Runs a Cosmos DB SQL query against a container and returns the matching documents.
- Replace Document
Replaces the whole body of an existing document in a Cosmos DB container.
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 Hyros
Hyros to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Hyros to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Hyros to MailchimpMailchimp marketing automation and email platform.
Hyros to StripeStripe is a payment processing platform for online businesses.
Hyros to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Hyros to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Azure Cosmos Db
HubSpot to Azure Cosmos DbHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Azure Cosmos DbGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Azure Cosmos DbGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Azure Cosmos DbGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Hyros and Azure Cosmos Db, answered
What can start an automation from Hyros?
Any of Hyros's 5 triggers in the catalog, including New Call, New Lead, New Sale and New Sale Attributed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Azure Cosmos Db when something happens in Hyros?
Any of Azure Cosmos Db's 14 actions, including Create Container, Create Database, Create Document and Get Container. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Azure Cosmos Db to Hyros?
Azure Cosmos Db has no triggers in the catalog today, so automations start in Hyros. If you need the other direction, ask: your agent reads Azure Cosmos Db's API documentation and adds it.
Do I have to build a connector for Hyros or Azure Cosmos Db?
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 Hyros and Azure Cosmos Db 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.