Score new Google Form job applicants and file them in Ashby
When someone submits your job application form, an agent reads their resume, scores them against the role, files them in Ashby, and posts a Slack recap.
Google Forms
Google Drive
Ashby
Slack BotHR & PeopleOperationsLead EnrichmentDocument ProcessingNotifications & AlertsBuild an agent workflow that triages new job applications from a Google Form into Ashby, with a Slack recap to the hiring team.
Trigger: poll a specific Google Form (google-forms) for new responses. I will pick the form at setup time.
Workflow inputs I will provide when I run it:
- The Google Form ID hosting the job application.
- The target Ashby job (title or job ID) the agent should file applications against.
- Role requirements to score against: required years of experience, required tech stack or skills, required location or work authorization.
- The Slack channel where the hiring recap should be posted (default to #hiring).
For each new response, the agent should do the following:
1. Pull the submission from Google Forms using List Responses and Get Response. Extract the applicant's name, email, and any free-text answers.
2. If the form includes a resume upload, get the Google Drive file ID for it and download the PDF via Google Drive Download File Content. If no resume is attached, continue without it and remember to flag missing resume later.
3. Look the candidate up in Ashby first with Search Candidates by email. If a match exists, use Update Candidate to refresh their profile. If not, use Create Candidate. This is the dedupe path, do not create a duplicate on resubmissions.
4. Score the applicant against the role requirements I provided. Produce four things: an overall fit score from 0 to 100, a one-paragraph rationale, a short list of red flags if any, and a recommended next step picked from advance, hold, or reject.
5. In Ashby, call Create Application against the target job for this candidate. Then call Create Candidate Note and attach the fit summary, score, red flags, and recommendation as the note body so the hiring committee can review inside Ashby.
6. In Slack, use the slackbot integration and Send a Message to the configured channel. The message must include: candidate name, role title, fit score, recommended next step, the one-paragraph rationale, and a deep link to the Ashby candidate profile. If the resume was missing, prepend a clear missing resume flag at the top of the message.
Use the slackbot integration (not the user slack integration) so the recap is posted by a bot, not as a specific recruiter. Integrations to wire: google-forms, google-drive, ashby, slackbot.
Keep the workflow resilient: never fail the whole run because the resume is missing or unreadable. Always create or update the Ashby candidate, always post a Slack recap, and surface any gaps as flags in the recap instead of silent skips.
What does this prompt do?
- Catches every new job application the moment it lands in your Google Form, with no manual copy-paste.
- Reads the candidate's resume, scores them against the role requirements you set (experience, stack, location), and writes a short fit summary with any red flags.
- Creates the candidate and a fresh application in Ashby on the right job, and attaches the fit summary as a candidate note for hiring committee review.
- Posts a recap in your hiring channel on Slack with name, role, score, rationale, recommended next step, and a deep link to the Ashby profile.
What do I need to use this?
- A Google Forms account hosting your job application form, with resume upload turned on.
- A Google Drive login so the workflow can fetch resumes attached to each submission.
- An Ashby admin login with API access (Read All and Write All is the simplest setup).
- A Slack workspace and the channel where hiring updates should land.
How can I customize it?
- Set the role requirements (years of experience, required stack, location or work authorization) when you start the workflow.
- Change which Slack channel receives the recap, or send it as a DM to a specific recruiter instead.
- Tighten or loosen how the agent scores candidates, and what counts as a recommended advance, hold, or reject.
- Point at a different Ashby job if you are hiring for multiple roles, or run two copies of the workflow side by side.
FAQs
What happens if a candidate did not attach a resume?
Will it create duplicate candidates if someone applies twice?
Can the fit score and rationale live inside Ashby?
How does the workflow know which Ashby job to file applications under?
Does this replace a human recruiter screen?
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 resumes one form response at a time.
Connect Google Forms, Ashby, and Slack once, and every new applicant lands prescored in the right job.