Weekly Workable pipeline health report with stalled candidates
Every Monday at 8am, get a short Slack read on what actually needs attention in hiring, plus one spreadsheet row per role that builds a week over week trend.
Every Monday at 8am, publish a hiring pipeline health report for all of our open roles in Workable. Post a written digest to Slack and append one row per open role to a Google Sheets tracker so we build a week over week trend we can look back on.
Start by gathering the current picture. Use the Workable List Jobs operation to get every job that is currently open, and use List Stages to get the recruitment pipeline stages configured on the account so you are working from our real stage names rather than assumed ones. Then use List Candidates, filtered by job and by stage, to count who is actually sitting where. Page through all results so the counts are complete, and skip archived or closed roles entirely.
Then do the analysis. For each open role, work out how many candidates sit in each stage. Identify stalled candidates: anyone whose most recent activity or stage change on their candidate record is more than the stale threshold ago. Default the stale threshold to 5 days and expose it as an editable setting at the top of the workflow, since different teams and seniority levels move at different speeds. Flag roles with a thin top of funnel, meaning very few or no candidates in the earliest stages, because those are the roles that will quietly miss their target. Finally, determine which single stage is the biggest bottleneck across the whole pipeline this week, judged by where candidates are piling up and aging rather than raw headcount alone.
Send the digest to Slack using the Slack Bot Send a Message operation. This message must be short and prioritized, not a wall of numbers. Lead with the two or three things that genuinely need action this week, for example the bottleneck stage, a role starving for applicants, or a cluster of candidates going cold. Under that, name the stalled candidates individually alongside the role they are in, how long they have been sitting, and the recruiter or hiring manager who owns them, taken from the owner or hiring team information on the candidate and job records. If no owner is present, list the candidate under their role rather than guessing at a name. Keep the per stage counts to a brief supporting summary and point people to the spreadsheet for the full numbers.
Then log the data using the Google Sheets Append Values operation. Append one row per open role to the tracker, capturing the run date, the role name, the candidate count in each stage, and the stalled candidate count for that role. Keep the column order stable every week so the sheet accumulates a clean trend rather than a shifting set of columns.
Make the stale threshold in days, the thin top of funnel threshold, the destination Slack channel, and the target spreadsheet and tab into editable settings. This workflow is read only against Workable: it reports on the pipeline and never modifies candidates, moves anyone between stages, or contacts a candidate. If a week has nothing urgent, say so plainly in one or two lines instead of padding the message.
What does this prompt do?
- Every Monday morning, reviews every open role in your recruiting system and counts how many candidates are sitting in each stage of your hiring process.
- Finds the candidates who have not moved in over five days and names them in the update alongside the recruiter responsible for them.
- Posts a short, prioritized Slack digest that leads with the two or three things your team should act on this week instead of a wall of numbers.
- Adds one row per open role to a spreadsheet each week, so you build a running history of how your hiring pipeline moves over time.
What do I need to use this?
- A Workable account with your open jobs and candidates in it
- A Slack workspace and a channel where the weekly update should be posted
- A Google account and a spreadsheet to use as the ongoing hiring tracker
- A rough idea of how many days a candidate can sit still before you consider them stalled
How can I customize it?
- Change the stalled threshold from five days to whatever matches your hiring speed, or set a shorter one for senior roles
- Pick the day and time it runs, and the Slack channel or group it posts to
- Adjust what counts as a thin top of funnel, and choose which stages to include or ignore in the counts
FAQs
Will this work if we only have a few open roles?
Does it move candidates or message them?
Why five days for a stalled candidate?
What if a candidate has no recruiter assigned?
Can it post somewhere other than Slack?
Related templates
When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.
Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.
Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.
Every weekday at 7am, sign in to the tender portals you track, filter new notices against your bid criteria, and open a deal for the ones worth chasing.
Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.
Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.
Stop rebuilding the pipeline picture by hand every Monday.
Get a prioritized read on your hiring pipeline in Slack every week, with the trend quietly accumulating in a spreadsheet behind it.