Automation Recipe: Auto-Draft Volunteer Screening Packets from New Applications

What This Builds

With volunteer turnover near 19 percent a year, applications arrive constantly, and each one currently means you stop, reread the role they applied for, and draft a screening question set and acknowledgment email by hand. This automation removes that pause. The moment someone submits your volunteer application form, it drafts a role-matched screening packet and a personalized acknowledgment email, logs the applicant to a tracking sheet, and leaves both waiting for your review, so a new application goes from raw form submission to an interview-ready packet without you touching a keyboard first.

Prerequisites

• A Google Form for volunteer applications with a question asking which role they're applying for
• Professional plan ($29.99/month) since this workflow needs more than two steps
• An OpenAI account with API access from platform.openai.com. This is separate from a ChatGPT subscription and is not included in Plus. It's billed per request, typically a few dollars a month at volunteer-application volume
• Gmail or Google Workspace email
• A Google Sheet to track applicants

The Concept

Zapier connects apps and watches for a trigger, then runs a set of actions in order every time that trigger fires. Here, the trigger is a new Google Form submission. The first action sends the applicant's answers to OpenAI's API with instructions to draft screening questions matched to the role and a short acknowledgment email. The next actions send that email and log the applicant to your tracking sheet. You still make every hiring decision. The automation just removes the blank-page moment that happens between "someone applied" and "I have something ready to review."

Build It Step by Step

Part 1: Set Up Your Form and Tracking Sheet

1. In your existing (or a new) Google Form, confirm it captures: applicant name, email, the role they're applying for, availability, and one open-ended question about their interest.
2. Create a Google Sheet called "Volunteer Applicant Tracker" with columns: Name, Email, Role Applied For, Date Applied, Screening Packet Status, Interview Scheduled.
3. Link the Form to a response spreadsheet, or plan to have Zapier write directly to your tracker sheet in Part 2.

Part 2: Create the Zapier Automation

1. Log into Zapier and click Create Zap.

Trigger: Search for Google Forms and choose New Form Response. Connect your account and select your volunteer application form.

1. Add a Filter by Zapier step. Set it to only continue if the "Role Applied For" field is not empty, this keeps incomplete test submissions from triggering the rest of the workflow.

2. Add an OpenAI action. Choose the conversation or chat completion action. Use this prompt, filling the bracketed fields with your Zapier field mappings from the form:

You are helping a nonprofit program manager screen a new volunteer applicant.

Applicant name: [Name field from form]
Role applied for: [Role field from form]
Availability: [Availability field from form]
Why they're interested: [Open-ended answer field from form]

Our role descriptions and typical screening questions:
- [Paste a short summary of your 2-3 most common volunteer roles and what
  each one requires, so the AI can match the right screening questions to
  the right role]

Produce two things, clearly labeled:

1. SCREENING QUESTIONS: three interview questions specific to the role they
   applied for, checking for relevant experience, availability fit, and
   comfort with the role's core task.

2. ACKNOWLEDGMENT EMAIL: a warm, brief email (under 120 words) thanking them
   for applying, confirming the role, and telling them our team will follow
   up within one week to schedule a conversation. Do not promise an
   interview date, only that we'll be in touch.

1. Add a Gmail: Send Email action. Set the To field to the applicant's email from the form, subject to something like "Thanks for your interest in volunteering with [Organization Name]," and the body to the acknowledgment email section of the OpenAI output.

2. Add a Google Sheets: Create Spreadsheet Row action pointing at your Volunteer Applicant Tracker. Map Name, Email, Role Applied For, and today's date. Set Screening Packet Status to "Ready for Review."

3. Add a second Gmail: Send Email action, this one to yourself, with the subject "New volunteer screening packet ready" and the body containing the screening questions section of the OpenAI output plus the applicant's name and role. This is the packet you'll actually use in the interview.

Part 3: Test and Refine

1. Submit a test application through your form using your own information. Confirm: the applicant received a reasonable acknowledgment email, you received a screening-questions email that actually fits the role you tested, and a row appeared in your tracker sheet.

2. If the screening questions come out generic, go back to the OpenAI action and add more specific detail to the role descriptions in the prompt, one sentence about what a strong volunteer in that role looks like usually fixes it.

3. Turn on the Zap. Publish your Google Form if you haven't already.

Sensitive data note: This workflow sends the applicant's name, email, and application answers through Zapier and OpenAI's API. Keep it to that. Do not add fields like date of birth, background-check results, or home address to the automation, route those through your case management system or HR process directly instead, and check with whoever owns your organization's data-handling decisions before expanding what this automation touches. Most nonprofits don't yet have a written AI policy, so this is worth a short conversation rather than an assumption.

Real Example: A Saturday Application

Setup: Your Zap is live, watching your public volunteer application form.

What happens automatically: A prospective tutor applies Saturday afternoon for your after-school reading program. Within a minute, she receives a warm acknowledgment email confirming the role and a one-week follow-up window. You receive a separate email with three screening questions tailored to a reading tutor role (comfort working one-on-one with a child, weekly time commitment, experience with the age group), and her name appears in your tracker with status "Ready for Review."

Monday morning: Instead of starting from a blank page for each of the four applications that came in over the weekend, you open four screening-question emails already matched to the roles applied for, along with a tracker showing exactly who applied for what and when.

Time saved: What used to be 20-30 minutes per applicant, rereading the role, drafting questions, writing an acknowledgment, now happens automatically. Your Monday work is reviewing four ready packets instead of writing four from scratch, roughly two hours saved on a typical weekend's worth of applications.

What to Do When It Breaks

• Applicants stop getting acknowledgment emails and you don't notice → This is the failure you won't see happening in real time. Go to Zapier's dashboard, click your Zap, and turn on Notify me when this Zap has trouble under the Zap's settings. Also check the tracker sheet weekly, if applicants who you know applied aren't appearing, the trigger has likely stopped firing.
• Screening questions don't match the role → The OpenAI action is likely not receiving a clean role name from the form. Check the field mapping, then confirm your form's role dropdown uses consistent role names rather than free text.
• Gmail send fails silently → Check Zapier's Task History (under the main menu) for that run. A failed email step shows up there with an error even if nothing appeared in your inbox.
• Duplicate rows appear in the tracker for one applicant → Usually caused by a Google Form response being edited after submission, which can re-trigger the Zap. Add a Filter step checking that the response is new, not edited, if this becomes frequent.

Variations

• Simpler version: Skip the OpenAI step and use a fixed acknowledgment email template with Zapier's field variables (applicant name, role) inserted directly. You lose the tailored screening questions but keep the automatic logging and acknowledgment.
• Extended version: Add a Slack or email notification to whichever staff member supervises that specific volunteer role, so screening packets route to the right reviewer automatically instead of all funneling to you.

What to Do Next

• This week: Build the Zap for your single highest-volume volunteer role first, test it with a real submission.
• This month: Expand the role-description prompt to cover every role you recruit for, and add the Zap error notification so you'll know immediately if it stops running.
• Advanced: Pair this with your Claude Project (see "Claude Project: Build a Persistent Program Operations Assistant") to draft a full onboarding packet for applicants who move past screening, using the same role context you already built here.

Advanced guide for Nonprofit Program Manager professionals. These techniques use more sophisticated AI features that may require paid subscriptions.