Use cases for workflow automations

• Send an email to HM after a few months of hiring someone, asking them to do a retro review of the interview process/questions/calibration with the benefit of knowing the on-the-job performance of the new hire. Did we ask right questions? Which interviewer was accurate? Who needs coaching? 
• A hyper-customized candidate experience survey for a specific Department / Location / even a job title. 
• Send branding or interview prep documents to candidates based on their stage in the interview process. You can further narrow it to a specific segment of candidates based on location and department. 
• Notifying employees as their referrals advance through the loops. 
• If the Hiring Manager shortlists the resume, automatically trigger the interview schedule request.

Hi ​@shragr, here are some additional context / Workflow automation use cases I’ve worked with / seen customers ask for

• Post-interview follow-up communications (candidate comms). I’ve seen customers look for a way to trigger a follow-up email after an interview has taken place, and since an “interview completed date” trigger isn’t always available, a common workaround is to trigger off a stage change (e.g., moving the candidate to a “Post-Interview” stage) and send the email from there.
• Automated candidate “keep warm” nurture sequences. I’ve seen customers set up workflows to email candidates every 7–10 days to keep them warm—then run into the issue that follow-ups can continue even after the candidate is rejected/progressed if there isn’t a clean “end when status changes” control.
• Feedback request automations + reminders. Multiple automation requests I’ve worked with are about improving the feedback loop:
  • Ensuring reminders don’t send after a hiring manager already completed the feedback form.
  • Making sure the right person is treated as the requester/owner of automated feedback actions (so recruiters get what they need without admins becoming the “owner” of everything just because they built the workflow).
• Scheduling and coordination efficiency. I’ve seen automation requests like automatically assigning scheduling requests to a coordinator (instead of requiring “assign to me” flows).

Best practices I use / recommend for workflow automation

1) Design around the reality that automations are trigger-based—and “stop conditions” may be limited

If your process depends on stopping future actions once someone advances/rejects a candidate, validate early whether the automation framework supports that. When it doesn’t (as in the candidate nurture example), you’ll need to redesign (often around stage changes) or accept manual guardrails. 
 

2) Use stage changes as the most reliable “switch”

When a customer wants a time-based action tied to an interview date (or post-interview moment) and the platform doesn’t offer that exact trigger, anchoring your automation to a clear stage transition is usually the cleanest pattern.

3) Be explicit about workflow “ownership” and notification routing

In Workflow Automation Center behavior I’ve documented/escalated, the creator/last editor of the workflow can become the owner of actions triggered—so notifications, feedback receipts, etc., may go to the admin instead of the recruiter unless you design around it (e.g., personal workflows, or product-supported changes for certain workflow types).
 

4) Treat reminders as part of the task lifecycle—not just a timed email

If reminders are configured only as part of the automation and the system can’t detect completion correctly, you can end up with “nag” emails after completion. The best practice is to ensure reminders are tied to the feedback task/form lifecycle in a way that can stop once completed (or advocate for that capability when it’s missing).
 

5) Show outcomes, not just configuration, when enabling others

From feedback I’ve received on automation-focused sessions, the most valuable enablement includes what the workflow looks like when it runs (before/after), not just how to build it—because that’s what helps teams trust the automation and understand the time saved.
 

6) Keep the experience customer-led when sharing automation best practices

When I’m helping set up customer-facing sessions (like Value Spotlight), what consistently works is emphasizing peer examples: where they started, what they built, what changed, and what they’d do differently—rather than Eightfold talking the whole time.