Job Setup

Workflows

Workflows automate actions based on interview outcomes.

How Workflows Work

Workflows run automatically after an interview is evaluated. Each workflow has:

  • Conditions: Rules that must be met for the workflow to run
  • Actions: What happens when conditions are met

Workflows are evaluated in order. If a candidate matches a workflow's conditions, its actions run and no further workflows are checked (unless configured otherwise).

Creating a Workflow

  1. Click Add Workflow
  2. Give it a name (e.g., "Move high scorers to next stage")
  3. Set the conditions
  4. Choose the actions
  5. Enable it

Conditions

Score-Based Conditions

  • Minimum Score: Candidate's overall score must be at least this value
  • Maximum Score: Candidate's overall score must be at most this value
  • Score Range: Candidate's score must fall within a range

Knockout Conditions

  • Knocked Out: Candidate failed a knockout question
  • Not Knocked Out: Candidate passed all knockout questions

Actions

JobAdder Actions (if connected)

  • Move to Status: Change the candidate's status in JobAdder
  • Add Note: Post the evaluation summary as a note on their JobAdder profile

Notification Actions

  • Send Email: Notify your team about the candidate

Workflow Order

Workflows are checked from top to bottom. Use the up/down arrows to reorder them. Put your most specific conditions first.

Example order:

  1. "Reject knocked out candidates" (moves to rejected in JobAdder)
  2. "Progress high scorers" (score ≥ 80, moves to next stage)
  3. "Review mid-range" (score 50-79, stays for manual review)
  4. "Reject low scorers" (score < 50, moves to rejected)

Application Scope

Choose which candidates the workflow applies to:

  • All Applications: Runs for every candidate
  • Excluding Test Applications: Skips test candidates

Enabling/Disabling

Toggle workflows on or off without deleting them. Disabled workflows are skipped during evaluation.

Manual Trigger

You can manually trigger a workflow on a specific candidate if needed, useful for testing or re-running after changes.