Integration
Connect Clockwork Recruiting to Azure Cosmos Db
When New Candidacy fires in Clockwork Recruiting, 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 Clockwork Recruiting 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 Clockwork Recruiting can start in Azure Cosmos Db
When New Candidacy in Clockwork Recruiting
then Create Document in Azure Cosmos Db
When New Person Record in Clockwork Recruiting
then Query Documents 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 Clockwork Recruiting and Azure Cosmos Db
Triggers and actions 6 triggers · 65 actions
Trigger
Candidate Status ChangeTriggers when a candidate's status changes on the chosen project.
Trigger
New CandidacyTriggers when a new candidate is added to the chosen project.
Trigger
New Person RecordTriggers when a new person record is added to your Clockwork firm.
Trigger
Updated CandidacyTriggers when any candidacy on the chosen project is updated.
Trigger
Updated Person RecordTriggers when a person record in your Clockwork firm is updated.
Trigger
Updated Person With VerbosityTriggers when a person record is updated, returning the person with their preferred email, phone, LinkedIn, address, primary position and tags.
Action
Create Person WebsiteCreate Person Website
Action
Delete a CandidateReturn status message
Action
Delete a PersonDelete Person.
Action
Delete a Person AddressDelete Address.
Action
Delete a Person AttachmentDelete attachment.
Action
Delete a Person CompensationDelete Compensation.
Action
Delete a Person EmailDelete EmailAddress.
Action
Delete a Person LinkedinDelete LinkedinUrl.
Action
Delete a Person NoteDelete Note.
Action
Delete Person EducationDelete Education.
Action
Delete Person Phone NumberDelete Phone Number.
Action
Delete Person PositionDelete Position.
Action
Delete Person WebsiteDelete Web Site.
Action
Find a CandidateReturns a single candidacy and the associated metadata.
Action
Find a CompanyReturns a single company and the associated metadata.
Action
Find a PersonReturns a single person and the associated metadata.
Action
Find a Person AddressReturns a single address and the associated metadata.
Action
Find a Person AttachmentReturns a single attachment.
Action
Find a Person CompensationReturns a single compensation and the associated metadata.
Action
Find a Person EmailReturns a single email address and the associated metadata.
Action
Find a Person NoteReturns a single note and the associated metadata.
Action
Find a ProjectReturns a single project and the associated metadata.
Action
Find a Project AdminReturns the project settings
Action
Find a Project ClientReturns a single client and the associated metadata.
Action
Find a Project UserReturns a single user and the associated metadata.
Action
Find a SchoolReturns a single school and the associated metadata.
Action
Find a TagReturns a single tag and the associated metadata.
Action
Find Person EducationReturns a single education and the associated metadata.
Action
Find Person LinkedinReturns a single linkedin_url and the associated metadata.
Action
Find Person Phone NumberReturns a single phone_number and the associated metadata.
Action
Find Person PositionReturns a single position and the associated metadata.
Action
Find Person WebsiteReturns a single web site and the associated metadata.
Action
Get All CompaniesReturns paginated companies data. Optionally filter the list by `name`, `do_not_contact`, and/or `associated_to_project`. Filters can be combined; omitting all of them returns every company.
Action
Get All PeopleReturns the list of all People of a Firm
Action
Get All SchoolsReturns paginated schools data
Action
Get All TagsReturns the tags defined in your Clockwork firm.
Action
People SearchReturns the list of all People of a Firm
Action
Update a CandidateReturn updated candidate
Action
Update a CompanyReturns a single company and the associated metadata.
Action
Update a Person EducationReturns a single education and the associated metadata.
Action
Update a TagReturns a single tag and the associated metadata.
Action
Update PersonReturns a single person and the associated metadata.
Action
Update Person AddressReturns a single address and the associated metadata.
Action
Update Person CompensationReturns a single compensation and the associated metadata.
Action
Update Person EmailReturns a single email address and the associated metadata.
Action
Update Person LinkedinReturns a single linkedin_url and the associated metadata.
Action
Update Person NoteReturns a single note and the associated metadata.
Action
Update Person Phone NumberReturns a single phone_number and the associated metadata.
Action
Update Person PositionReturns a single position and the associated metadata.
Action
Update Person WebsiteReturns a single web site and the associated metadata.
Action
Update SchoolReturns a single school and the associated metadata.
Action
Create ContainerCreates a new container in a Cosmos DB database, partitioned on the property you choose.
Action
Create DatabaseCreates a new database in the Azure Cosmos DB account, optionally with shared provisioned throughput.
Action
Create DocumentCreates a new document in a Cosmos DB container, or replaces an existing one with the same id when upsert is on.
Action
Delete ContainerDeletes a container, and every document in it, from a Cosmos DB database.
Action
Delete DatabaseDeletes a database, and every container and document in it, from the Azure Cosmos DB account.
Action
Delete DocumentDeletes one document from a Cosmos DB container.
Action
Get ContainerReturns one container in a Cosmos DB database, including its partition key and indexing policy.
Action
Get DatabaseReturns one database in the Azure Cosmos DB account by its name.
Action
Get DocumentReturns one document from a Cosmos DB container by its id and partition key.
Action
List ContainersReturns every container in a Cosmos DB database.
Action
List DatabasesReturns every database in the Azure Cosmos DB account.
Action
List DocumentsReturns the documents in a Cosmos DB container.
Action
Query DocumentsRuns a Cosmos DB SQL query against a container and returns the matching documents.
Action
Replace DocumentReplaces 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 Clockwork Recruiting
Clockwork Recruiting to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Clockwork Recruiting to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Clockwork Recruiting to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Clockwork Recruiting to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Clockwork Recruiting to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Clockwork Recruiting to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
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
Clockwork Recruiting and Azure Cosmos Db, answered
What can start an automation from Clockwork Recruiting?
Any of Clockwork Recruiting's 6 triggers in the catalog, including New Candidacy, New Person Record, Updated Candidacy and Updated Person Record. 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 Clockwork Recruiting?
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 Clockwork Recruiting?
Azure Cosmos Db has no triggers in the catalog today, so automations start in Clockwork Recruiting. 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 Clockwork Recruiting 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 Clockwork Recruiting 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.