We have provided concise descriptions of triggers available for ATS Automation in Recruitly to aid your understanding.
ATS Automation Triggers
Tip:
To learn more about an action, click on the "?" icon for further information. Refer to below image for reference:
Important:
Multiple steps/actions can be included in a single trigger to target records in various scenarios.
Job is about to expire:
When a job is nearing expiration in the system, actions can be set up to send notifications, add tasks, or send emails to the job owner and concerned users. Filters can be applied to target specific groups of records.
Job has expired:
Once a job has expired, multiple actions can be taken such as closing the job, updating the job status, rejecting pending candidates, removing it from websites or job boards, etc., and more. Filters can be applied to target specific groups of records.
No activity for candidates:
If there has been no activity for a candidate within a specific timeframe, actions can be triggered to send emails, add records to sequences, or take other relevant actions, etc., and more. Filters can be applied to target specific groups of records.
Job is added to the system:
When a job is added to the system, actions like sending notifications or adding tasks to the job owner can be executed. Filters can be applied to target specific groups of records.
Job application received:
Upon receiving a job application in the system, actions such as sending emails to selected email senders or to the candidate can be initiated, etc., and more.
Job interview is due:
As a job interview approaches, reminders via email and SMS can be sent to the contact and candidate.
Candidate CV is shared (CV Share):
When a candidate's CV is shared using the CV share feature, the candidate can be notified via email.
Placed candidate has started:
Once a placed candidate begins their job, actions like sending emails to the candidate, record owner, and contact can be performed, etc., and more. Filters can be applied to target specific groups of records.
Placed candidate is about to start:
Prior to the start date of a placed candidate, actions such as sending emails to the candidate, record owner, and contact can be initiated, etc., and more. Filters can be applied to target specific groups of records.
Placement is created:
Upon creating a placement in the system, actions such as sending emails to the candidate, record owner, and contact, or closing the job can be executed, etc., and more. Filters can be applied to target specific groups of records.
Candidate is added manually:
When a candidate is manually added to the system, actions like sending emails to the candidate, record owner, or adding the candidate to a sequence can be taken, etc., and more.
Candidate added to job pipeline:
Upon adding a candidate to a job pipeline, emails can be sent to concerned users like the job owner or pipeline owner. Filters can be applied to target specific groups of records.
Placement invoice creation is due:
When a placement is created but the invoice creation is pending, a reminder email can be sent to the placement owner.
Placement nearing end date:
For contract placements, when the contract end date is approaching, actions such as sending emails to the placement owner, contact, and candidate can be initiated, etc., and more. Filters can be applied to target specific groups of records.
Candidate pipeline status is updated:
Upon updating a candidate's pipeline status after adding them to a job, actions can be triggered to send them an email based on the changed status for specific stages/pipelines.
Job status is open:
When a job status remains open for a certain number of days, actions such as closing the job or sending notifications to the job owner can be taken. Filters can be applied to target specific groups of records.