Connect Claude & ChatGPT to 100Hires ATS

29 tools for 100Hires ATS

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• add_candidate_noteChanges dataAdd a note (`body`) to a candidate by `candidate_id`, with optional `visibility` and `mention_user_ids`.
• advance_applicationChanges dataAdvance an application to the next stage in its pipeline by `application_id`.
• create_applicationChanges dataAdd an existing candidate (`candidate_id`) to a job (`job_id`), optionally at a `stage_id` with a `cv`.
• create_candidateChanges dataCreate a candidate with name, email, phone, location and optional `cv`; pass `job_id` (and `stage_id`) to add them to a job. Search first to avoid duplicates.
• create_jobChanges dataCreate a job with `title`, `status` (e.g. Draft, Public), `description` (HTML) and `location_country`, plus optional city, remote, salary and department.
• get_applicationGet one application by `application_id`, including job, candidate, current stage and status.
• get_application_stage_historyGet the stage history of an application by `application_id`.
• get_candidateGet one candidate by `candidate_id`, including contact details, applications and profile.
• get_candidate_resumeGet the resume of a candidate by `candidate_id`.
• get_jobGet one job by `project_id` (the job ID), including description, location, salary and status.
• hire_applicationChanges dataMark an application as hired by `application_id`.
• list_applicationsList applications, filtered by `job_id`, `candidate_id`, `stage_id`, `status`, AI score range or date.
• list_candidate_emailsList emails sent to or scheduled for a candidate by `candidate_id`.
• list_candidate_notesList the notes on a candidate by `candidate_id`.
• list_interviewsList interviews, filtered by `job_id`, `candidate_id`, `application_id`, `interviewer_user_id` or `date`.
• list_job_statusesList the job statuses available in the account.
• list_jobsList jobs, filtered by keyword `q`, `status`, `department_id` or date. Use this to find a job ID.
• list_rejection_reasonsList the rejection reasons available when rejecting an application.
• list_stagesList pipeline stages, optionally for a `job_id` or `workflow_id`. Use a stage ID to move applications.
• list_usersList the users (team members) in the company. Use their IDs as interviewers or note mentions.
• move_applicationChanges dataMove an application to a specific pipeline stage by `application_id` and `stage_id` (see list_stages).
• reject_applicationVisible to othersReject an application by `application_id`, with an optional `rejection_reason_id`. The candidate may be emailed unless `suppress_notification` is true.
• schedule_interviewChanges dataSchedule an interview for an application: `application_id`, `start_time` and `end_time` (Unix seconds), `interviewer_ids` (user IDs) and optional `location`.
• search_candidatesSearch candidates by keyword `q`, `email`, `full_name`, `linkedin`, `job_id` or `stage_id`, or by created/updated date. Use this to find a candidate ID.
• send_candidate_emailVisible to othersEmail a candidate: `candidate_id`, `to` addresses, `subject` and HTML `body`. It is sent at `scheduled_at` (Unix seconds) or about 15 minutes after creation.
• set_job_statusChanges dataChange a job's `status` (e.g. Draft, Public, Archived) by `job_id`. Setting it public publishes the job.
• tag_candidateChanges dataAdd one or more `tags` to a candidate by `candidate_id`.
• update_candidateChanges dataUpdate a candidate's name, email, phone, location or profile by `candidate_id`. Only the fields you pass change.
• update_jobChanges dataUpdate a job by `project_id` (the job ID): title, description, location, salary, department and more. Only the fields you pass change.

Questions