Set the rule once. The pipeline runs it every time.
Build automations the way you would say them out loud: when this happens, if the candidate looks like this, then do that — otherwise do something else. Hireall runs the rule on every applicant, waits when you tell it to wait, and writes down exactly what it did.
The repetitive half of recruiting, handled while you sleep.
Automations live on your pipeline stages, so a rule is always attached to a real step in a real job — not buried in a separate workflow tool.
Three triggers
A rule fires when a candidate applies, when you move them into a stage, or when they finish a test. Pick the moment that matches the work you keep repeating.
Conditions that filter
Screening answers, AI fit score, university, department, GPA, city, country and more. Combine them with “all must match” or “any must match” — or add none and treat everyone the same.
Five actions
Move to a stage, send an e-mail from your templates, add an internal note, calculate an AI fit score, or draft an offer for approval. Each action runs immediately or after a delay you set.
Immediate or delayed
Every action carries its own timing — right now, a few hours later, or a few days later. Chain them and one rule becomes a small sequence.
A sending window
Delayed steps that land at 03:00 or on a Sunday wait for the next open slot, on the days and hours you choose and in local time. Immediate steps still fire on the spot.
A log for every run
Executed, skipped or failed — with the reason attached. When a rule does nothing you can see why instead of guessing.
Rejections with reasons
Record a reason on every rejection and let the rejection e-mail go out on a delay you set — so no candidate hears back instantly, and none is forgotten.
Three blocks. Every rule you will ever write is made of them.
These are the actual options in the builder today, not a wish list.
Something happens
- A candidate applies
- You move someone into the stage
- A test is completed
The candidate looks like this
- Screening answer
- AI fit score
- University
- Department
- GPA
- City
- Country
- Language
equals · is one of · greater than · less than. Combine with all-must-match or any-must-match. Leave it empty and the rule applies to everyone.
Do this, now or later
- Move to a stage
- Send an e-mail template
- Add an internal note
- Calculate the AI fit score
- Draft an offer for approval
Each action runs immediately or after hours or days. Add an Else branch for everyone who does not match.
If this, then that — and an Else for everyone who does not match.
A rule is three blocks. The trigger says when it runs. The conditions say who it runs for — screening answers, AI fit score, or profile fields like university and city, compared with equals, is one of, greater than or less than. The actions say what happens, in the order you list them. Add an Else branch and the candidates who fail the condition get their own treatment instead of being left in limbo: matching applicants move to Interview, the rest to Under review with a note.
A rule that can wait is a rule you can actually use.
Not everything should happen the instant a candidate lands in a stage. Give any action a delay — hours or days — and it goes into a queue instead of firing. Delayed steps respect a sending window, so a step that would land at 3am or on a weekend slides to the next working hour. And if the candidate moves on, gets hired or is rejected in the meantime, the queued step is cancelled rather than sent into a situation that no longer exists.
Automation you can hand to a colleague without holding your breath.
Every run writes a record: which rule, which candidate, which action, and whether it executed, was skipped or failed — with the reason in plain words. A chain can only go ten steps deep, so a rule can never end up triggering itself in a loop. If a template is deleted or a feature is no longer available, the step is skipped and logged instead of failing silently. Test a new rule on one candidate, read the log, then turn it loose on the whole pipeline.
The work nobody puts on a job description.
Acknowledging, chasing, routing and closing the loop — the tasks that quietly eat a recruiting week.
Sorting hundreds of applications
Score, filter and route on the way in, so the shortlist is already forming before anyone opens the list.
- AI fit score calculated on application
- Strong matches moved on automatically
- Everyone else gets a reply, not silence
The chasing you keep forgetting
Reminders, nudges and timed rejections that go out on schedule instead of whenever someone remembers.
- Nudge a few days after an invite
- Delayed rejections that never feel instant
- Cancelled the moment the candidate replies
Stage changes that carry their own paperwork
Moving someone to a stage should trigger the paperwork that stage needs — the fit score, the note for the hiring manager, the offer draft.
- Fit score recalculated on stage entry
- Internal note left for the hiring manager
- Offer drafted and waiting for approval
What teams ask before they switch a rule on
How automations behave inside Hireall.
On your pipeline stages. Open a job's pipeline, click the stage, and add rules under the trigger blocks — On application, On manual move, or On test completion. A rule always belongs to a stage, so its scope is obvious to whoever inherits the job.
Move the candidate to another stage, send an e-mail from your templates, add a note to the profile, calculate an AI fit score, or draft an offer. Each action runs immediately or after a delay you set. Video interview invites, tests and document requests are sent from the candidate profile, and interviews are scheduled from the calendar.
Yes — that is what conditions are for. Filter on screening question answers, AI fit score, or profile fields such as university, department, GPA, city and country, using operators like equals, is one of, greater than and less than. Add an Else branch to define what happens to everyone who does not match. With no conditions at all, the rule applies to every candidate.
The step is cancelled and logged as skipped, with the reason — the candidate left the stage, or was rejected. Automations never chase someone into a situation that has already changed.
No. Delayed steps are held to a working-hours window and slide to the next open slot when they would otherwise land overnight or at the weekend. Immediate steps still send straight away, because those are the direct response to something a recruiter just did. The window runs in your company's time zone, or the job's for candidate e-mails, and you can set your own days and hours — see the time zones page.
Automation is part of the pipeline — there is no separate workflow product to buy. See the pricing page for plan details.
Automation is part of the pipeline, not a separate product.
No per-rule fee, no workflow add-on, no third-party automation tool to connect. Build as many rules as your stages need.
Talk to our team
Tell us about your roles and team size — we'll map Hireall to your hiring process and the plan that fits.
Contact sales Priced per company, not per seat