Google Sheets to Gmail, polished interview briefs fast
Interview prep breaks down in the same boring place every time: someone is skimming PDFs, copy-pasting highlights, then trying to write “good questions” five minutes before the panel joins.
If you run recruiting as a Talent Acquisition lead, you feel the pain first. Recruiters get buried in it. And hiring managers end up with uneven prep. This Google Sheets Gmail automation turns a single row and a resume link into a consistent interviewer brief that actually helps.
You’ll see how the workflow pulls candidate data from Sheets, downloads the resume from Drive, uses GPT to generate a clean HTML brief, then sends it through Gmail to your interview team.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Google Sheets to Gmail, polished interview briefs fast
flowchart LR
subgraph sg0["When clicking ‘Execute workflow’ Flow"]
direction LR
n0@{ icon: "mdi:message-outline", form: "rounded", label: "Send Follow-up Email1", pos: "b", h: 48 }
n1@{ icon: "mdi:database", form: "rounded", label: "Get row(s) in sheet", pos: "b", h: 48 }
n2@{ icon: "mdi:robot", form: "rounded", label: "Basic LLM Chain", pos: "b", h: 48 }
n3@{ icon: "mdi:brain", form: "rounded", label: "Azure OpenAI Chat Model1", pos: "b", h: 48 }
n4@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Execute workf..", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "Download file", pos: "b", h: 48 }
n6@{ icon: "mdi:cog", form: "rounded", label: "Extract from File", pos: "b", h: 48 }
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Code"]
n7 --> n2
n5 --> n6
n2 --> n0
n6 --> n7
n1 --> n5
n3 -.-> n2
n4 --> n1
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n4 trigger
class n2 ai
class n3 aiModel
class n1 database
class n7 code
classDef customIcon fill:none,stroke:none
class n7 customIcon
Why This Matters: Interview Prep Shouldn’t Be a Fire Drill
Most interview panels don’t fail because the candidate was wrong. They fail because the team shows up unaligned. One person read the resume, another only skimmed LinkedIn, and someone else is guessing what “good questions” look like for that role. Then you get overlapping questions, missed risk areas, and a debrief full of vibes instead of signal. Frankly, it’s not anyone’s fault. Manual prep is slow, and it’s easy to let it slide when you’re juggling scheduling, feedback chasing, and a dozen open reqs.
It adds up fast. Here’s where it typically breaks down in real hiring teams:
- Resume review becomes a 30-minute scramble right before the interview, so the panel starts cold.
- Every recruiter formats “the brief” differently, which means interviewers stop trusting it.
- Important context gets lost between tools because candidate details live in Sheets while the resume lives in Drive.
- Weak prep leads to weak questions, and weak questions lead to weak decisions that you’ll pay for later.
What You’ll Build: AI-Generated Interviewer Briefs Sent from Gmail
This workflow creates a repeatable “brief pack” for every candidate, on demand. You start with a candidate row in Google Sheets that includes basic details and a Google Drive resume link. When you trigger the workflow, it downloads the PDF resume from Drive, extracts the text, and combines it with the metadata from your sheet (name, role, email, whatever you store). Then GPT-4o-mini generates a structured HTML interviewer brief: a candidate summary, job fit notes, risk areas to probe, and 5–7 targeted interview questions. Finally, the workflow sends that brief to your interview team via Gmail, so everyone walks into the conversation with the same context.
The workflow starts with Google Sheets and Google Drive to gather the facts. AI turns the resume into an actual preparation document. Gmail delivers it instantly, ready to forward or print.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you have 10 interviews a week across a few roles. A typical manual brief takes about 30 minutes (download resume, skim, write notes, draft questions, format, send), which is roughly 5 hours weekly. With this workflow, you trigger the run in a minute, then wait for processing (often around 2–5 minutes depending on resume length and AI response time). You still sanity-check the output, but it’s a quick read, not a blank-page exercise.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets for candidate rows and resume links
- Google Drive to store and download resume PDFs
- Gmail to email briefs to the interview panel
- Azure OpenAI API key (get it from Azure OpenAI Studio)
Skill level: Beginner. You’ll connect Google accounts, paste an API key, and tweak a prompt or two.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A manual run kicks things off. You trigger the workflow when a candidate is ready for panel prep, so you’re not blasting emails every time a sheet changes.
Candidate details come from Google Sheets. n8n reads the row you specify (name, role, interviewer distribution list, and the Google Drive resume link). This becomes the “source of truth,” which keeps your process consistent.
The resume gets downloaded and converted into usable text. The workflow pulls the PDF from Google Drive, then runs PDF text extraction so the AI model can analyze the contents without you copying anything by hand.
AI generates the interviewer brief and Gmail sends it. The workflow merges resume text with your sheet metadata, asks GPT-4o-mini to produce a professional HTML brief (including questions and risk areas), and emails it via Gmail. Optional nodes like Slack can alert the team that the brief is ready.
You can easily modify the HTML template and the prompt to match your role types, scorecards, or brand voice. See the full implementation guide below for customization options.
Troubleshooting Tips
- Google Drive credentials can expire or need specific permissions. If things break, check the Google connection in n8n’s Credentials panel first, then confirm the resume file is shared to the authenticated account.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Quick Answers
About 30 minutes if your Google and Azure accounts are ready.
No. You’ll connect accounts and adjust a few fields and prompts.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Azure OpenAI usage costs, which depend on how long the resumes are and how much HTML you generate.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. Swap the AI prompt in the AI Agent / OpenAI Chat Model step to match your scorecard (for example: leadership principles, customer focus, technical depth). You can also change the Gmail “To” field to send different briefs to different panels, and update the Google Sheets columns you pull from so each role type gets the right context.
Usually it’s expired Google OAuth credentials or the wrong Google account connected in n8n. Reconnect Google Sheets in n8n Credentials, then confirm the spreadsheet is shared with that account and the workflow is pointing at the correct sheet/tab. If it only fails sometimes, watch for Google API quota limits when you run lots of briefs back-to-back.
If you self-host, there’s no execution limit (it mostly depends on your server and API rate limits). On n8n Cloud, your monthly execution cap depends on your plan, and this workflow uses one execution per candidate brief. Practically, it’s common to run dozens a day without issues, but very large batches may need throttling so Google and Azure OpenAI don’t rate-limit you.
Often, yes, because this workflow benefits from richer branching, merging, and AI prompt control. n8n also gives you a self-hosting option, which matters when your hiring volume spikes and you don’t want to pay per tiny step. Zapier and Make are fine for simple “when row added, send email” flows, but resume download + PDF text extraction + HTML generation tends to get awkward fast. Another practical point: n8n handles more complex error paths (like an Error Trigger) so failures don’t disappear silently. Talk to an automation expert if you want help choosing.
Once this is in place, interviewer prep stops being a recurring emergency. The workflow handles the repetitive parts so your team can focus on the actual conversation.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
