Screen every new Recruitee candidate before a recruiter opens it
Every new applicant gets a written strengths-and-gaps brief and a triage tag in Recruitee, plus a heads-up in Slack.
Recruitee
Slack BotHR & PeopleDocument ProcessingNotifications & AlertsWhen a new candidate is created in Recruitee, I want an AI screening brief written back into the candidate record before a recruiter ever opens it. Trigger this workflow from a Recruitee webhook on the candidate created event.
Start by calling Get Candidate with the candidate ID from the webhook payload to pull the full profile, including CV URLs and any custom fields captured on the application form. Then work out which offer the candidate applied to and call Get Public Company Offer for that role, so you have the actual job description and requirements to score against rather than a generic idea of the job. Read the CV from the URL on the profile.
Write a structured screening note onto the candidate with Create Note. The note should cover exactly three concrete strengths, each tied to something specific in this person's background rather than generic praise; three gaps measured against the requirements listed on the offer, naming the requirement each gap relates to; and two suggested interview questions tailored to this specific person and this specific role. Keep it short enough that a recruiter can read the whole thing in under a minute.
Then apply a triage tag with Update Candidate, using a fixed vocabulary of exactly strong-match, worth-a-look, or needs-review. Never invent a new tag value outside those three. Preserve any tags already on the candidate rather than replacing them.
Finally, post a short summary to the hiring channel using the Slack Bot Send a Message operation, with the candidate name, the role they applied for, and the triage tag you assigned. One or two lines is plenty, since the full brief lives on the candidate record in Recruitee.
This workflow is advisory only. Never auto-reject a candidate, never disqualify anyone, never move a candidate out of the pipeline, and never change their stage. The note and the tag are inputs to a human decision and nothing more. If the CV is missing, unreadable, or the link fails to load, say so plainly in the note and tag the candidate needs-review instead of guessing at their background from a name and email address alone. Do the same if the offer has no meaningful requirements to score against: state that the comparison could not be made rather than inventing criteria.
What does this prompt do?
- Runs the moment someone applies to one of your jobs, so there is no batch job to wait for and no manual review queue to work through.
- Reads the candidate's full profile and CV, then compares it against the real description and requirements of the role they actually applied for.
- Writes a short brief onto the candidate record covering three concrete strengths, three gaps against the requirements, and two interview questions written for that specific person.
- Tags each applicant as strong match, worth a look, or needs review, and posts the name, role, and tag to your hiring channel.
What do I need to use this?
- A Recruitee account with permission to view candidates and to add notes and tags
- A Slack workspace and a channel where your hiring team follows new applicants
- At least one published job with its description and requirements filled in, since that is what candidates get compared against
How can I customize it?
- Rename the three triage tags to match the vocabulary your hiring team already uses
- Send the summary to a different Slack channel, or route different departments to different channels
- Change what the brief covers, for example adding notice period or salary expectations when you collect them on the application form
FAQs
Will this automatically reject candidates?
What happens if someone applies without a CV?
Where does the screening brief actually show up?
What if our job descriptions are thin or out of date?
Does it screen candidates for every open role?
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 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.
When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.
Stop reading cold applications.
Give every recruiter a written brief and a triage tag waiting on the candidate record before they open it.