Integration
Connect Vitally to Azure Cosmos Db
When Customer Created fires in Vitally, 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 Vitally 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Vitally can start in Azure Cosmos Db
When Customer Created in Vitally
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 Vitally and Azure Cosmos Db
Triggers and actions 8 triggers · 34 actions
- Customer Created
Triggers when a new account (customer) is created in Vitally.
- Custom Object Instance Created
Triggers when a new instance of a custom object is created.
- Custom Object Instance Updated
Triggers when an instance of a custom object is created or updated.
- Note Created
Triggers when a new note is created in Vitally.
- NPS Response Created
Triggers when a new NPS response is recorded in Vitally.
- Organization Created
Triggers when a new organization is created in Vitally.
- Project Created
Triggers when a new project is created in Vitally.
- Task Created
Triggers when a new task is created in Vitally.
- Create Account
Creates an account (customer) in Vitally, identified by your own external ID.
- Create Note
Creates a note on an account or organization in Vitally.
- Create NPS Response
Records an NPS survey response from a user in Vitally.
- Create Organization
Creates an organization in Vitally, identified by your own external ID.
- Create Project From Template
Creates a project for an account or organization from a project template.
- Create Task
Creates a task on an account or organization in Vitally.
- Create User
Creates a user in Vitally and links them to accounts or organizations.
- Find a Customer
Returns a account by its Vitally ID or external ID.
- Find a Custom Object Instance
Finds a custom object instance by ID, external ID, linked account or a custom field value.
- Find a Note
Returns a note by its Vitally ID or external ID.
- Find a Organization
Returns a organization by its Vitally ID or external ID.
- Find a Task
Returns a task by its Vitally ID or external ID.
- Find a Teammate
Finds a Vitally team member by email address.
- Find a User
Finds a user by email address, external ID or email domain.
- Get Account Health Scores
Returns an account's health score and its breakdown.
- Update Customer Traits
Updates the name or traits of a account in Vitally; traits are merged with existing ones.
- Update Organization Traits
Updates the name or traits of a organization in Vitally; traits are merged with existing ones.
- Update Project Status
Changes a project's status in Vitally.
- Update Task
Updates a task in Vitally, for example to reassign or complete it.
- Update User Traits
Updates the name or traits of a user in Vitally; traits are merged with existing ones.
- 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 Vitally
Vitally to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Vitally to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Vitally to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Vitally to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Vitally to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Vitally to AnthropicAnthropic builds Claude, a family of large language models.
More into Azure Cosmos Db
HubSpot to Azure Cosmos DbHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Azure Cosmos DbSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Azure Cosmos DbSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
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
Vitally and Azure Cosmos Db, answered
What can start an automation from Vitally?
Any of Vitally's 8 triggers in the catalog, including Customer Created, Custom Object Instance Created, Custom Object Instance Updated and Note Created. 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 Vitally?
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 Vitally?
Azure Cosmos Db has no triggers in the catalog today, so automations start in Vitally. 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 Vitally 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 Vitally 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.