Integration

Recruitis integration

Recruitis is an applicant tracking system (ATS). An agent can list, read and create job advertisements (as drafts), publish them on channels and open, close or archive positions; create candidates and applications (answers), read answers, interviews, communication, activity, tags, custom fields, checklists and meetings, record communication, share meeting reservation links, recommend people for jobs, manage job filters, and export report and BI data. Candidate records, files and messages are personal data; recommending and sharing a reservation link contact real people. Not exposed: login and logout, rejecting an answer (its documented flag is ambiguous), answer export marking, view counting, career-site form rendering, adding comments and the deprecated task list. Authentication is a Recruitis API token (Settings, API integration) sent as a Bearer token; some routes need a full_access token.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Recruitis

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.

Communication, 5 operations

  • create_answer_communication_recordCreate answer communication recordPOSTAdds a communication record (email, SMS, call, LinkedIn message or note, incoming or outgoing) to one answer's history in Recruitis, with optional attachments. Returns the record id.
  • create_candidate_communication_recordCreate candidate communication recordPOSTAdds a communication record (email, SMS, call, LinkedIn message or note, incoming or outgoing) to a candidate's history in Recruitis, with optional attachments. Returns the record id.
  • list_answer_communicationList answer communicationGETLists the communication linked to one answer of a candidate (emails, SMS, LinkedIn messages, notes), page by page. Message contents are personal data.
  • list_candidate_communicationList candidate communicationGETLists the communication linked directly to a candidate (emails, SMS, LinkedIn messages, notes), page by page. Message contents are personal data.
  • list_job_communicationList job communicationGETLists the communication with candidates (emails, SMS, LinkedIn messages, notes) for one job advertisement. Message contents and candidate contacts are personal data.

Candidate, 4 operations

  • create_candidateCreate candidatePOSTCreates a candidate without an application, for the talent pool, or updates the existing one with the same email or phone. Returns the candidate id. Candidate records are personal data.
  • delete_candidateDelete candidateDELETEPermanently deletes a candidate with all answers, interviews, notes, attachments and GDPR consents. It cannot be undone and is limited by a daily quota (see get_current_account).
  • get_bi_candidateGet bi candidateGETReturns one answer for BI reporting: status, source, state history, rejection, hiring proposal, interview, hire and employment dates, notes and offer (personal data).
  • list_bi_candidatesList bi candidatesGETLists candidates' answers for BI reporting over a date range of at most 3 months, page by page: status, source, state history, rejection, hiring proposal, dates and notes (personal data).

Channel, 4 operations

  • list_channelsList channelsGETLists the publication channels the company can publish job advertisements on, with their ids (used by publish_job_on_channel and to filter list_jobs).
  • list_job_channelsList job channelsGETLists the publication channels a job advertisement is published on, with the publication dates and whether each is paused.
  • publish_job_on_channelPublish job on channelPUTPublishes a job advertisement on one publication channel between date_from and date_to (or updates those dates). The job must already be published in Recruitis, not a draft.
  • unpublish_job_from_channelUnpublish job from channelDELETEUnpublishes a job advertisement from one publication channel.

Extra, 4 operations

  • get_answer_tagsGet answer tagsGETReturns the tags attached to an answer (application).
  • get_candidate_tagsGet candidate tagsGETReturns the tags attached to a candidate.
  • set_answer_tagsSet answer tagsPUTReplaces the tags of an answer (application): every tag saved before is overwritten by the list sent.
  • set_candidate_tagsSet candidate tagsPUTReplaces the tags of a candidate: every tag saved before is overwritten by the list sent.

Filter, 4 operations

  • create_filterCreate filterPOSTCreates a job filter item in a group (the group is created when it does not exist) and returns its id and group id.
  • delete_filterDelete filterDELETEDeletes a job filter item.
  • list_filtersList filtersGETLists the job filter items (such as departments) with their ids and groups, optionally only some groups. Their ids filter list_jobs.
  • update_filterUpdate filterPUTRenames a job filter item or moves it to another group.

Answer, 3 operations

  • create_answerCreate answerPOSTCreates an application (answer) to a job and returns its id; a candidate is created, or merged by email or phone. Consent to data processing is granted automatically (1 year). Candidate data is personal data.
  • get_answerGet answerGETReturns one answer (application) in detail: candidate name, contacts, rating, flow status, rejection, requirements, job details, source, attachments and cover letter (personal data).
  • list_answersList answersGETLists non-rejected answers (applications) page by page (limit up to 50), filterable by job, flow and creation date; flow_id -1 lists rejected ones. Returns candidate names, contacts and status (personal data).

Job, 3 operations

  • create_jobCreate jobPOSTCreates a job advertisement as a draft and returns its id. Complete and publish it by hand in Recruitis first: publishing it to a channel or changing its state through the API before that may leave it inconsistent.
  • get_jobGet jobGETReturns one job advertisement: title, description, state, workfields, filters, contact person, addresses, employment types, salary, statistics and publication channels.
  • list_jobsList jobsGETLists job advertisements page by page (limit up to 50, default 10), filterable by profession, office, filter item, channel, state and last edit date. Returns each job's details, salary, addresses and channels.

Reservation link, 3 operations

  • delete_reservation_linkDelete reservation linkDELETEDeletes a shared reservation link that is not booked yet (its event is null in list_answer_meetings) and that you own; otherwise Recruitis refuses it.
  • list_reservation_linksList reservation linksGETLists the meeting reservation link templates available to share with candidates: title, description, type, address, author and preview URL.
  • share_reservation_linkShare reservation linkPOSTShares a meeting reservation link with the candidate of an answer, so the candidate receives it and can book a meeting (it reaches a real person). Returns the shared link and its URL.

Comment, 2 operations

  • delete_commentDelete commentDELETEDeletes one comment by its id.
  • list_commentsList commentsGETLists comments of one kind (applicant or offer, as Recruitis names them) with their author, text, dates and tags.

Position, 2 operations

  • get_bi_positionGet bi positionGETReturns one position for BI reporting: title, dates, answer count, offer request, author, sharing, filters, publication channels and places.
  • list_bi_positionsList bi positionsGETLists positions for BI reporting over a date range of at most 3 months, page by page: title, dates, answer count, author, sharing, filters, publication channels and places.

User, 2 operations

  • get_candidate_answer_custom_fieldsGet candidate answer custom fieldsGETReturns a candidate's custom field values for one position (answer): id, name and value (personal data).
  • get_candidate_custom_fieldsGet candidate custom fieldsGETReturns a candidate's custom field values that are not tied to a position: id, name and value (personal data).

Access state, 1 operation

  • set_job_access_stateSet job access statePUTOpens (1), closes (2) or archives (3) a published position. Archiving stops new applications, blocks edits to existing ones and anonymizes candidates who gave no GDPR consent.

Activity feed, 1 operation

  • list_candidate_activityList candidate activityGETReturns a candidate's activity history (notes, history, communication, tasks), optionally filtered to one kind (personal data).

Applicant, 1 operation

  • recommend_person_for_jobRecommend person for jobPOSTRecommends a person for a job (a referral). Recruitis then emails that person asking whether they are interested, so this sends an email to a real person. Returns the referral id.

Checklist, 1 operation

  • get_answer_checklistGet answer checklistGETLists the checklists of an answer in one flow, with their items and each item's state (unchecked, checked, rejected).

Employment, 1 operation

  • list_employment_typesList employment typesGETLists the employment types (full time, part time...) with their ids. Names are returned in Czech.

File, 1 operation

  • get_fileGet fileGETDownloads one candidate file (CV, cover letter, attachment) by its hash and returns its name, size and content as base64. Files are personal data.

Flow, 1 operation

  • list_flowsList flowsGETLists the recruitment flow templates and their statuses, or the statuses of one flow by name or of a job's flow (jobId wins).

Interview, 1 operation

  • list_answer_meetingsList answer meetingsGETLists the meetings scheduled for an answer and the reservation links shared for it (event null means not booked yet).

Me, 1 operation

  • get_current_accountGet current accountGETReturns the Recruitis account the token belongs to: employee and company ids and names, email, role, token type and expiry, and the daily quota for candidate deletion.

Note, 1 operation

  • list_answer_interviewsList answer interviewsGETLists the interviews recorded for an answer, with the SWOT notes, free note, questions and criteria ratings (personal data).

Np, 1 operation

  • list_nps_recordsList nps recordsGETLists candidate NPS (satisfaction) records over a date range of at most 3 months, page by page: position, flow, rating, opinion, dates and recruiters.

Office, 1 operation

  • list_officesList officesGETLists the company's offices (branches) with their address, description and logo; their ids filter list_jobs.

Reject reason, 1 operation

  • list_reject_reasonsList reject reasonsGETLists the reject reasons, split into candidate-side and company-side reasons, with their ids.

Report, 1 operation

  • export_reportExport reportGETExports report data for a date range (default today): answers, jobs, offices, recruiters and timeline sheets, the same data as the Excel reports. Contains candidate personal data; large ranges are slow.

Source, 1 operation

  • list_sourcesList sourcesGETLists the answer sources (system or company-defined) with their ids, used as source_id when creating an answer.

State, 1 operation

  • set_checklist_item_stateSet checklist item statePUTSets the state of one checklist item for an answer: 1 unchecked, 2 checked, 3 rejected, in the given flow or the answer's current one.

Table, 1 operation

  • list_tasksList tasksGETLists recruiting tasks, 10 per page: to solve or solved, due today or overdue, by task or by candidate, and by assignment (to me, by me to others, me to me).

Workfield, 1 operation

  • list_workfieldsList workfieldsGETLists all professions grouped by field, with their ids (used to filter list_jobs). Names are returned in Czech.

Use Recruitis from Claude Code, Cursor or Codex

Connect Recruitis in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Recruitis 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 Recruitis

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Recruitis once

    Add your Recruitis connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

Recruitis integration FAQ

What can you do with the Recruitis integration?

LiveContext exposes 54 operations on Recruitis, covering communication, candidate, channel and extra.

Popular integrations

Browse the whole catalog