AI agent for hh.ru (HeadHunter)
Connect hh.ru (HeadHunter) to your AI agent through the WorkAist MCP server.
Marketplace
Pre-built connector templates · install with one click.
- 1Install in one click
Pick hh.ru (HeadHunter) from the marketplace. WorkAist handles OAuth 2.0 and stores the credentials encrypted — no JSON keys to paste.
- 2Tools auto-generated
hh.ru (HeadHunter) exposes 6 MCP tools to every agent in your workspace: list_candidates, get_application, schedule_interview, list_jobs, and more. Each tool is a typed function, not a brittle script.
- 3Data flows to your graph
Historical recruiting records sync to your private knowledge graph. Agents query relationships across all connected sources, not just hh.ru (HeadHunter) in isolation.
- 4Your agents take action
Your AI agent picks the right tool, runs it under your access policies, and answers in plain language — with a full audit trail of every hh.ru (HeadHunter) call.
hh.ru (HeadHunter) is recruiting software built for businesses in Russia you can connect to WorkAist in minutes. Through the open MCP standard, your AI agents screen candidates, schedule interviews and keep records up to date — autonomously, under explicit permissions, with no manual hand-offs. hh.ru (HeadHunter) authenticates via OAuth, and because WorkAist is self-hosted under AGPL-3.0, your data never leaves your own infrastructure.
Authentication & setup
The hh.ru (HeadHunter) connector authenticates via OAuth 2.0.
WorkAist redirects you to the provider, you authorize, and the access token is encrypted and stored. No keys to copy.
Frequently paired with hh.ru (HeadHunter)
FAQ
Can a WorkAist AI agent really automate hh.ru (HeadHunter) end-to-end?▼
Yes. The connector exposes read and write tools through Model Context Protocol. AI agents call them through plain-language instructions in a CLAUDE.md file — no glue code.
How does this differ from using the hh.ru (HeadHunter) API directly?▼
The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents hh.ru (HeadHunter) as part of a unified Knowledge Graph alongside your other tools.
What does it cost?▼
WorkAist is open-source under AGPL-3.0 and self-hosted, so the connector itself is free. You pay only for hh.ru (HeadHunter)'s own API costs (if any) and the LLM tokens your agent consumes.
Is my hh.ru (HeadHunter) data sent to a third party?▼
No. WorkAist runs in your own infrastructure. Data flows from hh.ru (HeadHunter) → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.
What if hh.ru (HeadHunter) changes its API?▼
The connector is versioned and published openly. When hh.ru (HeadHunter) ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.