> For the complete documentation index, see [llms.txt](https://docs.senseloaf.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senseloaf.ai/integrations/recruit-crm-it-setup-guide.md).

# Recruit CRM — IT Setup Guide

One-time setup steps to connect Recruit CRM to SIA

This guide is for IT administrators and Recruit CRM account owners. It covers enabling API access, connecting Recruit CRM to SIA, and optionally setting up custom fields and candidate stage mapping.

Once setup is complete, your HR team can start using SIA's hiring intelligence directly from Recruit CRM.  See the Recruit CRM HR Workflow Guide for what they can do from there.

{% hint style="info" %}
**Note:** API access is available on the **Business plan or higher**. If you're on a lower plan or a free trial, you'll need to upgrade before you can connect. Connecting Recruit CRM to SIA connects it for your **entire organisation** — confirm with your team before switching connectors, as SIA only keeps one ATS active at a time.
{% endhint %}

### Before you begin

To connect Recruit CRM to SIA, you'll need to complete two steps — and optionally two more:

1. Enable API access in Recruit CRM
2. Create the Senseloaf custom fields in Recruit CRM *(optional)*
3. Set up candidate stage mapping *(optional)*
4. Connect Recruit CRM in the SIA Connectors page

### Step 1 — Enable API access in Recruit CRM

{% hint style="warning" %}
Only the **Account Owner** can access and manage this setting. An Admin can only do this if the Account Owner has created a custom role explicitly granting the permission.
{% endhint %}

1. Log in as the Account Owner and open **Admin Settings**
2. Scroll down and click **API**
3. Toggle **Enable API Token** on
4. Copy the API token that's displayed and store it securely

{% hint style="warning" %}
You won't be able to see the full token value again after leaving this screen. Store it securely before continuing.
{% endhint %}

### Step 2 — Create custom fields in Recruit CRM *(optional)*

Senseloaf can write its score and report link into a set of custom fields on the candidate record. Creating these is optional, but if you do, let the Senseloaf team know once they're created so the fields can be mapped during onboarding.

1. Log in as the Account Owner (or a role with Data Customization access) and open **Admin Settings**
2. Under **Data Customization**, choose the **Candidates** entity
3. Click **+ New Custom Field**
4. Create the fields below, choosing the matching field type, then click **Save Field**

| **Field name** | **Field type** | **Stores**                                                                                                     |
| -------------- | -------------- | -------------------------------------------------------------------------------------------------------------- |
| **SIA Score**  | Number         | The overall candidate score from Senseloaf's AI agents — resume matching, prescreening, and interview combined |
| **SIA Report** | Text / URL     | A link to the candidate's Senseloaf report card                                                                |

{% hint style="info" %}
**Note:** Recruit CRM allows up to 15 custom fields on the Pro plan and 100 on the Business plan. Once a field's type is set, it cannot be changed later — you'd need to create a new field and delete the old one, which also deletes its stored data. Activity updates (screening, matching, engagement) are logged automatically as notes on the candidate.  No separate field is needed for that.
{% endhint %}

**Quick reference**

| **Level** | **Name**   | **Type**   | **Required?** |
| --------- | ---------- | ---------- | ------------- |
| Candidate | SIA Score  | Number     | Optional      |
| Candidate | SIA Report | Text / URL | Optional      |

### Step 3 — Candidate stage mapping *(optional)*

Recruit CRM organises each job's pipeline as a set of hiring stages. Senseloaf can automatically move candidates between these stages based on their AI evaluation outcome — matching, prescreening, or interview. You're not limited to a fixed set of stages, and there's nothing new to create if your existing pipeline already covers the outcomes you need.

### Enable automatic syncing

To enable automatic syncing of your Recruit CRM data with SIA, reach out to the Senseloaf team at <support@senseloaf.com>. The team will configure and enable the bidirectional sync for your organisation.

### Step 4 — Connect Recruit CRM to SIA

**A. Open Connectors in SIA**

1. Log in to your SIA account
2. Click your **Profile icon** in the bottom-left corner
3. Click **Connectors** from the menu
4. Search for **Recruit CRM** and click **Connect** — this opens the pop-up for entering credentials

**B. Enter your Recruit CRM credentials**

* **API Token** — paste the token generated in Step 1 into the API Key field

**C. Connect Recruit CRM**

1. Click **Connect**
2. SIA establishes the connection with your Recruit CRM account

### What happens once connected

Once Recruit CRM is connected, SIA begins syncing jobs and candidates automatically, no further setup required from IT. For a full overview of what the HR team can do from here, see the Recruit CRM HR Workflow Guide.


---

# 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.senseloaf.ai/integrations/recruit-crm-it-setup-guide.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.