Who this is for: Recruiters building Candidate sequences who want to tie outreach to a specific job opening.
What job attachment does
Attaching a job to a Candidate sequence connects the sequence's activity to a specific role in your pipeline. It unlocks two automations:
Moving candidates to a job stage when they enter the sequence, and again when they reply, so you don't have to manually update pipeline status as outreach runs.
It also makes the sequence easier to find and attribute in reporting: you can filter sequences by job, and see which roles are driving the most outreach activity.
When job attachment is available
Job attachment is only available on Candidate sequences. It does not appear on Contact (BD) sequences.
You can attach a job during sequence creation, or at any time before recipients start entering the sequence. Once at least one recipient has moved through the sequence, the attached job cannot be changed.
How to attach a job
In the sequence creation modal, scroll to Attach Job Opening
Use the dropdown to search for and select an open job
Configuring automatic stage movements
Once a job is attached, you can configure up to three automatic pipeline stage movements:
When the sequence starts, move the candidate to
Select a stage from the attached job's pipeline. When a recipient enters the sequence and their first step executes, Recruiterflow moves them to this stage on the job automatically.
Useful for: Moving candidates from "Sourced" to "Outreach In Progress" the moment outreach begins, so your pipeline reflects reality without manual updates.
When a candidate replies, move them to (Manual)
Select a stage from the attached job's pipeline. When a recipient replies to any step in the sequence, Recruiterflow moves them to this stage automatically.
Useful for: Moving candidates from "Outreach In Progress" to "Replied" or "Interested" the moment a response comes in, no manual stage update needed.
Note: Both of these automations are optional. You can configure one, both, or neither. Leaving either field blank means no automatic movement happens for that trigger.
"When a candidate replies" is different from intelligent reply detection.
The trigger above fires on any reply — including out-of-office messages, neutral acknowledgements, and negative replies like "not interested." It does not distinguish between a candidate who wants to proceed and one who doesn't.
AIRA's intelligent reply detection is a separate feature. It reads the reply content and fires only when a candidate expresses genuine interest — asking for next steps, confirming availability, or requesting a call. If you want candidates to advance in the pipeline only when they're genuinely interested, configure the positive reply stage alongside or instead of this trigger.
When AIRA detects a reply, move candidate to
Select a stage from the attached job's pipeline. AIRA reads the content of each inbound reply and fires this movement only when the candidate expresses genuine interest — asking for next steps, proposing a time to speak, or requesting more information about the role.
Useful for: Advancing only genuinely interested candidates in the pipeline automatically, without promoting every reply — including out-of-office and neutral responses — to a higher stage.
See How Positive Reply Detection Works for a full explanation of what AIRA classifies as positive, neutral, and negative — and how this interacts with the Stop on Response toggle.
What the stage movements apply to
Stage movements only apply to recipients who:
Are added to the sequence after the job is attached
Recipients added before the job was attached are not affected by these automations.
Job Recruiter as sender priority
When a job is attached, a fourth Sender Priority option becomes available: Job Recruiter. This assigns the recruiter who owns the attached job as the sender for each recipient, if that recruiter is in the sender list.
See Configuring Senders and Sender Priority for the full explanation of how priority rules work.
Removing or changing a job
You can remove the attached job at any time before the first recipient enters the sequence
Once recipients have started, the attached job is locked and cannot be changed
Removing a job before launch removes all stage movement automations as well