Automation triggers and actions
An automation rule has one trigger (When), any number of conditions (Only if) and up to 20 actions (Do this). This page lists each one with the name the rule editor shows. How to build a rule is in Automations.
Triggers
Section titled “Triggers”A rule runs for an application. The triggers marked “Driver file” also run for a hired driver who has no open application: see Runs about a hired driver.
| Trigger | When it fires | Options |
|---|---|---|
| Application created | A new application arrives from any channel. | None |
| Moved to another stage | The application changes stage. | From stage and To stage, each optional (Any stage) |
| Marked as not qualified | The application is marked not qualified. Every other pending action of the application is canceled. | None |
| Candidate withdrew | The application is marked withdrawn. Every other pending action of the application is canceled. | None |
| Hired | The candidate is hired. Every other pending action of the application is canceled. | None |
| Call logged | A recruiter logs a call. | Call outcome: Reached, No answer, Left voicemail, Wrong number, Call back later, or Any outcome |
| Message received | The candidate sends an SMS or an email. | None |
| Message failed | A message to the candidate fails. | None |
| Interview scheduled | An interview is booked. | None |
| Interview canceled | An interview is canceled. | None |
| Interview completed | An interview is marked completed. | None |
| Interview no-show | An interview is marked no-show. | None |
| Task overdue | A task of the application passes its due date. | None |
| Application stalled in a stage for N days | The application has been in the same stage for the number of days. Checked every hour. | Days in the same stage, 1 to 365 |
| Full application sent to the candidate | The first full application link is sent. | None |
| Full application signed | The candidate signs the full application. | None |
| Offer accepted | The candidate signs the offer. | None |
| Offer declined | The candidate declines the offer. | None |
| Offer expired | The offer passes its valid date without an answer. | None |
| A document was sent by the driver (Driver file) | The driver or candidate sends a document for an item. | Item type: a section of the driver file, or Any item |
| A document was approved (Driver file) | A document of an item is approved. | Item type |
| A document was rejected (Driver file) | A document is sent back. | Item type |
| A document is expiring in N days (Driver file) | An item reaches an alert day before it expires. | Days before it expires: one of your alert days, or 0 for the day it expires; Item type |
| A document expired (Driver file) | An item expires. | Item type |
| Eligibility for dispatch changed (Driver file) | The driver becomes eligible, or stops being eligible. | Eligibility: Became eligible for dispatch or Is no longer eligible for dispatch |
| Onboarding completed (Driver file) | The onboarding of the driver is completed. | None |
Application stalled in a stage for N days finds an application only during the 7 days after it crosses the line. A rule you turn on today does not reach an application that stalled more than the number of days plus 7 ago. Items of the drug and alcohol file never start a rule.
Conditions
Section titled “Conditions”Every condition must be true when the rule starts, and again before each action. A condition with a list of values is true when the application has one of them (up to 50 values).
| Condition | What it reads | Values |
|---|---|---|
| Job | The job of the application | Jobs of your company |
| Current stage | The stage the application is in now | Stages of your pipeline |
| Source channel | Where the candidate came from | The source channels |
| Campaign | The campaign of the application | Campaigns of your company |
| Lead score range | The lead score | Minimum score and Maximum score, 0 to 1,000; an application without a score is in no range |
| Recruiter | The recruiter of the candidate | Members of your company |
| Language | The language the candidate prefers | English, Spanish |
| Has SMS consent | Whether the candidate agreed to text messages | Yes or No |
| Has an email | Whether the candidate has an email address | Yes or No |
| Driver type | The driver type of the driver file | CDL, Non-CDL, Owner-operator |
| Employment type | The employment type of the driver file | Employee, Independent contractor, Owner-operator |
| Overall compliance status | The status of the driver file | Compliant, Pending, Expired |
The last three are not met while the application has no driver file yet.
Actions
Section titled “Actions”Each action has a Wait before (in Minutes, Hours or Days, at most 90 days) counted from the action before it, or from the trigger for the first one.
| Action | What it does | Ends as Skipped or Failed when |
|---|---|---|
| Send an SMS with a template | Sends an SMS message template to the candidate. | The template is archived or is not for SMS; the sending service refuses it (no consent, opted out, daily limit, allowed hours wait) |
| Send an email with a template | Sends an email message template to the candidate. | The template is archived or is not for email; the sending service refuses it |
| Send the scheduling link of an interview type | Sends the system template Scheduling invite, by SMS or email, with a new scheduling link for the Interview type. | The interview type is archived; the company has no Scheduling invite for that channel |
| Send the link of the candidate area | Sends the system template Candidate portal link, with a link to the candidate area. | The sending service refuses it |
| Send an offer from a template | Sends an offer from the Offer template, in the Language of the offer, open for 1 to 60 days (Open for (days)). | The application already has an open offer, or this run already sent one. The template cannot use {start_date}, {pay} or {benefits} |
| Create a task | Creates a task with the Task title, due after Due in, for The recruiter of the application or A user. | The application has no recruiter |
| Move to a stage | Moves the application to an open Stage. | The application is already in that stage |
| Assign a recruiter | Makes the User the recruiter of the candidate. | The user already is the recruiter |
| Enroll in a sequence | Enrolls the candidate in the Sequence. | The candidate is in the sequence, or was in the last 30 days |
| Remove from every sequence | Takes the candidate out of every sequence. | None |
| Notify a user by email | Emails a member of your company about the candidate. | None |
| Send the full application | Sends the full application link, by email when the candidate has one, otherwise by SMS, or by the channel you choose in Send by. | A full application was already sent for this application |
| Start pre-hire screening | Creates the pre-hire screening requests of the application. | Every pre-hire screening request already exists |
How a run goes
Section titled “How a run goes”- The Run history of a rule shows each run as Running, Completed, Failed or Canceled, and each action as Done, Skipped, Failed, Scheduled for a time, Waiting for the action before it or Canceled, with the reason.
- An action that hits an unexpected error is tried 3 times in all before it ends as Failed.
- When the application leaves the pipeline (hired, not qualified, withdrawn or closed), its pending actions are canceled. Turn off and Archive cancel the pending actions of the rule.
- An action can start another rule. The chain stops at a depth of 3: a run started that deep has every action skipped.
Runs about a hired driver
Section titled “Runs about a hired driver”The triggers marked “Driver file” run for the person once the driver is hired. In such a run:
- Only Notify a user by email runs. Every other action ends as Failed with
not_applicable. - Only Driver type, Employment type and Overall compliance status can be met. A rule with any other condition does not run for a hired driver.
Planned
Section titled “Planned”| Item | Status |
|---|---|
| Platform > Automations: rules that run actions across every module, in one place. The menu shows it as Coming soon. See Platform automations. | Planned |