> 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/recruitee-hr-workflow-guide.md).

# Recruitee — HR Workflow Guide

What happens after Recruitee is connected — and what your team can do from there

This guide is for recruiters and hiring managers using SIA with Recruitee. Once connected, SIA automatically syncs your open offers and candidate applications so you can run AI-powered matching, prescreening, and interviews without leaving your existing workflow. Results come back into Recruitee as notes on the candidate, so your team can see how someone scored without switching to another system to check.

{% hint style="info" %}
**Note:** Recruitee must be connected to SIA before any of this applies. If it hasn't been set up yet, ask your IT admin to follow the Recruitee IT Setup Guide.
{% endhint %}

### How offers sync from Recruitee

SIA checks your Recruitee account every 15 minutes and pulls in every open offer automatically. There's no manual job creation needed on your end.

{% hint style="info" %}
**Note:** Recruitee refers to jobs as **offers.** You'll see this term used throughout the platform and in SIA Chat when working with Recruitee data.
{% endhint %}

For each offer it finds, SIA sets up three things automatically:

* **Job details** — the role, description, and requirements come across as-is from Recruitee
* **A default resume matching strategy** — a starting set of criteria to score candidates against, based on the offer itself, so scoring can begin right away
* **Workflow activation** — if the offer already has a SIA user assigned, it goes live immediately and starts evaluating candidates

If an offer doesn't yet have a SIA user assigned, it's held in **Draft** rather than going live. Nothing is evaluated or acted on until someone is assigned to own it.

### Candidate sync and shortlisting

Alongside offers, SIA pulls in candidates from Recruitee every 15 minutes for every active offer, evaluates each one against that offer's matching strategy, and ranks them by grade in the Candidate Listing, so your team opens a ready-sorted list rather than a raw pile of applications.

Shortlisted and disqualified candidates can be tagged in Recruitee to flag the outcome at a glance, right alongside the note SIA leaves on their profile.

One thing worth knowing: Recruitee doesn't expose a way to move a candidate along its pipeline stages through this integration, so SIA can't move candidates between stages on your behalf the way it can in some other ATSs. Your team reviews the AI outcome in the candidate's notes and tags, then moves them along the pipeline manually, shortlisting and scoring are still fully automatic, it's just the stage move in Recruitee itself that stays a manual click.

### What lands as a note in Recruitee

Every SIA evaluation — resume matching, prescreening, or an interview — automatically flows back to the candidate's Recruitee profile as a plain-text note containing the score, grade, summary, and a link to the full report. Your team never has to leave Recruitee to see how someone did.

Recruitee has no candidate-level custom fields available through this integration, so this note — combined with tags for quick filtering — is how results show up in Recruitee itself.

Your team can review the evaluation outcome directly from Recruitee with key insights at a glance. When they want to go deeper, they can jump straight into the full evaluation report in SIA. This gives hiring teams the flexibility to review from Recruitee when they need a quick decision, or open SIA when they want the full picture.

### Interact with your Recruitee data in SIA Chat

Once Recruitee is connected, you can ask SIA about jobs, candidates, notes, and pipeline stages in plain language directly from SIA Chat. The prompts below are a starting point — explore more from directly within the SIA platform.

{% prompt description="Getting started" icon="bolt-lightning" openInAIProviders="false" %}

```markdown
What can I do with my Recruitee integration?
```

{% endprompt %}

{% prompt description="Jobs and Application Status" icon="rotate" openInAIProviders="false" %}

```markdown
How many candidates are in each stage of the [Job Title] pipeline?
```

{% endprompt %}

{% prompt description="Update Notes" icon="file-import" openInAIProviders="false" %}

```markdown
Add a note to [Applicant Name] from [Job Name] in Recruitee: strong on system design, weak on SQL.
```

{% endprompt %}

{% prompt description="Stage Changes" icon="rotate" openInAIProviders="false" %}

```markdown
Which candidates moved stages today because their score changed?
```

{% endprompt %}

### **Connecting your other tools**

SIA Chat isn't limited to Recruitee. Since your other tools are connected to SIA too, you can act on the same candidates and jobs across Slack, Google Workspace, and email without leaving the conversation. Ask SIA to hand off a shortlist, a report, or a scheduling task to whichever tool your team actually works in — it'll route the request to the right connector automatically.

{% prompt description="Share update in channels" icon="paper-plane-top" openInAIProviders="false" %}

```markdown
Post today's shortlisted candidates to our #hiring Slack channel.
```

{% endprompt %}

{% prompt description="Export Date to Google Sheet" icon="file-import" openInAIProviders="false" %}

```markdown
Export this week's shortlist to a Google Sheet for the hiring manager.
```

{% endprompt %}

{% prompt description="Send Emails" icon="paper-plane-top" openInAIProviders="false" %}

```markdown
Send an email invite to [Candidate Name] for the next interview round.
```

{% endprompt %}

{% prompt description="Schedule Meetings" icon="calendar-day" openInAIProviders="false" %}

```markdown
Schedule a screening call with [Candidate Name] on my calendar for next week
```

{% endprompt %}

### Setting up and managing your workflow

For everything else, writing jobs, configuring agents, activating workflows, screening candidates, and shortlisting, the process is the same as the standard Senseloaf setup. Refer to the articles below:

* Configuring resume matching → [Create Matching Strategy](https://docs.senseloaf.ai/hiring-workflows/create-matching-strategy)
* Setting up prescreening → [Configure Prescreening](https://docs.senseloaf.ai/hiring-workflows/configure-prescreening)
* Setting up interviews → [Plan AI Interview](https://docs.senseloaf.ai/hiring-workflows/plan-ai-interview)
* Automating candidate progression → [Set Pipeline Automation](https://docs.senseloaf.ai/hiring-workflows/set-pipeline-automation)
* Reviewing your candidate pipeline → [Candidate Listing](https://docs.senseloaf.ai/agents-output/candidate-listing)
* Shortlisting and disqualifying → [Shortlist and Disqualify](https://docs.senseloaf.ai/candidate-pipeline/shortlist-and-disqualify)


---

# 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/recruitee-hr-workflow-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.
