Integration
Connect ComplyCube to Azure Cosmos Db
When Check Completed fires in ComplyCube, 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 ComplyCube 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 ComplyCube can start in Azure Cosmos Db
When Check Completed in ComplyCube
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 ComplyCube and Azure Cosmos Db
Triggers and actions 2 triggers · 53 actions
- Check Completed
Triggers when a new check is received.
- New Event
Triggers when a new event is received.
- Add Note
Add a note to a client for investigations, reviews, or compliance reporting.
- Create Address
Creates a new address for a client.
- Create Check
Create a verification check (identity, document, AML, or other check type) against a client.
- Create Client
Updates clients details using the given input.
- Create Document
Creates a new document for a client.
- Create Session
Creates a verification session link using workflow templates.
- Delete Address
Deletes an existing address.
- Delete Client
Deletes an existing client.
- Delete Document
Deletes an existing document.
- Delete Note
Delete a note.
- Find Addresses
Search and verify an address for KYC address checks.
- Find Companies
Search for companies by name or registration details for KYB checks.
- Generate Check Report
Generate a PDF report for a specific check.
- Generate Client Report
Generate a PDF report summarizing a client's compliance record.
- Generate Session Report
Generates a session report PDF and returns it as a file for use in later Zap steps.
- Generate Token
Generate an SDK token to securely authenticate a frontend user session.
- Get Address
Retrieves an address using "Address ID".
- Get Check Results
Retrieves a check's results using "Check ID".
- Get Client
Retrieves a client's results using "Client ID".
- Get Company Details
Retrieve detailed information about a company by its ID.
- Get Document
Retrieves a document using "Document ID".
- Get Live Photo
Retrieve a client's live photo by ID.
- Get Note
Retrieve a note by ID.
- Get Risk Profile
Retrieve a client's AML risk profile and score.
- Get Session Results
Retrieves a session's results using "Session ID".
- List Addresses
List addresses linked to a client.
- List Checks
List checks performed on a client.
- List Clients
List clients with optional filters and pagination.
- List Documents
List documents linked to a client.
- List Live Photos
List a client's live photos.
- List Notes
List notes linked to a client.
- List Workflow Sessions
List a client's workflow sessions.
- Update Address
Updates an existing address.
- Update Check
Update an existing check's parameters.
- Update Client
Updates clients details using the given input.
- Update Document
Updates an existing document.
- Update Note
Update an existing note.
- Upload Document Image
Uploads an image attachment (front or back) to an existing document.
- Upload Live Photo
Upload a client's live photo (selfie) for biometric identity and liveness verification.
- 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 ComplyCube
ComplyCube to Azure SqlManaged cloud SQL Server database service for storing, querying, and managing relational data at scale.
ComplyCube to GamerPowerGamerPower tracks live game giveaways, free game keys, loot drops and beta access across PC, console and...
ComplyCube to ScraperAPIScraperAPI is a data extraction service that transforms websites into structured, automation-ready data
ComplyCube to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
ComplyCube to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ComplyCube to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into Azure Cosmos Db
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
ComplyCube and Azure Cosmos Db, answered
What can start an automation from ComplyCube?
Any of ComplyCube's 2 triggers in the catalog, including Check Completed and New Event. 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 ComplyCube?
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 ComplyCube?
Azure Cosmos Db has no triggers in the catalog today, so automations start in ComplyCube. 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 ComplyCube 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 ComplyCube 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.