Interviewer briefs in Slack when Greenhouse candidates hit onsite

By General Input

Every hour, catch candidates moving to onsite or final round in Greenhouse and drop a short briefing in the role's Slack channel with background and a talking point.

Integrations

  • Greenhouse
  • Apollo
  • Slack

Type

Agentic Task

Categories

  • HR & People
  • Operations

Every hour during business hours, prep short interviewer briefings for candidates who just advanced to onsite or final-round in Greenhouse and drop each one into the role's hiring channel in Slack.

Start with Greenhouse List Applications, filtering to applications updated since the workflow last ran. Detect stage changes by comparing the last_activity_at timestamp on each application against the previous run's timestamp, and keep only applications whose current_stage.name matches the onsite or final-round labels this org uses (for example "Onsite", "Final Round", "Executive Interview"). Make the list of qualifying stage names configurable at the top of the workflow so it's easy to tweak.

For each qualifying application, call Greenhouse Get Candidate to pull the candidate's resume, primary email, name, current company, and the job they're interviewing for. Then run Apollo People Enrichment with the candidate's email, name, and current company to get employment history and a LinkedIn URL. Apollo is our stand-in for a LinkedIn lookup — feed whichever identifiers you have for the best match.

Draft a tight 5-to-8-line briefing for each candidate that covers: the role they're interviewing for, two or three background highlights (previous companies, notable roles or projects), one interesting angle for interviewers to ask about (a career pivot, a shipped product, a domain overlap), the LinkedIn URL, and a link back to the candidate's Greenhouse profile. Keep it scannable — this is meant to be read on a phone five minutes before the interview.

Post the briefing to the role's hiring channel with Slack Send a Message. Resolve the channel from a role-to-channel mapping (a naming convention like #hiring-<role-slug> works well as a fallback). Then use Greenhouse Add Candidate Note to attach the same briefing text to the candidate's profile so interviewers who prefer Greenhouse also see it in the activity feed.

Guardrails: never brief the same candidate twice for the same stage transition (dedupe by candidate id + stage name), skip candidates whose Apollo enrichment returns no useful data (post a minimal briefing with just the Greenhouse info rather than a blank one), and log a warning if the role's Slack channel can't be resolved so nothing is silently dropped.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsCandidate texting desk for your open Greenhouse rolesWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsMailjet email delivery lookup console for support teamsCatch feature flags that never got switched on in production