Integration
Connect folk to Azure Cosmos Db
When Company Added fires in folk, 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 folk 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 folk can start in Azure Cosmos Db
When Company Added in folk
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 folk and Azure Cosmos Db
Triggers and actions 11 triggers · 30 actions
- Company Added
Triggers when a new company is created or added to a group.
- Company Custom Field Updated
Triggers when a company custom field (for example tag, status, text, assignee) is updated.
- Company Removed
Triggers when a company is deleted from the workspace or removed from a group.
- Company Updated
Triggers when a company basic field (like name, email or URL) in a group is updated.
- Deal Added
Fires when a new deal is created.
- Deal Removed
Fires when a deal is deleted from a pipeline.
- Deal Updated
Fires when a deal is updated (stage change, field update).
- Person Added
Triggers when a new person is created or added to a group.
- Person Custom Field Updated
Triggers when a person custom field (for example tag, status, text, assignee) is updated.
- Person Removed
Triggers when a person is deleted from the workspace or removed from a group.
- Person Updated
Triggers when a person basic field (like first name, job title, email or URL) in a group is updated.
- Create Company
Creates a company in folk, optionally adding it to a group and setting that group's custom fields.
- Create Deal
Creates a deal in a folk group, optionally linked to companies and people, and sets that deal type's custom fields.
- Create Group
Creates a group in folk. A default "All people" table view is added to the group automatically.
- Create Note
Creates a note on a folk person, company or deal. Optionally posts it as a reply to an existing note.
- Create Person
Creates a person in folk, optionally adding them to a group and setting that group's custom fields.
- Create Reminder
Creates a reminder on a folk person, company or deal, scheduled with an iCalendar recurrence rule.
- Delete Company
Deletes a company from folk by its id.
- Delete Person
Deletes a person from folk by their id. This also removes their custom fields, notes and associations.
- Find a Company
Searches folk companies by name, email or website and returns the matches, with the first one broken out for easy mapping.
- Find a Person
Searches folk people by email, full name or phone and returns the matches, with the first one broken out for easy mapping.
- Get a Company
Fetches one folk company by id, including its custom field values.
- Get a Note
Fetches one folk note by id, with its text, author and the record it is attached to.
- Get a Person
Fetches one folk person by id, including their custom field values.
- List Groups
Returns the groups in the folk workspace, with each group's id, name and visibility.
- Update Company
Updates a folk company. Only the fields you fill in are changed; list fields such as emails replace the whole list.
- Update Person
Updates a folk person. Only the fields you fill in are changed; list fields such as emails replace the whole list.
- 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 folk
folk to OpenRouterOpenRouter is a unified interface to AI models.
folk to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
folk to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
folk to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
folk to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
folk to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Azure Cosmos Db
Google Calendar to Azure Cosmos DbGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
folk and Azure Cosmos Db, answered
What can start an automation from folk?
Any of folk's 11 triggers in the catalog, including Company Added, Company Custom Field Updated, Company Removed and Company Updated. 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 folk?
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 folk?
Azure Cosmos Db has no triggers in the catalog today, so automations start in folk. 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 folk 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 folk 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.