> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/connectors/source-catalog/sales-crms/recruit-crm.md).

# Recruit CRM

## **Why syncing my Recruit CRM to** [**Whaly**](https://whaly.io)**?**

Syncing your Recruit CRM can be useful for various cases

* Understand who your candidates are
* Report on the performance of your recruiters to be sure that you keep accelerating
* Build actionable dashboards with the list of Jobs or of Candidates that needs to be act upon
* ...

## Which Recruit CRM data is synced by [Whaly](https://whaly.io)?

[Whaly](https://whaly.io) 🐳 is currently syncing the following data:

* **Candidate**: Candidates are people applying for jobs.
* **Candidate Hiring Stage**: Hiring Stage of candidates in a given job.
* **Candidate Stage**: Steps in the Candidate pipeline.
* **Collaborator**: People working at your company, managing your candidates, jobs and contacts.
* **Company**: Company offering jobs.
* **Contact**: Contacts belongs to companies that are offering jobs.
* **Contact Stage**: Steps in the Sales pipeline.
* **Job**: Jobs are employment offers that candidates can apply for and ultimately be hired for.
* **Job Stage**: Steps in the Job pipeline.

{% embed url="<https://docs.google.com/presentation/d/1mEKKfRAYOp2J_dQcz5_5Hby2BUsh_N-qneNkSHwExe4/edit?usp=sharing>" %}

[You can find the relationship between all those objects here.](https://docs.google.com/presentation/d/1mEKKfRAYOp2J_dQcz5_5Hby2BUsh_N-qneNkSHwExe4/edit)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.whaly.io/connectors/source-catalog/sales-crms/recruit-crm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.