When you accept a Job Change Alert in Recruiterflow, something important just happened — a candidate moved to a new company, or a contact just became a hiring manager. The question is: what happens next?
Without automation, the answer is: nothing, until someone on your team manually follows up. With Recipes, you can change that. The moment an alert is accepted, Recruiterflow can automatically send an email, create a task, add the person to a sequence, or update a field — no manual work required.
This article explains how to set that up.
New to Job Change Alerts or Recipes? Read these first:
— Using Job Change Alerts in Recruiterflow
— Creating Recipes in Recruiterflow
The Two New Triggers
Recipes now support two new triggers specifically tied to Job Change Alerts:
A candidate job change alert is accepted — fires when you accept an alert confirming a candidate has switched jobs
A contact job change alert is accepted — fires when you accept an alert confirming a contact has moved to a new role or company
Both triggers fire at the moment of acceptance — individually, in bulk, or via auto-accept. The recipe runs immediately after the alert is accepted, regardless of how it was accepted.
How to Set Up the Recipe
Go to Recipes in the main navigation panel
Click +New Recipe
Under Triggers, select either "A candidate job change alert is accepted" or "A contact job change alert is accepted"
Apply any filters if needed — for example, run this recipe only for contacts in a specific industry or candidates with a certain source
Choose your Action — what Recruiterflow should do the moment the alert is accepted
Save and activate the recipe
Recipe Ideas by Use Case
Contact becomes a hiring manager — reach out immediately
This is the highest-value use case. When a contact moves into a hiring role, your window to win the deal is short. A recipe ensures no one falls through the cracks.
Trigger: A contact job change alert is accepted
Action: Send an email to the contact using a congratulations + outreach template, or create a task for the owner to call within 24 hours
Example email angle: "Congrats on the new role at [Company] — we'd love to support your hiring as you build out the team."
Candidate switches jobs — re-engage them
A candidate changing jobs is the right moment to check in, not six months later.
Trigger: A candidate job change alert is accepted
Action: Add the candidate to a re-engagement email sequence, or send a direct email checking in on their new role
Auto-update fields and keep your database clean
Use the trigger to automatically update profile fields the moment a job change is confirmed — so your database stays accurate without manual cleanup.
Trigger: A candidate or contact job change alert is accepted
Action: Update a custom field (e.g., "Last Job Change Date", "Re-engagement Status") to reflect the confirmed change
Notify the record owner instantly
If your team reviews alerts in bulk, the owner of a record may not realise their candidate or contact just accepted an alert. A recipe can ping them immediately.
Trigger: A candidate job change alert is accepted or a contact job change alert is accepted
Action: Create a task assigned to the record owner to follow up within a set timeframe
Things to Know
These triggers fire whether the alert was accepted individually, in bulk, or via the auto-accept setting. If you use auto-accept, the recipe will run automatically without any manual action from your team.
Dismissed alerts do not fire either trigger. The recipe only runs on accepted alerts.
Job Change Alerts are part of Recruiterflow's AIRA Plan. If you don't see these triggers in your Recipes, you can update your plan here: AIRA Plan Upgrade