AI Agent for Resume Screening — Built for Google Forms
For teams that take job applications through a Google Form instead of an ATS: an agent that reads each response and its uploaded résumé, checks the must-haves, and sends the hiring manager a ranked shortlist with reasons.
31 applications since Friday. Tonight's shortlist:
How do you screen résumés submitted through Google Forms?
Connect the form and the Google Drive folder where its file-upload question saves résumés.
- 01
Trigger fires
For each new response, the agent reads the answers and opens the uploaded file, then checks the knockout questions you care about, like availability dates, work authorisation or a required certificate, against both.
- 02
Read the form answers and the uploaded résumé
It scores the résumé against the must-haves and nice-to-haves the hiring manager wrote, adds the score and a one-line reason to the responses sheet, and sends a daily shortlist email.
- 03
Check availability and certificates against the knockout rules
It doesn't reject anyone: people who miss a must-have are marked, not emailed, and a person makes every decision.
- 04
Score against the manager's must-haves and nice-to-haves
- 05
You approve
Anything under your confidence bar waits for a human.
How you tell it what to do
Built in plain English.
You write the rule the way you'd describe it to a teammate. The agent reads the rule, breaks it into the actions it'll take, and confirms the apps it'll touch — before it does anything.
- 1Read the form answers and the uploaded résumé
- 2Check availability and certificates against the knockout rules
- 3Score against the manager's must-haves and nice-to-haves
- 4Write score and reason to the sheet, email shortlist
How it connects
Connect Google Forms. The agent does the rest.
Claude and ChatGPT are already running on our side. You connect Google Forms with one click, and resume screening runs inside it.
Claude and ChatGPT run on our keys. Nothing for you to configure.
- Google FormsConnect
- Google DriveConnect
- GmailConnect
Runs on your data, in your apps.
Nothing to deploy. Nothing to maintain.
Actions
What Google Forms + DeskFerry can do
Real Google Forms actions your AI agent can perform automatically — no manual work required.
Collect form submissions
Capture new responses from Google Forms in real-time and push them to your CRM, database, or project management tool.
Route responses by answer
AI reads submission data from Google Forms and routes it to different workflows based on specific answer values.
Send confirmation emails
Trigger personalized confirmation or thank-you emails when someone completes a form in Google Forms.
Aggregate response analytics
Compile response counts, completion rates, and answer distributions from Google Forms into summary dashboards.
Create follow-up tasks
Generate tasks for your team when Google Forms receives responses that require manual review or outreach.
Validate submission data
Check responses from Google Forms for required fields, valid formats, and duplicate entries before processing.
Sync respondents to lists
Add respondents from Google Forms to email lists, CRM contacts, or audience segments based on form type.
Generate response reports
Produce periodic summaries of form data from Google Forms with charts, averages, and trend comparisons.
Résumé is a photo of a printed page, rotated sideways. Answers look strong; needs a person to open the file.
Form says lifeguard certified; résumé lists a certificate that expired in March. Not scored until someone asks him.
Same email applied Friday for Kitchen and today for Counsellor with a different résumé. Scored for Counsellor only.
Human in the loop
Approve before it sends.
Every draft lands in a review queue. You approve, edit, or reject — the agent never acts on its own unless you explicitly turn that on for a workflow you trust.
Governance
Every action, with the reasoning attached.
Each step the agent takes is logged with what it did, why it did it, and which app it touched. Audit-ready, so security and compliance can sign off without backfilling.
- Agent6:00 PM
Sent Hana the evening shortlist: 6 ranked, 9 marked 'dates', 3 waiting on review.
- Agent5:41 PM
Scored Marcus Oyelaran 9/10 and wrote the reason to column K of Form Responses 1.
- Agent5:38 PM
Held Tom Reyes's application unscored.
Reason: He answered yes to 'current lifeguard certificate', but the résumé shows it expired in March, and the rule makes it a must-have.
- Agent5:37 PM
Opened résumé Oyelaran_M.pdf from the form's upload folder and read 2 pages.
- Hana9:12 AM
Added 'wilderness first aid' to the nice-to-haves for counsellors.
How it works
Get started in three steps
Step 01
Connect the form, its Drive folder and Gmail
Link the application form, the Drive folder its file-upload question writes to, and the responses sheet where scores and reasons should go.
Step 02
Paste the job post and knockouts
Write the must-haves, the nice-to-haves, the dates or certificates that rule someone out, and which answers the agent must ignore when scoring.
Step 03
Read the shortlist and the holds
The shortlist lands when you ask for it. Unreadable files, contradictory answers and duplicate applicants wait for you, not the ranking.
Start automating Resume Screening for Google Forms
7-day free trial. Works with the tools you already use.
FAQ
Frequently asked questions
Where does Google Forms put the uploaded résumés?
A form with a file-upload question saves each file to a folder in the form owner's Google Drive, and applicants have to sign in to a Google account to upload. The agent reads files from that folder by the link in each response, so it needs access to the same Drive.
Does the agent reject candidates or email them?
No, unless you add that yourself. By default it scores, explains and ranks; it doesn't send rejections. Applicants who miss a knockout are marked in the sheet with the reason, so the hiring manager sees exactly why they aren't on the shortlist and can override it.
Can I stop it using certain answers when it scores?
Yes. List the questions it may read, such as availability, certificates and experience, and the ones it must leave out of scoring, such as name, age, address or a photo. Each score's reason quotes the résumé line or answer it relied on, so you can check it didn't use anything else.
What if someone pastes a LinkedIn link instead of uploading a file?
The agent scores from the form answers it has and marks the row 'no résumé file'. It doesn't browse LinkedIn profiles. You can add a rule to email those applicants asking for a file, or leave them for the hiring manager to look at by hand.
We're moving to an ATS later. Is this wasted work?
The rule carries over. Must-haves, knockouts and the shortlist format are written in plain English, so when applications move to Greenhouse, Lever or Workable you connect that instead of the form and keep the same screening instructions. Past scores and reasons stay in the responses sheet for reference.
Explore more