Google Calendar + Gmail reminders, Sheets stays updated
Interview scheduling is easy. Keeping everyone aligned after it’s scheduled is the part that quietly breaks. Candidates miss links, interviewers forget, and suddenly you’re chasing updates across threads and DMs.
This Calendar email automation hits Recruiters first, but hiring managers and ops leads feel it too. You get fewer no-shows, cleaner tracking, and a pipeline you can actually trust without babysitting every step.
This workflow watches your interview calendar, sends the right reminders, then logs outcomes in Google Sheets the moment results come in. You’ll see what it does, what you need, and how to run it reliably.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Google Calendar + Gmail reminders, Sheets stays updated
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n5@{ icon: "mdi:database", form: "rounded", label: "Update Sheet with Result", pos: "b", h: 48 }
n6["<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/webhook.dark.svg' width='40' height='40' /></div><br/>Webhook: Submit Interview Re.."]
n7@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check if Passed", pos: "b", h: 48 }
n8@{ icon: "mdi:message-outline", form: "rounded", label: "Email Candidate - Passed", pos: "b", h: 48 }
n9@{ icon: "mdi:message-outline", form: "rounded", label: "Email Candidate - Failed", pos: "b", h: 48 }
n10@{ icon: "mdi:message-outline", form: "rounded", label: "Email Manager", pos: "b", h: 48 }
n7 --> n8
n7 --> n9
n9 --> n10
n8 --> n10
n5 --> n7
n6 --> n5
end
subgraph sg1["Check Every 5 Minutes Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Check Every 5 Minutes", pos: "b", h: 48 }
n1@{ icon: "mdi:location-exit", form: "rounded", label: "Get Calendar Events", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Filter Upcoming Interviews", pos: "b", h: 48 }
n3@{ icon: "mdi:database", form: "rounded", label: "Add to Google Sheet", pos: "b", h: 48 }
n4@{ icon: "mdi:message-outline", form: "rounded", label: "Send Reminder to Candidate", pos: "b", h: 48 }
n1 --> n2
n0 --> n1
n2 --> n3
n2 --> n4
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 n0 trigger
class n7,n2 decision
class n5,n3 database
class n6 api
classDef customIcon fill:none,stroke:none
class n6 customIcon
Why This Matters: Interviews Fall Apart After Scheduling
Most interview processes don’t fail because you didn’t schedule the call. They fail in the messy middle: reminders go out late (or not at all), links aren’t where people expect them, and feedback sits in someone’s head until you ping them twice. Then you open your “pipeline tracker” and realize it’s basically a guessing game. That lag costs real time because you’re making decisions off stale info, and it also chips away at candidate experience. Honestly, even a small amount of chaos becomes a pattern once you’re running multiple interviews a week.
It adds up fast. Here’s where it breaks down.
- Interview reminders depend on someone remembering to send them, which is unreliable during busy hiring weeks.
- Status updates in the tracker happen hours (or days) after the interview, so the team can’t act quickly.
- No-shows create a double cost: wasted interviewer time and a longer time-to-fill when you need to reschedule.
- Pass/fail outcomes get scattered across email threads, making audits and handoffs painful.
What You’ll Build: Automated Interview Reminders + Outcome Logging
This workflow runs quietly in the background and keeps interviews moving without you nudging people. Every 5 minutes, it checks Google Calendar for upcoming events that match your interview criteria (title keywords, descriptions, or other event details). When it finds a near-term interview, it sends a Gmail reminder to the candidate and the internal interviewer(s) so everyone shows up prepared with the right link. After the interview, a simple webhook endpoint receives the outcome (pass/fail plus optional feedback), and the workflow writes that result into Google Sheets. From there it branches: candidates automatically get the right follow-up email, and your hiring manager gets notified so decisions don’t stall.
The workflow starts on a schedule, then uses Google Calendar to detect relevant interviews. It sends reminders via Gmail, and later accepts a result submission via webhook, which updates Google Sheets and triggers the correct pass/fail notifications.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you run 15 interviews in a week. Manually, you might spend 5 minutes confirming details, 5 minutes sending reminders, and another 5 minutes updating the tracker per interview, which is about 4 hours total. With this setup, reminders and logging happen automatically; you only spend a minute submitting the result through the webhook form. That’s roughly 3 hours back in a normal week, plus fewer “did they join?” moments during the day.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Calendar to pull upcoming interview events.
- Gmail to send reminders and outcomes.
- Google Sheets ID (copy it from the Sheet URL).
Skill level: Beginner. You’ll connect Google accounts, paste a Sheet ID, and adjust a couple filters and email templates.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A scheduled check looks for interviews. Every 5 minutes, n8n scans your Google Calendar and pulls events from the hiring calendar you choose.
Only the right events make it through. A filter narrows the list to near-term interviews (for example, events with “Interview” in the title and a start time within your reminder window), so you don’t email people about unrelated meetings.
Reminders and tracking happen automatically. For each matched event, the workflow sends Gmail reminders to the candidate and internal interviewers, and it can also append a row in Google Sheets so the interview is logged before it even happens.
Results come back through a webhook and trigger follow-ups. After the call, a result submission (pass/fail plus feedback) hits your webhook URL, updates the existing row in Google Sheets, and sends the correct candidate email. Then the hiring manager gets a notification so the next step happens quickly.
You can easily modify the event keywords and reminder timing to match your process. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Trigger
This workflow polls Google Calendar on a schedule to find interviews starting soon.
- Add and open Scheduled Poll Trigger.
- Set the interval rule to run every minutes (the workflow uses a minutes-based interval).
- Confirm Scheduled Poll Trigger connects to Fetch Calendar Sessions.
Step 2: Connect Google Calendar and Fetch Sessions
Pull upcoming interview events from a specific calendar.
- Open Fetch Calendar Sessions.
- Credential Required: Connect your googleCalendarOAuth2Api credentials.
- Set Operation to
getAll. - Set Calendar to your calendar ID, replacing
[YOUR_ID]. - Set Time Min to
{{ $now.toISO() }}and Time Max to{{ $now.plus({ hours: 1 }).toISO() }}.
Step 3: Set Up the Near-Term Filter and Parallel Branches
Filter events so only interviews starting within 5 minutes move forward, then branch into logging and reminder actions.
- Open Filter Near-Term Interviews.
- Set the first condition to before with Left Value
{{ $json.start.dateTime }}and Right Value{{ $now.plus({ minutes: 5 }).toISO() }}. - Set the second condition to after with Left Value
{{ $json.start.dateTime }}and Right Value{{ $now.toISO() }}. - Ensure Filter Near-Term Interviews outputs to both Append Interview Row and Send Candidate Reminder in parallel.
Step 4: Connect Google Sheets for Interview Logging
Store interview sessions and outcomes in Google Sheets.
- Open Append Interview Row.
- Credential Required: Connect your googleApi credentials.
- Set Authentication to
serviceAccount. - Set Document ID to
YOUR_SPREADSHEET_IDand Sheet Name toSheet1. - Open Record Interview Outcome and repeat the same Document ID and Sheet Name settings.
- Credential Required: Connect your googleApi credentials in Record Interview Outcome.
Step 5: Configure the Candidate Reminder Email
Send a reminder 5 minutes before the interview starts.
- Open Send Candidate Reminder.
- Credential Required: Connect your gmailOAuth2 credentials.
- Set Send To to
{{ $json.attendees[0].email }}. - Set Subject to
Interview Reminder - Starting in 5 Minutes. - Set Message to the provided HTML template with expressions like
{{ $json.summary }},{{ $json.start.dateTime }}, and{{ $json.hangoutLink }}.
Step 6: Configure the Result Webhook and Outcome Routing
Receive interview outcomes via webhook, store them, and notify candidates and the hiring manager.
- Open Incoming Result Webhook and set HTTP Method to
POSTwith Pathinterview-result. - Confirm Incoming Result Webhook connects to Record Interview Outcome.
- Open Evaluate Pass Status and set the condition: Left Value
{{ $json.result }}equals Right ValuePass. - Open Notify Candidate Success and set Send To to
{{ $json.candidateEmail }}and keep the message template with{{ $json.feedback }}. - Open Notify Candidate Rejection and set Send To to
{{ $json.candidateEmail }}and keep the message template with{{ $json.feedback }}. - Open Alert Hiring Manager and replace
[YOUR_EMAIL]in Send To with the manager’s email. - Credential Required: Connect your gmailOAuth2 credentials for Notify Candidate Success, Notify Candidate Rejection, and Alert Hiring Manager.
candidateEmail, result, and feedback or the emails will be missing key data.Step 7: Test and Activate Your Workflow
Verify both the scheduling and results flows before turning the workflow on.
- Manually run Scheduled Poll Trigger to confirm Fetch Calendar Sessions returns upcoming events.
- Check that Filter Near-Term Interviews outputs to both Append Interview Row and Send Candidate Reminder in parallel when an event is within 5 minutes.
- Send a test POST to Incoming Result Webhook with JSON that includes
candidateEmail,result, andfeedback. - Verify that Record Interview Outcome logs to Google Sheets and Evaluate Pass Status routes correctly to Notify Candidate Success or Notify Candidate Rejection, followed by Alert Hiring Manager.
- When tests succeed, toggle the workflow to Active for production use.
Troubleshooting Tips
- Google Calendar credentials can expire or need specific permissions. If things break, check the Google connection inside n8n’s Credentials screen first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Gmail sending can fail if the OAuth scope is too limited or the “from” address doesn’t match the connected account. Check the Gmail node’s error output and confirm you can send a test email from inside n8n.
Quick Answers
About 30 minutes if your Google accounts are ready.
No. You’ll mostly connect Google accounts and adjust a filter plus a few email templates.
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 Google Workspace costs if your org requires paid Gmail/Calendar accounts.
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. Most teams tweak the “Filter Near-Term Interviews” logic (keywords, time window, or which calendar is checked) and rewrite the Gmail templates to match their tone. You can also change the Google Sheets columns to match your pipeline stages, as long as you keep the fields the update step expects. If your results come from a form tool, keep the webhook but map the submitted fields to your sheet’s “Result,” “Feedback,” and “Updated At” columns.
Usually it’s an expired Google OAuth token or the connected account doesn’t have edit access to the sheet. Reconnect the Google Sheets credential in n8n, then confirm the Sheet ID points to the right file and tab. If it fails only sometimes, check for renamed columns or moved headers because the update step relies on consistent field names.
Plenty for most small teams: scanning a calendar every 5 minutes and handling a few dozen interviews a day is normal on even modest setups.
Often, yes, because this flow has a few moving parts: scheduled polling, filtering, a webhook intake, and branching pass/fail logic. n8n handles that kind of “one workflow, many paths” setup cleanly, and self-hosting avoids per-task pricing when volume grows. Zapier and Make can still do it, but the bill can climb once you’re checking calendars frequently and writing multiple updates. If you only want a simple reminder email and nothing else, those tools can be quicker to set up. Talk to an automation expert if you want help choosing.
Once this is live, interviews stop being a coordination problem and start being a predictable pipeline. The workflow handles the repetitive follow-ups so your team can focus on making the right hire.
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.
