Recipes let you automate repetitive actions in Recruiterflow — sending emails, moving candidates, creating tasks, updating fields, and more — without any manual work each time the trigger fires.
What is a Recipe?
A Recipe is an automation rule made up of three parts: a trigger (what starts the recipe), optional filters (which records it applies to), and an action (what Recruiterflow does automatically). You can chain multiple triggers in one recipe — the action fires when any one of them is satisfied, but only once per record even if all triggers match.
How to create a Recipe
Go to the Recipes page in the main navigation.
Click Create Recipe.
Choose your trigger — the event that starts the automation.
Optionally, add filters to narrow which records the recipe applies to (e.g., only candidates from a specific source, or jobs in a specific stage).
Set the action — what Recruiterflow should do when the trigger fires.
Save and activate the recipe.
Triggers
A trigger is the event that kicks off the recipe. Recruiterflow supports triggers across candidates, jobs, companies, and deals — including stage changes, applications, sourcing, disqualification, job-level events, post-placement events, and date-based conditions. For details on each trigger type, see the related articles below.
Filters
Filters narrow the recipe's scope. For example, you can run a recipe only on candidates from a specific source, or only on jobs with a particular status. Leaving filters empty means the recipe runs on all records that match the trigger.
Actions
Actions are what Recruiterflow executes when a recipe fires. Available actions include moving a candidate to a new stage, sending an email or text message, adding a candidate to a campaign, creating a task, and automatically updating fields on candidate or contact profiles. You can also set a delay so the action fires a set amount of time after the trigger — useful for sequences that need to feel less automated.
A practical example
Your team gets a high volume of applicants who don't meet the minimum requirements. Instead of sending rejection emails manually, set up a recipe: trigger on "Candidate disqualified" from the Applied stage → action: send rejection email using your rejection template. Every disqualified applicant gets a timely, professional response with zero manual effort.
Things to know
If a candidate satisfies multiple triggers in the same recipe, the action still fires only once per record.
Recipes can be paused or edited at any time from the Recipes page.
Email delays let you control exactly when automated messages go out after a trigger fires.
Recipes work across candidate, job, company, and deal objects — not just candidate stage changes.
Related articles