Recipes let you automate the repetitive stuff in your recruiting workflow — sending emails, notifying teammates, triggering follow-ups — every time a candidate hits a specific stage or status. Here are the use cases recruiters reach for most.
Use case 1: Send a disqualification email
When a candidate is disqualified from a stage (typically Applied or Application Review), a Recipe sends them a polite rejection email automatically. No more forgetting to close the loop.
This use case has its own walkthrough, see Send a disqualification email automatically.
Use case 2: Send a take-home assignment
When a candidate moves to the Take-Home Test stage, a Recipe sends them the assignment instructions and any attached files. The recruiter never has to copy/paste a brief or remember to attach the spec.
Use case 3: Send a scheduling email at phone interview stage
When a candidate moves to Phone Interview, a Recipe triggers a scheduling email — usually with a Calendly or scheduling link. The candidate picks a time without anyone chasing them.
Use case 4: Notify the team at the offer stage
When a hiring manager moves a candidate to Offer, a Recipe notifies your offer-letter desk, finance, or anyone else who needs the heads up. Nothing falls through the cracks.
What every Recipe has in common
Each Recipe pairs a trigger (something that happens to a candidate — disqualified, moved to a stage) with an action (send an email, send a notification, etc.). You scope the Recipe to all jobs or specific jobs and turn it on.
Things to know
A Recipe applies going forward only. Candidates who already hit the trigger event before you turned the Recipe on won't receive the email or notification.
Recipes scoped to all jobs are workspace-wide. Always double-check the scope before turning a Recipe on if you only want it to run on one team's roles.
Email-sending Recipes use the candidate's email address on file — confirm the address before relying on the Recipe.