Score Google Form applicants in Ashby with a Slack hiring recap

Build 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.

Additional information

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.

Frequently asked questions

What happens if a candidate did not attach a resume?

The agent still creates the candidate in Ashby with whatever the form captured, and clearly flags missing resume in the Slack recap so a recruiter can chase it.

Will it create duplicate candidates if someone applies twice?

No. The agent looks up the email in Ashby first. If the candidate already exists it updates their profile instead of creating a duplicate.

Can the fit score and rationale live inside Ashby?

Yes. The score, rationale, red flags, and recommended next step are attached as a candidate note on the Ashby profile, so the hiring committee can review without leaving the ATS.

How does the workflow know which Ashby job to file applications under?

You pick the target job when you set the workflow up. The agent matches that against your live Ashby jobs and uses it for every application it creates.

Does this replace a human recruiter screen?

No. It writes a first-pass recommendation so your recruiters can prioritize who to look at next, not auto-reject anyone. You still decide who actually advances.