Score new Google Form job applicants and file them in Ashby

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.