Post a job, share one application form, and let AI screen every résumé against the job description. Qualified candidates get an interview invite with your Calendly link; everyone else gets a polite decline, and your hiring channel sees a summary in Slack.
Free · no credit card · connects your Gmail + Slack
Installing the recipe provisions all of this in your workspace, ready to run.
The pipeline tracker. Every applicant lands here with their AI score, screening summary, and live status: applied, screened, interview_invited, or rejected.
HR-facing: title, department, hiring-manager email and Calendly link, and the full JD. Publishing it creates the response sheet that IS your job openings store, which the candidate form reads from.
Candidate-facing: name, email, role, location, years of experience, skills, resume upload, optional cover letter. Submission fires the screening workflow.
Looks up the matching JD, writes the application to the Candidates table, scores the resume with TinyGPT, branches on qualified or not, sends the invite or the decline, and posts the summary to your hiring channel.
Send interview invites (BCC: hiring manager) and rejection emails to candidates
Notify the hiring channel with the AI screening summary for every applicant
HR opens the Post Job Opening form and submits the role: job title, department, hiring-manager email, hiring-manager Calendly link, and the full job description. It lands in the Openings sheet automatically, and that sheet is what the candidate form's role dropdown reads from. No copy-paste, no drift between what was posted and what gets screened against.
Put the published Job Application form on your careers page or straight into outbound posts. Candidates submit their name and email, the role they're applying for, their location, years of experience, skills, a resume upload, and an optional cover note. One public link is the whole top of your funnel.
Every application triggers the Screen & Notify workflow automatically. The form is the trigger: there's nothing to re-run, nothing to remember, and no batch to process on Friday afternoon.
The workflow looks up the job description in the Openings sheet using the role the candidate selected, and pulls the hiring-manager email so the right person is notified later. If no matching opening exists, the workflow exits cleanly. Nothing is created and nobody is emailed. A closed role can't accidentally screen candidates.
TinyGPT runs against the resume, skills, years of experience, and the job description together, and returns three things: a score out of ten, a one-paragraph read of the candidate, and a qualified true or false. The full application plus the AI verdict is written into the Candidates table with status screened.
Qualified candidates get an interview invite by Gmail, BCC'd to the hiring manager, containing the hiring manager's Calendly link. The candidate picks a slot that works for them. No scheduling thread, no calendar event for anyone to manage, no three-day gap while two inboxes negotiate. The row moves to interview_invited.
Candidates who aren't a fit get a plain, respectful rejection, sent same-day, not never. The row moves to rejected and no interview is created. This is the step most hiring processes quietly skip, and the one candidates remember.
Qualified or rejected, the workflow posts a one-line summary to your hiring channel: candidate name, role applied for, AI score, and decision. Your hiring team watches the funnel move without opening a single sheet. Swap Slack for Discord or Telegram at install, the message format is identical.
Install the recipe, connect Gmail and Slack, and post your first role in two minutes.
