Recruitee connector for AI agents

Tools your recruiting agent reaches for on Recruitee, scoped per user.

CALL ANY TOOL

53 tools for recruiting in Recruitee: candidates, job offers, talent pools, pipeline stages, requisitions, notes, tags, and tasks, with publish, close, and disqualify actions.

recruitee_add_candidate_followers

Add candidate followers

Add team members as followers of a Recruitee candidate so they receive updates about that candidate. Returns the candidate record with its updated followers. Use add_candidate_followers to subscribe people. Get admin IDs from recruitee_list_admins.

Parameters

Name

Type

Required

Description

admin_ids

array

Required

IDs of the admins (team members) who should follow the candidate. Get them from recruitee_list_admins.

integer

Required

Numeric ID of the Recruitee candidate. Get it from recruitee_list_candidates or recruitee_search_candidates.

recruitee_add_candidate_sources

Add candidate sources

recruitee_archive_offer

Archive offer

recruitee_change_placement_stage

Change placement stage

recruitee_close_offer

Close offer

recruitee_create_candidate

Create candidate

recruitee_create_candidate_note

Create candidate note

recruitee_create_location

Create location

recruitee_create_placement

Create placement

recruitee_delete_candidate

Delete candidate

recruitee_delete_note

Delete note

recruitee_disqualify_placement

Disqualify placement

recruitee_get_candidate

Get candidate

recruitee_get_department

Get department

recruitee_get_offer

Get offer

recruitee_get_pipeline_template

Get pipeline template

recruitee_get_talent_pool

Get talent pool

recruitee_list_admins

List admins

recruitee_list_candidate_attachments

List candidate attachments

recruitee_list_candidate_tasks

List candidate tasks

recruitee_list_disqualify_reasons

List disqualify reasons

recruitee_list_offer_placements

List offer placements

recruitee_list_requisitions

List requisitions

recruitee_list_tags

List tags

recruitee_publish_offer

Publish offer

recruitee_remove_candidate_tags

Remove candidate tags

recruitee_search_candidates

Search candidates

recruitee_unarchive_offer

Unarchive offer

recruitee_update_candidate

Update candidate

recruitee_update_offer

Update offer

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Recruitee tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["recruitee"], toolNames: [
    "recruitee_list_offers",
    "recruitee_list_offer_placements",
    "recruitee_change_placement_stage"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Move Maria Lopez to the Offer stage for the Product Designer job" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["recruitee"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Move Maria Lopez to the Offer stage for the Product Designer job" }],
  tools,
});

// Execute the tool call with the user's vaulted Recruitee access token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["recruitee"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Move Maria Lopez to the Offer stage for the Product Designer job" }],
  tools,
});

// Tool call runs with the user's vaulted Recruitee access token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["recruitee"] }, pageSize: 100,
});

const agent = new Agent({
  name: "recruiting_agent",
  model: "gemini-2.5-pro",
  instruction: "Recruitee tools scoped to this user",
  tools,
});

await agent.run("Move Maria Lopez to the Offer stage for the Product Designer job");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Recruitee tool. Click to copy, paste into your agent, done.

Candidates

Copy the prompt

Copied

Search candidates tagged python who applied this month.

Copy the prompt

Copied

Create a candidate for Jordan Lee and add them to the Sales Engineer job.

Copy the prompt

Copied

Add the tags referral and senior to Priya Shah.

Pipeline

Copy the prompt

Copied

Move Maria Lopez to the Offer stage for the Product Designer job.

Copy the prompt

Copied

Disqualify Sam Lee from the Data Analyst job with the reason Overqualified.

Copy the prompt

Copied

Show the pipeline for the Sales Engineer job and who is in each stage.

Jobs and tasks

Copy the prompt

Copied

Publish the Customer Success Manager job.

Copy the prompt

Copied

Close the Backend Engineer job to new applications.

Copy the prompt

Copied

Create a task for Alex to call Priya Shah's references by Friday.

SEE HOW AUTH WORKS

Each user connects their own Recruitee access token once, and Scalekit sends it with every call. Access tokens stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Recruitee

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Recruitee

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Recruitee

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Recruitee

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other recruiting and HR connectors.

People Ops and HR teams

Offer letter routing agent

Drafts the offer in PandaDoc, blocks on the hiring manager's approval in Slack, then emails the candidate their e-signature link. Every call runs as the recruiter who triggered it, never a shared HR bot.

Support and Ops Teams

Meeting prep

Pulls agenda, participant context, and open action items before every meeting.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Recruitee access token looks fine in a demo. In production every stage move and disqualification looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Recruitee today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Recruitee as the user or through a shared token?

As the user. Each user connects their own Recruitee access token once, and Scalekit sends it with every call. Stage moves, notes, and tasks the agent records are attributed to that user in your audit trail, not a shared service account.

Where is the Recruitee access token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new access token. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Recruitee?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the candidate and pipeline read tools without recruitee_delete_candidate, which deletes a candidate, or recruitee_publish_offer. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Recruitee access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

What is an offer in Recruitee?

In Recruitee an offer is a job opening or a talent pool, not an offer letter. recruitee_list_offers returns both, recruitee_list_offer_placements shows the candidates in each pipeline stage, and recruitee_change_placement_stage moves a candidate between stages.