Hiring automation
Build hiring rules in the ATS: triggers on apply or stage change, branches on AI Score, emails, pipeline moves, and team alerts.
Define when a rule runs, what conditions must pass, and which actions fire next. Each run leaves a trace on the candidate so your team can see what happened and when.
Example automation: strong applicants skip the queue
One rule you can build for a software engineer role looks like this from the candidate's perspective:
- Trigger: new application A candidate submits to the role. The rule starts as soon as the application is stored.
- Action: acknowledgment within five minutes The ATS sends your acknowledgment template so the applicant sees a reply quickly while you are in meetings.
- Condition: AI Score above 80 After AI Score runs, only applicants who clear the bar continue down this branch.
- Action: move to Phone Screen The candidate's stage changes to Phone Screen. Your pipeline view and reports show them in the right column.
- Action: notify hiring manager in Slack A message goes to the manager's channel or DM with the candidate name, role, score, and a link back to the profile in Canvider.
How it works
- Choose a trigger Start from an event such as a new application to a specific job, a stage change, or a score crossing a threshold after AI Score finishes.
- Add conditions and actions Chain steps like a timed acknowledgment email, a branch when AI Score is above 80, a move to Phone Screen, and a Slack message to the hiring manager.
- See each run on the candidate Open the candidate profile to read which emails went out, which stage they are in now, and the timestamped log for that automation. Fix a rule and the next applicant picks up the change.
Why use it?
- Candidate emails you can trust Send acknowledgment, interview invite, rejection, or custom template messages from the ATS. Each send appears on the candidate timeline with subject and time so nobody double-emails by mistake.
- Pipeline status that updates itself Rules move applicants between stages when conditions match, for example from Applied to Phone Screen after a strong AI Score. Filters and reports reflect the new stage without manual drag-and-drop for every hire.
- Scheduling and handoffs your team actually uses When your flow includes calendar holds or internal tasks, those items are created from the same rule so the recruiter and hiring manager see the same next step. Slack or email notifications fire when a handoff is ready.
What the automation builder looks like
In Canvider you work in a single rule editor per job or template. At the top you pick the trigger (for example New application). Below that, steps stack vertically: each row is either a condition, a delay, or an action. Conditions show fields like AI Score or stage; actions list email templates, change stage, or send a webhook or Slack notification depending on your workspace setup. You can name the rule, turn it on or off, and open a recent run list to see which candidates matched and whether each step succeeded. There is no separate flowchart canvas: it reads like a checklist the whole team can understand.