Weekly Workable pipeline health report with stalled candidates

By General Input

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.

Integrations

  • Workable
  • Slack Bot
  • Google Sheets

Type

Agentic Task

Categories

  • HR & People
  • Operations

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.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentLocal listing health board for every location you manageLet support send one-off Loops emails without an engineerA brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensStop cold emails to anyone with a live deal in PipedriveLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasoniMessage campaign console with pre-flight checks and delivery board