Skip to main content
Who can do this: Users with the Manage Job Req Settings permission.Availability: The text message action needs text messaging set up for your account, and the WhatsApp action appears only once WhatsApp is connected. See Text messages and WhatsApp.
Automation rules do the repetitive work on a job req for you. Each rule waits for something to happen, like a candidate finishing an activity, checks the conditions you set, and then takes one or more actions: moving the candidate to the next step, sending an email or text, assigning a recruiter, rejecting, or adding them to another job req. It’s how a small team keeps up with thousands of applicants and treats every one of them the same way. Every rule has three parts:
  • Trigger: the event that starts it. Each rule has exactly one.
  • Conditions: optional checks the candidate must meet. With no conditions, the actions run every time the trigger happens.
  • Actions: what Journeyfront does. A rule can have several, and they all run.

Where rules appear

On the job req’s Workflow page (Setup, then Workflow), each rule is a purple bar with a lightning bolt. It sits next to whatever its trigger points to:
  • Under START: rules that run when a Candidate Application is created.
  • Under an activity: rules that run when candidates complete it or its status changes.
  • At the bottom of a step: rules that run when candidates move into, complete or spend a set time in that step.
  • Under HIRED or REJECTED: rules that run when a candidate is hired or rejected.
Each bar shows the rule’s name, its delay and its actions, then an ON/OFF switch, a pencil to edit it and a trash can to delete it. Click a bar to see the whole rule in the panel on the right: TRIGGER, DELAY, CONDITION(S) and ACTION(S).
A rule named Typing test reminder shown as a purple bar at the bottom of the Assessments step, with its ON switch, pencil and trash can, and its details on the right: the TRIGGER, DELAY, CONDITION(S) and ACTION(S) cards and an Edit button

Create an automation rule

1

Open the Workflow page

Open the job req and go to Setup, then Workflow.
2

Click a lightning bolt

Click the lightning bolt (Add Automation) next to where the rule belongs: START, a step’s name, an activity, HIRED or REJECTED. The automation editor opens with a trigger already chosen for that spot. You can change it.
The Workflow page with the lightning bolt (Add Automation) highlighted on the Qualification Questions activity in the Screening step, next to its eye and bell icons
3

Name it

Type a name at the top that says what the rule does, like “Advance strong screeners”.
4

Set the trigger

Click TRIGGER in the flow on the right. Pick the Trigger and, depending on the trigger, the Activity, Status or Step it applies to.
The automation editor open over the Workflow page: the rule's name, Cancel, Save and the Enabled switch at the top, the TRIGGER fields (Trigger, Step and Time in step reaches) on the left, and the TRIGGER, DELAY, CONDITION(S) and ACTION(S) cards on the right
5

Set the delay

Click DELAY. Delay before evaluating conditions is how many minutes Journeyfront waits after the trigger before checking conditions. The default is 2 minutes, which gives scores and statuses time to settle.
6

Add conditions (optional)

Click CONDITION(S), then + Add Condition. Pick the Condition, then fill in what it compares, like the activity, operator and score. For each extra condition, choose And (all must be true) or Or (any one can be true) with Change to Or or Change to And.
7

Add actions

Click ACTION(S), then + Add Action. Pick the Action Type and fill in its details. Add as many actions as you need.
8

Turn it on and save

New rules start off. Switch Enabled to On, then click Save. A rule that’s off never runs.
While a rule is on, any required field you’ve left empty shows Missing Data, and Journeyfront won’t save or switch on a rule that’s incomplete. You can save a rule that’s off with fields still empty, so build it with Enabled off and turn it on when it’s ready. To change a rule later, click its pencil, or click the bar and then Edit. To turn it off without deleting it, flip its ON/OFF switch. To delete it, click its trash can, then Delete.
Name each rule after what it does (“Reject: no work authorization”, “Text reminder: typing test”). When a candidate’s history shows that an automation acted on them, the name is what your team sees.

Rules and workflow versions

Rules belong to a version of the workflow, and each candidate is checked against the rules of the version they’re on.
  • On the Workflow page, adding, editing, switching and deleting rules saves straight away to the version you’re looking at. On the Latest version, that means the change is live right away.
  • In the workflow editor (Create New Version or Edit Draft), rules are part of your draft, like steps and activities. They take effect when you publish. See Publish workflow changes.
Check the version name at the top of the Workflow page before you change a rule. To try a new rule on future applicants only, add it in the editor and publish it with a new version.

Triggers

When an activity is scored after the candidate submits it, like screening questions your team or AI scores, its status is Complete - Need Scores until scoring is done. Candidate Completes Activity runs as soon as the candidate submits. To act on the final score, use Activity Status Changes To with the status Complete instead.

Conditions

All scores in conditions use the 1 to 5 scale. Score conditions compare with Greater than, Greater than or equal to, Equal to, Between, Less than or equal to or Less than.
The automation editor with CONDITION(S) selected: an Activity score is condition on Screening Questions and a Candidate State/Region Is Colorado condition, joined by AND with the Change to Or link between them, and the same two conditions shown in the flow on the right
Source, Hiring Class, Assigned User, Fraud Risk Level and the location conditions use Is or Is Not, plus Is Set and Is Not Set to check whether there’s a value at all. For example, Fraud Risk Level Is Not Set matches applications that haven’t been checked yet.

Actions

Actions are what the rule does once the trigger has happened and the conditions are met: move the candidate, message them, assign them, set their hiring class, reject them or add them to another job req. In the automation editor, click ACTION(S), then + Add Action, and pick the Action Type. Each type then asks for its own details, listed below. A rule can have several actions, and they all run.
The automation editor for the rule Advance to interview with ACTION(S) selected and the Action Type list open, highlighted: Assign User, Change candidate step to, Reject candidate, Send Email to Candidate, Send SMS to Candidate, Send WhatsApp Message to Candidate, Set Hiring Class and Add to Other Job Req
See Candidate assignment, Reject candidates, Email templates and Add candidates to another job req for more on each.

Common recipes

These examples use made-up names and scores. Set your own based on how your roles and candidates perform.
  • Trigger: Activity Status Changes To, Activity “Screening Questions”, Status Complete.
  • Condition: Activity score is, Activity “Screening Questions”, Greater than or equal to 4.
  • Action: Change candidate step to “Assessments”, with Send email inviting user to complete the next step ticked.
Candidates who score lower stay where they are for your team to review.
  • Trigger: Candidate Time in Step Reaches, Step “Assessments”, 2 Days.
  • Condition: Activity Status is, Activity “Typing Test”, Not Started.
  • Action: Send SMS to Candidate with a friendly reminder template and the link to continue.
  • Trigger: Candidate Application is Created.
  • Condition: Candidate State/Region Is the state your regional recruiter covers.
  • Action: Assign User, Single User, that recruiter.
Make one rule per region. Or use Add to Other Job Req to send candidates in a region to that region’s job req.
  • Trigger: Candidate Completes Step, Step “Assessments”.
  • Condition: Overall score is Less than 2.
  • Actions: Reject candidate with the matching reason, and Send Email to Candidate with your rejection template, with a Delay Days of 1 so the reply doesn’t feel instant.
Start with rules that move, message and assign candidates. Before you automate rejections, run the rule with a softer action (like assigning the candidates to a reviewer) for a few weeks, and check that it picks the people you expect.

Check that a rule is working

There’s no test mode, so watch the first candidates after you turn a rule on. Each time a rule acts on a candidate, their Candidate Application’s Comments & Activities tab shows an Automation Ran entry with the rule’s name.
The Comments and Activities tab of a Candidate Application with an Automation Ran by System entry for the rule Advance strong screeners, followed by a Step Changed entry from Screening to Interview

FAQ

Open their Candidate Application and check the Comments & Activities tab. An Automation Ran entry names the rule that acted. Then open the job req’s Workflow page and click that rule to see its trigger and conditions. Conditions are checked once, after the delay, using the candidate’s scores at that moment; later changes to a score don’t undo the action.
No. Actions taken by an automation don’t start other automations. If a rule moves a candidate to a step, a second rule with the Candidate Moved to Step trigger won’t run for that move. Put all the actions you need in the same rule instead.
Only to events that happen after the rule is turned on. A rule doesn’t look back at candidates who already completed the activity or reached the step. Candidate Time in Step Reaches acts on candidates as they reach the time you set, not on those already past it.
Check that the rule is on, and that it’s on the version of the workflow the candidate is on. Then check whether the score was ready when conditions were checked. If an activity is still waiting on scores, use Activity Status Changes To with Complete, or increase the delay. Also check that another rule didn’t move the candidate first, since automations don’t trigger each other.
After the delay you set (2 minutes by default), plus a short time for processing. Rules that share the same trigger are checked together, after the shortest delay among them, so give them the same delay. Emails and texts with Delay Days or Delay Hours go out later, as scheduled.
Yes, as many as you need, each with its own trigger, conditions and actions.
A rule’s place in the flow follows its trigger. If you change the trigger to point at a different step or activity, the rule moves there.
Yes. Duplicating a job req copies its automation rules along with its steps and activities. Check them on the copy, especially rules that assign specific users or send candidates to another job req.
Any active or inactive job req in your account, other than the one the rule is on. Closed and archived job reqs aren’t listed. The candidate’s application on the current job req stays as it is.

Build a workflow

Steps and activities your rules act on.

Publish workflow changes

How rule changes in a draft reach candidates.

Candidate assignment

Default assignees, bulk assignment and automation.

How scoring works

What the scores in your conditions mean.