> ## Documentation Index
> Fetch the complete documentation index at: https://help.journeyfront.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This is the Journeyfront Help Center for hiring teams. Journeyfront is an applicant tracking system (ATS). Use the Help Center's terms: job req, Candidate Profile (the person), Candidate Application (one person on one job req), hiring class. Link to the article you used in your answer.

# Automation rules

> Act on candidates automatically when something happens in a job req's workflow: move them, message them, assign them or route them.

> [!NOTE]
>
> **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](https://help.journeyfront.com/communication/text-messages.md).

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.

[Automations | Journeyfront Feature Walkthrough](https://www.youtube.com/embed/hJMSs9qjwXw)

## 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](https://mintcdn.com/journeyfront/Ki8OScNKQAoeTHdj/images/workflows/automation-rules/gen-automation-in-flow.png?fit=max\&auto=format\&n=Ki8OScNKQAoeTHdj\&q=85\&s=a030ee89dc88b8b08014754538e7a9d2)

## 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](https://mintcdn.com/journeyfront/MP6XVW1Unu3e4opR/images/workflows/automation-rules/automation-add-bolt.png?fit=max\&auto=format\&n=MP6XVW1Unu3e4opR\&q=85\&s=997c78816301300238f5102441bb1a4d)

**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](https://mintcdn.com/journeyfront/Ki8OScNKQAoeTHdj/images/workflows/automation-rules/gen-automation-editor.png?fit=max\&auto=format\&n=Ki8OScNKQAoeTHdj\&q=85\&s=d5b2ad7051b5d47e84d31c168850e601)

**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**.

> [!TIP]
>
> 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](https://help.journeyfront.com/workflows/publish.md).

> [!TIP]
>
> 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

| Trigger | Runs when | You also choose |
| - | - | - |
| **Candidate Application is Created** | A new Candidate Application is created on this job req: someone applies, or your team adds or imports them. | Nothing else |
| **Candidate Completes Activity** | A candidate finishes the chosen activity. | **Activity** |
| **Activity Status Changes To** | The chosen activity reaches the chosen status, for example an interview becoming **Scheduled** or an offer becoming **Offer Accepted**. The statuses depend on the activity type. | **Activity** and **Status** |
| **Candidate Moved to Step** | Someone moves the candidate into the chosen step, for example with **Change Step**. | **Step** |
| **Candidate Completes Step** | A candidate finishes all the activities in the chosen step. | **Step** |
| **Candidate is Hired** | The candidate is hired. | Nothing else |
| **Candidate is Rejected** | The candidate is rejected. | Nothing else |
| **Candidate Time in Step Reaches** | A candidate has been in the chosen step for the time you set. | **Step**, and the time in **Days** and **Hour** |

> [!TIP]
>
> 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**.

| Condition | What it checks |
| - | - |
| **Overall score is** | The candidate's overall score on this job req. |
| **Activity score is** | The score on one activity you choose. |
| **Attribute Score is** | The score on one attribute you choose. See [Attributes](https://help.journeyfront.com/scoring/attributes.md). |
| **Attribute group score is** | The score on one attribute group you choose. Also offers **Is Highest**: true when this is the candidate's highest attribute group score (ties count). |
| **Predictive model score is** | The score from one of the job req's predictive models. Also offers **Is Highest**. See [Predictive models](https://help.journeyfront.com/scoring/predictive-models.md). |
| **Activity Status is** | Whether one activity you choose has a particular status, like **Not Started** or **Complete**. |
| **Status is** / **Status is Not** | The application's status: **Incomplete**, **New**, **Active**, **Hired**, **Rejected** or **Withdrawn**. |
| **Source** | Where the candidate came from. |
| **Hiring Class** | The candidate's hiring class on this job req. |
| **Assigned User** | Who the candidate is assigned to. |
| **Fraud Risk Level** | The application's fraud risk level: **Low**, **Medium** or **High**. See [Fraud flags](https://help.journeyfront.com/candidates/fraud-flags.md). |
| **Candidate Country**, **Candidate State/Region**, **Candidate City**, **Candidate Zip Code** | The location from the candidate's address. Pick a country or state from the list; type a city or zip code. |
| **Application Field** / **Personal Field** | One of your account's custom fields. Pick the field, then a value; what you can enter depends on the field type. See [Custom fields](https://help.journeyfront.com/account-setup/custom-fields.md). |

![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](https://mintcdn.com/journeyfront/Ki8OScNKQAoeTHdj/images/workflows/automation-rules/gen-conditions.png?fit=max\&auto=format\&n=Ki8OScNKQAoeTHdj\&q=85\&s=8601bf4b54c10d4e8197d5131e571ab9)

**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](https://mintcdn.com/journeyfront/MP6XVW1Unu3e4opR/images/workflows/automation-rules/automation-actions-list.png?fit=max\&auto=format\&n=MP6XVW1Unu3e4opR\&q=85\&s=3ee51d7c014632d8fde7452965b19b53)

| Action | What it does | You fill in |
| - | - | - |
| **Assign User** | Assigns the candidate to a user, replacing anyone already assigned. With **Multiple Users(Random)**, Journeyfront picks one of the users you list at random each time. | **Assign Method** (**Single User** or **Multiple Users(Random)**) and **Select Users** |
| **Change candidate step to** | Moves the candidate to another step. Tick **Send email inviting user to complete the next step** to email the candidate a link to continue. | **Step** |
| **Reject candidate** | Rejects the candidate with the reason you choose. It doesn't email the candidate; add a **Send Email to Candidate** action for that. | **Reject Reason** and optional **Reject Notes** |
| **Send Email to Candidate** | Sends one of your email templates. | **Email template**, and optional **Delay Days** and **Delay Hours** |
| **Send SMS to Candidate** | Sends one of your text message templates. It isn't sent to candidates who aren't opted in to texts or who are blocked. | **Message template**, **From Phone Number**, optional delay |
| **Send WhatsApp Message to Candidate** | Sends one of your approved WhatsApp templates, to candidates opted in to WhatsApp. Only listed once WhatsApp is connected. | **Message template**, **From Phone Number**, optional delay |
| **Set Hiring Class** | Puts the candidate in one of this job req's active hiring classes. | **Hiring Class** |
| **Add to Other Job Req** | Creates a Candidate Application on another job req. Skipped if the candidate already has an application there, or if that job req's re-apply waiting period hasn't passed. | **Target Job Req**, **Transfer Data** (**Transfer All Applicable Data** or **Don't Transfer Data**), and whether to **Send email inviting candidate to complete the application steps** |

See [Candidate assignment](https://help.journeyfront.com/workflows/candidate-assignment.md), [Reject candidates](https://help.journeyfront.com/candidates/reject.md), [Email templates](https://help.journeyfront.com/communication/email-templates.md) and [Add candidates to another job req](https://help.journeyfront.com/candidates/add-to-another-job.md) 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.

> [accordion] Advance candidates who do well on screening questions
>
> * **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.

> [accordion] Nudge candidates who haven't started a test
>
> * **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.

> [accordion] Route candidates by location
>
> * **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.

> [accordion] Reject and notify candidates who don't meet the bar
>
> * **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.

> [!TIP]
>
> 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](https://mintcdn.com/journeyfront/Ki8OScNKQAoeTHdj/images/workflows/automation-rules/gen-automation-ran.png?fit=max\&auto=format\&n=Ki8OScNKQAoeTHdj\&q=85\&s=1e64480db1536b16bcdb868fa75fb269)

## FAQ

> [accordion] Why did a candidate move or get rejected?
>
> 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.

> [accordion] Can one automation trigger another?
>
> 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.

> [accordion] Do new rules apply to candidates who are already in the job req?
>
> 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.

> [accordion] A rule didn't act on a candidate who should have matched. Why?
>
> 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.

> [accordion] How quickly do rules run?
>
> 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.

> [accordion] Can I have more than one rule on a job req?
>
> Yes, as many as you need, each with its own trigger, conditions and actions.

> [accordion] Why does my rule appear under a different step or activity than where I added it?
>
> 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.

> [accordion] Are rules copied when I duplicate a job req?
>
> 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.

> [accordion] Which job reqs can Add to Other Job Req send candidates to?
>
> 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.

## Related

> [card] [Build a workflow](https://help.journeyfront.com/workflows/build.md)
>
> Steps and activities your rules act on.

> [card] [Publish workflow changes](https://help.journeyfront.com/workflows/publish.md)
>
> How rule changes in a draft reach candidates.

> [card] [Candidate assignment](https://help.journeyfront.com/workflows/candidate-assignment.md)
>
> Default assignees, bulk assignment and automation.

> [card] [How scoring works](https://help.journeyfront.com/scoring/how-scoring-works.md)
>
> What the scores in your conditions mean.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.