Triggers represent the conditions that must be met so that Autoflow Actions are executed. The basic pieces explained here can be combined to create various flows that will help you automate many processes. In this article, we’ll take an in-depth look at how to set them up.
After you’ve chosen the Folder for which incoming candidates will be checked, you will be prompted to start choosing your criteria.
Criteria
The criteria are based on a Candidate Attribute that will be compared to the desired value using an operator.
So, for example, if we wanted to check if a candidate’s Name is Sam, our Attribute would be “Name”, the operator would be “is”, and the value would be “Sam”. Let’s take a look at each of these pieces:
Candidate Attributes
Candidate Attributes are data points for each candidate. Some Candidate Attributes are determined when the candidates are created in Talkpush (such as Name, Source, Added date), and others after they fill out the Prescreening Questions (this can include Address, Expected Salary, and Age).
In our example above, where we want to check if a candidate’s Name is Sam, the Attribute would be Name. For Autoflow purposes, Attributes can be classified into one of 4 types:
Type | Characteristics | Example Attributes |
Text | A string of text | Name, Address, Source |
Number | A sequence of digits | Age, Expected Salary |
Date | A calendar date with day, month, and year | Added at, Completed at |
Dropdown | Any item from a given dropdown list | Country, Assigned Recruiter |
Note: If you delete one of the Candidate Attributes you used to set up the Autoflow, you'll see a red Disabled text in its place. You may edit the Autoflow to incorporate new Attributes to replace any deleted ones.
Operators
The chosen Candidate Attribute will be compared to your chosen values via an Operator. These tools are determined by what kind of Attribute you are checking for. Operators depend on the type of Attribute chosen.
So in the example above, where we want to check if the candidate’s Name is Sam, the Operator would be is. Here’s a list of operators, along with their relation to the given value, X.
Text Attributes
Operator | Criteria will be true if the attribute… |
is | is exactly X |
is not | is not exactly X |
starts with | contains X at the start |
ends with | contains X at the end |
matched | is X (not case sensitive) |
does not match | is not X (not case sensitive) |
is empty | is not filled |
is present | is filled |
Number Attributes
Operator | Criteria will be true if the attribute… |
is | is exactly equal to X |
greater than | is bigger than X |
less than | is smaller than X |
greater than or equal | is equal to or bigger than X |
less than or equal | is equal to or smaller than X |
is empty | is not filled |
is present | is filled |
Date Attributes
Operator | Criteria will be true if the date… |
on | is exactly X |
after | is later than X |
before | is earlier than X |
is unknown | is not filled |
has any value | is filled |
more than | is before X days ago |
less than | is after X days ago |
exactly | is X days ago |
For Dropdown attributes, the only available operator is is, which works in the same way as described for text attributes.
After choosing your desired operator, you must choose the value to compare to. Please note that for operators that check if an Attribute is filled or not, no value can be chosen.
Values
In the final step for setting your criteria, you must decide the value to compare the Attribute to.
In our previous example, where we want to check if the candidate’s Name is Sam, our Value would be Sam.
For Text attributes, you must type a string of text. For Number attributes, you must input digits.
For Date attributes, you’ll be presented with a calendar to mark your desired date, or a box to input the number of days:
And finally, for Dropdown attributes, you’ll see the dropdown list to select your desired value.
For any given attribute, you may also choose Select Candidate Attribute in order to compare two existing attributes. The available operators for comparison are determined by the first Attribute selected.
You are now ready to set all different criteria for your Autoflow Trigger. Now let’s see how to link criteria together using AND/OR clauses.
AND/OR Clauses
For each Autoflow trigger, you can link together two or more Criteria using AND/OR clauses. This is useful if you need your action triggered by several criteria being true simultaneously or at least one of several criteria to be true.
AND Clause
This clause will be considered true if all criteria are met.
Let’s consider an example, we want our Action to be triggered if the candidate’s age is 21 years or older, AND the candidate has more than 3 years of experience.
In this case, the Action will be triggered only if the candidate meets both criteria. A 25-year-old with no work experience and a 19-year-old with 4 years of experience will not be considered, as they will fail to meet one of the criteria.
OR Clause
This clause will be considered true if at least one of the criteria is met.
Let’s consider an example, we want our Action to be triggered if the candidate was added before January 1, 2022, OR if they have no phone number registered.
In this case, as long as at least one of the criteria is met, the Action will be triggered. So, if a candidate has a mobile number but was added on May 2021, the action will be triggered since they meet one of the conditions. The action will also be triggered if the candidate was added on June 2022 but has no mobile number registered.
After you have linked your Criteria, your trigger is created! Now you’re ready to go to the next step and set your Autoflow Action.
Note: An autoflow cannot reactivate a bot; only candidates, recruiters, or the bulk restart option can do so.
Q: Why isn't my Autoflow triggering after I've updated or modified it? A: Autoflow is not retroactive, meaning it won't automatically apply changes to existing applications. For Autoflow to trigger on an existing application, you must update that specific application. If no changes are made, the updated Autoflow won't activate.
To force the updated Autoflow to trigger, you can move the application out of its current folder (e.g., move it to the "On Hold" folder) and then move it back.
Q: What does "Version" under Autoflows represent? A: The "Version" in Autoflows shows the current version of an autoflow and tracks changes over time. For example, if an Autoflow is labeled as "version 2," any actions triggered by it will also appear as "version 2" in the AP Autoflow logs. When you edit an autoflow, its version number increases (e.g., it becomes "version 3"). This versioning system helps you identify which version of the Autoflow was active during specific actions or events.
|