Candidate Stage Triggers: Automate the Right Recruitment Action at the Right Moment

What are candidate stage triggers?

A candidate stage trigger is an action connected to a Kanban column in an applicant tracking system (ATS). When a member of the hiring team moves a candidate into that stage, the selected action is scheduled or completed automatically. It is a simple idea with a useful outcome: the workflow follows the candidate instead of living in a recruiter’s memory, a spreadsheet, or a separate task list.

For example, moving someone into Phone Screen can add an Interview needed tag and notify the hiring manager. Moving someone into Offer can send a prepared candidate email. The recruiter still decides who progresses and when. The trigger handles the repeatable operational follow-up.

Treegarden Stage Triggers are configured on the relevant Kanban column. The lightning icon on a column shows when active triggers exist, so the automation remains visible at the point where the team actually manages candidates.

How stage triggers work in a recruitment pipeline

Each Kanban column can have one or more triggers. A recruiter opens the column’s Stage Triggers menu, adds the actions they want, chooses a timing for each action, and saves the configuration. The actions are ordered, which makes it possible to create a small, understandable sequence rather than an opaque automation.

1. A recruiter moves a candidate into a pipeline stage. This can happen by drag and drop, from the candidate’s status control, as part of a bulk move, through rejection, or when moving a candidate to another job.
2. Treegarden records the stage entry. The candidate Timeline shows what is pending and what subsequently happened.
3. Each enabled trigger follows its selected timing. An action can run immediately, or after 1 minute, 15 minutes, 1 hour, 24 hours, or 48 hours.
4. Pending work stays tied to the stage. If the candidate leaves the column before a delayed action is due, that pending action is cancelled rather than running out of context.

This gives teams useful guardrails without taking control away from recruiters. A stage trigger is not a hiring decision engine: it does not decide whether somebody advances, rejects a candidate, or schedules an interview on its own. It completes the practical action the team deliberately configured after a human stage change.

The three Stage Trigger actions in Treegarden

1. Email with template

This action sends the candidate an approved email template when a member of the hiring team moves them into the relevant stage. It is designed for communication that should be consistent and timely but does not need to be written from scratch every time.

Common examples include an application acknowledgement, a next-step invitation, an interview preparation note, a decision-pending update, or an offer follow-up. The team selects the template while configuring the trigger, so a recruiter does not need to hunt for it during a busy pipeline review.

Email triggers can run immediately when timing matters, or after a delay when the communication should not appear at the exact instant of a move. Every scheduled, successful, cancelled, skipped, or failed action is visible in the candidate Timeline, creating a clear record for the team.

2. Mention @ a colleague

This action sends an internal mention to the people who need to react to a candidate’s progress. It is useful when a stage change requires attention from someone other than the person moving the candidate.

Eligible recipients are internal Recruiters, Hiring Managers, and HR Managers with ATS access. External collaborators are deliberately excluded, so a stage trigger does not create an unintended external notification path.

Use it to ask a hiring manager to review a shortlisted candidate, alert HR that an offer was accepted, or tell a recruiter that a candidate has reached an assessment stage. It creates a prompt for the team without sending an unnecessary email to the candidate.

3. Add tag

This action adds one or more existing, company-scoped tags to the candidate record. Tags make the pipeline easier to scan, filter, segment, and report on later.

For instance, a team might add Needs hiring manager review when a recruiter moves a candidate into a shortlist stage, Interview coordination when a candidate moves toward an interview, or Offer accepted when a recruiter moves a candidate into the final stage. Because the action happens consistently, the tag taxonomy stays useful instead of gradually becoming dependent on each individual recruiter’s habits.

Timing, cancellation, and re-entry: the rules that prevent noise

Good recruitment automation should help the team without producing stale or duplicated actions. That is why Stage Triggers follow the candidate’s actual stage state.

• Immediate actions run after the stage move is recorded.
• Delayed actions can be set for 1 minute, 15 minutes, 1 hour, 24 hours, or 48 hours.
• Leaving the stage cancels pending actions. A delayed rejection follow-up, tag, or colleague mention will not fire after the candidate has moved somewhere else.
• Re-entering later creates a new run. If a candidate genuinely returns to the stage, the configured workflow can apply again.
• Reordering inside the same column does not trigger anything. Moving a card higher or lower in a Kanban column is not treated as a new stage entry.

New applications are intentionally opt-in per trigger. A team can decide whether an application first created in a given stage should count as an entry, rather than accidentally emailing every applicant because a new rule was switched on.

Four practical recruitment workflows to start with

1. Keep applicants informed without manual follow-up

In an Application received column, add an email trigger based on your application acknowledgement template. If you want the message to be sent to brand-new applications, enable initial entry for that specific rule. This gives candidates confirmation that their application reached the team while leaving recruiters free to focus on review.

2. Make a shortlist reviewable

In a Shortlisted column, add a tag such as Hiring manager review and a colleague mention for the assigned hiring manager. The candidate is clearly labelled in searches and reports, while the person who needs to provide feedback receives an internal prompt.

3. Make the interview handoff explicit

When a recruiter moves a candidate into an Interview stage, add an Interview coordination tag immediately and send the candidate’s preparation email from an approved template. If your team wants an internal reminder after the move has settled, add a delayed mention as a separate action.

4. Protect the offer-to-acceptance handoff

When a candidate moves into Offer accepted, add a tag that makes the status visible to HR and mention the colleague responsible for onboarding. This creates a clear handoff point without treating acceptance as the end of the candidate experience.

How to configure triggers safely

Start with one repeatable action per stage. A visible, understandable workflow is more valuable than a large set of rules nobody remembers. Once the first rule behaves as expected, add a second action only where it removes a real operational gap.

Use the column popover to review the active trigger count and the individual actions. The active lightning indicator makes it easier to see where automation is in use. Recruiters, company administrators, and HR Managers with ATS access can configure, cancel, or run actions early when appropriate. Hiring Managers can see a concise impact summary without being given controls that could change the workflow.

Choose delayed actions deliberately. An immediate application acknowledgement is often useful; a 24-hour follow-up may be a better fit after an interview. The important question is not “can this be automated?” but “will this action still be correct if the candidate moves on before the delay ends?”

Stage triggers versus email-only automation

Traditional stage-based email automation is useful, but it solves only one part of a hiring workflow. Candidate Stage Triggers expand the same stage-entry idea to internal coordination and candidate data hygiene: a template email can be paired with a colleague mention or an automatically applied tag.

The result is a more complete operational signal around the candidate’s move. The candidate gets the right communication, the right teammate is alerted, and the record is labelled for the next step. For more detail on email design, read our guide to stage-based email automation. For a broader view of which tasks should remain human, see recruitment automation.

Frequently asked questions about candidate stage triggers

What is a candidate stage trigger?

A candidate stage trigger is an automated action that runs when a member of the hiring team moves a candidate into a selected pipeline stage. In Treegarden, it can send a candidate email from a template, mention an eligible colleague internally, or add tags to the candidate record.

Can one recruitment stage have multiple triggers?

Yes. You can configure several ordered actions for one stage. Each action has its own timing, so a team can combine an immediate tag with a later colleague mention or candidate email.

What happens if the candidate moves out of the stage before a delayed action runs?

Treegarden cancels the pending action. This keeps delayed automation relevant to the candidate’s actual position in the pipeline.

Do triggers run again if a candidate re-enters a stage?

Yes. A later, genuine re-entry creates a new trigger run. Moving the card around inside the same column does not, because it is not a stage change.

Who can receive a colleague mention?

Internal Recruiters, Hiring Managers, and HR Managers with ATS access can be selected. External collaborators are not available as trigger recipients.