Integration

Taleez integration

Taleez is a French applicant tracking system (ATS). Read and filter job offers with their hiring steps, status history and application questions, list, create and update candidates, set their custom properties, attach documents, add candidates to jobs or talent pools, submit applications to a job or to the spontaneous application form, and read units, recruiters, pools, calendar events and property definitions. Candidate tools read and write personal data (names, e-mail, phone, CV, home location). The deprecated document upload route is not exposed, and the API offers no way to delete records or edit job offers. Authentication is a secret key, generated in the Taleez account settings under API & Webhooks and sent in the X-taleez-api-secret header; each key reaches only the scopes enabled for it there.

Connect Taleez How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Taleez.Built from the 34 Taleez tools below, on the connection you add once.

What you can do with Taleez

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Candidate, 7 operations

add_candidates_to_jobAdd candidates to jobPOSTLinks existing candidates to a job offer, without answers to its questions (use create_job_application for that). Workflows, automatic e-mails and webhooks are not triggered. Scope job.candidates.add.
add_candidates_to_poolAdd candidates to poolPOSTAdds existing candidates to a talent pool. Needs the pool.candidates.add scope on the key.
create_candidateCreate candidatePOSTCreates a candidate from personal details (sourcing) and returns its id. To apply someone to a job with answers, use create_job_application. Workflows, automatic e-mails and webhooks are not triggered. Scope candidate.create.
get_candidateGet candidateGETReturns one candidate: names, mail, phone, CV URL, language, social links, unit, place of residence and property values. Needs the candidate.get scope on the key.
list_candidatesList candidatesGETLists the company's candidates with their personal data (names, e-mail, phone, CV link, social links, home location) in 0-based pages of up to 1000. Filter by e-mail; withProps adds property values. Scope candidates.list.
list_pool_candidatesList pool candidatesGETLists the candidates of a talent pool with their personal data (names, e-mail, phone, CV link, social links, home location) in 0-based pages of up to 1000; withProps adds property values. Scope pool.candidates.list.
update_candidateUpdate candidatePOSTUpdates a candidate's names, mail, phone, social links and location; firstName and lastName are always required. An empty object for socialLinks or location clears it. Scope candidates.update.

Application, 3 operations

create_job_applicationCreate job applicationPOSTApplies a candidate to a job with answers to its questions (list_job_questions). A candidate with the same e-mail gets the application, else one is created. Workflows, e-mails, webhooks are not triggered.
create_spontaneous_applicationCreate spontaneous applicationPOSTSubmits a spontaneous application (not tied to a job) with answers to the spontaneous form (list_spontaneous_questions). A candidate with the same e-mail gets it, else one is created. Scope spontaneous.application.create.
list_candidate_applicationsList candidate applicationsGETLists a candidate's applications (spontaneous, applied to a job, or associated to a job) with job, current step, rejected, processed and hired dates and step history. Scope candidate.applications.list.

Job, 3 operations

add_candidate_to_jobsAdd candidate to jobsPOSTLinks an existing candidate to one or more jobs, without answers to job questions (use create_job_application for that). Workflows, automatic e-mails and webhooks are not triggered. Scope candidate.jobs.add.
get_jobGet jobGETReturns one job offer: title, status, contract, location, company, tags, public and apply URLs, descriptions and property values. Needs the job.get scope on the key.
list_jobsList jobsGETLists job offers in 0-based pages, filtered by unit, status, contract, city, company label, tag or visibility; several values of one filter mean OR. withDetails adds descriptions. Scope jobs.list.

Pool, 3 operations

add_candidate_to_poolsAdd candidate to poolsPOSTAdds an existing candidate to one or more talent pools. Needs the candidate.pools.add scope on the key.
list_candidate_poolsList candidate poolsGETLists the talent pools a candidate belongs to, with the date added, the recruiter who added the candidate and the source (referer). Needs the candidate.pools.list scope on the key.
list_poolsList poolsGETLists the company's talent pools in 0-based pages: id, name, creation timestamp and owning recruiter. Needs the pools.list scope on the key.

Candidate property, 2 operations

get_candidate_propertyGet candidate propertyGETReturns one candidate property definition: type, choices, translations, whether it is locked or admin-only, and how many candidates have a value. Needs the candidate-property.get scope on the key.
list_candidate_propertiesList candidate propertiesGETLists the candidate property definitions (custom fields) of the company: id, name, type, apiKey, choices and translations. withDisabled adds disabled ones. Needs the candidate-properties.list scope on the key.

Document, 2 operations

add_candidate_documentAdd candidate documentPOSTUploads a file (pdf, doc, docx, rtf, odt, jpeg, png or pages) to a candidate and returns the document id. Uploading the same content again only renames it. Needs the candidate.documents.add scope.
list_candidate_documentsList candidate documentsGETLists the documents attached to a candidate: id, name, URL, size in bytes and creation timestamp. Needs the candidate.documents.list scope on the key.

Event, 2 operations

list_candidate_eventsList candidate eventsGETLists the calendar events of a candidate: start and end timestamps, subject, location, meeting URL, organizer, attendees and attached files. Needs the candidate.events.list scope on the key.
list_eventsList eventsGETLists the company's calendar events in 0-based pages: start and end timestamps, subject, location, meeting URL, organizer, attendees and files. Needs the events.list scope on the key.

Job property, 2 operations

get_job_propertyGet job propertyGETReturns one job property definition with its choices, translations, the number of jobs that have a value and who last updated it. Needs the job.property.get scope on the key.
list_job_propertiesList job propertiesGETLists the job property definitions (custom fields) of the company: id, name, type, apiKey, choices, translations and whether candidates see it. Needs the job.properties.list scope on the key.

Property, 2 operations

get_candidate_propertiesGet candidate propertiesGETReturns a candidate's property values: per property its id, type, text value, selected choices (with star ratings) or linked document. Needs the candidate.properties.list scope on the key.
update_candidate_propertiesUpdate candidate propertiesPOSTSets property values on a candidate: a text or date value, choice ids (replaced or appended), star ratings or an existing document id. Ids come from list_candidate_properties. Scope candidate.properties.update.

Question, 2 operations

list_job_questionsList job questionsGETLists the application questions of a job: id, order, label, type, whether an answer is required, and the choices of choice questions; the answers of create_job_application refer to them. Scope job.questions.list.
list_spontaneous_questionsList spontaneous questionsGETLists the questions of the spontaneous application form: id, order, label, type, whether an answer is required, and choices. Needs the spontaneous.questions.list scope on the key.

Filter, 1 operation

count_jobs_by_filterCount jobs by filterGETReturns the total number of jobs and the job counts per status, contract type, city, tag and company label (only values that have at least one job). Needs the jobs.filtered-counts scope.

Recruiter, 1 operation

list_recruitersList recruitersGETLists the recruiters (users) of the company in 0-based pages: id, names, mail, phone, role, picture, and whether the user is disabled, confirmed or flagged as a hard bounce. Needs the recruiters.list scope.

Status, 1 operation

list_job_status_historyList job status historyGETReturns the status history of a job: each status with the timestamp at which the job entered it. Needs the job.statuses.list scope on the key.

Step, 1 operation

list_job_stepsList job stepsGETLists the hiring steps (pipeline stages) of a job: id, name and order starting at 0. Needs the job.steps.list scope on the key.

Tmp, 1 operation

upload_temporary_documentUpload temporary documentPOSTUploads a file not linked to a candidate and returns its id, to pass as docTempId in an answer of create_job_application or create_spontaneous_application. Needs the document.create scope on the key.

Unit, 1 operation

list_unitsList unitsGETLists the units (entities) of the company in 0-based pages: id, internal and public names, creation timestamp and which one is the main unit. Needs the units.list scope on the key.

Use Taleez from Claude Code, Cursor or Codex

Connect Taleez in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Taleez operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Taleez

Create your workspace
Sign up free. Nothing to install.
Connect Taleez once
Add your Taleez connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.