Google Sheets + Slack: interview feedback reminders
Interview feedback always starts with good intentions. Then the day gets busy, someone forgets, and you’re stuck chasing scorecards across Slack threads, emails, and half-updated spreadsheets.
Sheets Slack reminders hit hardest when you’re the recruiting coordinator trying to close loops fast. But HR leads and hiring managers feel it too because one missing form can stall a decision for days.
This workflow checks your Google Sheet daily, nudges panelists in Slack (or email if Slack ID is missing), and marks the reminder as sent so you don’t double-ping people. You’ll see exactly where the bottleneck is, and you’ll stop babysitting it.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Google Sheets + Slack: interview feedback reminders
flowchart LR
subgraph sg0["Daily Reminder Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Daily Reminder Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:database", form: "rounded", label: "Fetch Interview Feedback Data", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check If Feedback Is Submitted", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check for Slack ID", pos: "b", h: 48 }
n4["<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/slack.svg' width='40' height='40' /></div><br/>Send Slack Reminder"]
n5@{ icon: "mdi:message-outline", form: "rounded", label: "Send Email Reminder", pos: "b", h: 48 }
n6@{ icon: "mdi:database", form: "rounded", label: "Update Reminder Status", pos: "b", h: 48 }
n3 --> n5
n3 --> n4
n5 --> n6
n4 --> n6
n0 --> n1
n1 --> n2
n2 --> n3
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 n2,n3 decision
class n1,n6 database
classDef customIcon fill:none,stroke:none
class n4 customIcon
The Challenge: Getting feedback without chasing people
Collecting interview feedback sounds simple until you’re running multiple roles at once. You finish an interview loop, open the tracker, and realize three panelists still haven’t submitted anything. So you message them. Then you message again. Someone replies “done” but forgets to tick the box in the sheet. Another person never saw the Slack ping because their notifications are a war zone. Meanwhile the candidate is waiting, your hiring manager is asking for an update, and “we’ll decide tomorrow” turns into next week. Honestly, it’s not the reminder that’s hard. It’s tracking it without losing your mind.
The friction compounds quickly. Here’s where it breaks down.
- Panelists miss the “please submit feedback” message because it’s buried in channel noise or sent at the wrong time.
- You end up sending duplicate nudges since there’s no reliable “reminder already sent” flag you trust.
- When Slack IDs aren’t tracked, the fallback becomes manual email, which means more copy-paste and more chances to miss someone.
- Decisions stall because one or two late scorecards hold the entire loop hostage.
The Fix: Daily Google Sheets checks with Slack (and email) nudges
This n8n workflow turns your interview feedback tracker into a lightweight follow-up system that runs on autopilot. Every day at 6:00 PM, it reads your Google Sheet and looks for interview entries where feedback hasn’t been marked as submitted. For each pending item, it checks whether a valid Slack ID exists for the interviewer. If it does, the workflow sends a direct message in Slack with a clear reminder. If it doesn’t, it sends a fallback reminder via Gmail to the interviewer’s email address. After sending the nudge, it updates the same row in Google Sheets to mark the reminder as sent, so the next run doesn’t spam people or restart the cycle.
The workflow starts on a schedule, then pulls rows from Google Sheets and filters to “still waiting.” Slack handles the fast path, Gmail covers the edge cases, and the sheet update keeps everything consistent so you always know what happened.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say you’re coordinating 10 interviews a day and, on average, 3 panelists per day need a reminder. Manually, you might spend about 5 minutes per person checking the sheet, finding the right Slack profile or email, sending the message, and noting it somewhere, which is roughly 45 minutes. With this workflow, the “work” is basically zero: the trigger runs at 6:00 PM, messages go out automatically, and the reminder flag updates without you touching anything. That’s close to an hour you get back on days when things are hectic.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets to store interview rows and status flags.
- Slack to send direct-message reminders to panelists.
- Gmail to send fallback reminders when Slack IDs are missing.
Skill level: Beginner. You’ll connect accounts and map a few sheet columns, but you won’t be writing code.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
A daily schedule kicks it off. The workflow runs automatically every day at 6:00 PM (you can change the time later). No one has to remember to “do reminders.”
Your Google Sheet becomes the source of truth. It reads rows from your interview tracker and focuses only on entries where feedback_submitted is not marked “Yes.” That filter matters because it stops noise and keeps reminders targeted.
Slack first, email if needed. If the row has a valid slack_id, the workflow sends a Slack DM. If the Slack ID is missing (or blank), it falls back to Gmail and sends a reminder to interviewer_email.
The sheet updates so you don’t double-nudge. After sending the message, it writes back to Google Sheets (for example, setting reminder_sent to “Yes”). That small update is what makes the automation reliable over time.
You can easily modify the schedule time to run hourly, or change the message template to match your tone and scorecard link. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
Set the workflow to run daily based on the schedule defined in the trigger.
- Add or open Scheduled Nudge Trigger.
- In Rule, set Interval to trigger at hour
18. - Confirm the node is connected to Retrieve Feedback Records.
Step 2: Connect Google Sheets
Pull interview records and later update the reminder flag in your spreadsheet.
- Open Retrieve Feedback Records and select the spreadsheet in Document with ID
[YOUR_ID]. - Set Sheet Name to
Interview_Feedback. - Credential Required: Connect your googleSheetsOAuth2Api credentials in Retrieve Feedback Records.
- Open Refresh Reminder Flag and confirm Operation is
appendOrUpdate. - Credential Required: Connect your googleSheetsOAuth2Api credentials in Refresh Reminder Flag.
Step 3: Set Up Feedback Status Logic
Filter records to only those missing feedback and route based on Slack availability.
- Open Verify Feedback Status and set the condition to equals with Left Value
={{ $json["Feedback Submitted (Y/N)"] }}and Right ValueY. - Confirm that the false branch continues to Validate Slack Identifier for missing feedback.
- In Validate Slack Identifier, keep the condition to check
={{ $json["Candidate Slack Id"] }}with the empty operator.
Validate Slack Identifier outputs to both Send Email Prompt and Dispatch Slack Prompt in parallel.
Step 4: Configure Email and Slack Prompts
Send reminder messages through Gmail and Slack using the record data.
- Open Send Email Prompt and set To to
={{ $json["Candidate Email"] }}. - Set Subject to
={{ $json.Recommendation }}and Message to={{ $json["Areas of Improvement"] }}. - Credential Required: Connect your gmailOAuth2 credentials in Send Email Prompt.
- Open Dispatch Slack Prompt and set Text to
={{ $json["Areas of Improvement"] }}. - Set User to
={{ $json["Candidate Slack Id"] }}with Select asuser. - Credential Required: Connect your slackApi credentials in Dispatch Slack Prompt.
⚠️ Common Pitfall: If the Slack user ID is missing or invalid, Dispatch Slack Prompt will fail for that item. Ensure the Candidate Slack Id column is populated.
Step 5: Update the Reminder Flag in Sheets
After sending reminders, update the row to mark the reminder as sent and keep records synchronized.
- Open Refresh Reminder Flag and confirm the mapping fields are pulling from Validate Slack Identifier, such as
={{ $('Validate Slack Identifier').item.json["Interview ID"] }}and={{ $('Validate Slack Identifier').item.json["Candidate Name"] }}. - Set Feedback Submitted (Y/N) to
=Yto mark the reminder outcome. - Verify Matching Columns includes
Feedback Submitted (Y/N)to update the correct row.
Step 6: Test and Activate Your Workflow
Validate the end-to-end flow before turning it on in production.
- Click Execute Workflow and confirm Retrieve Feedback Records pulls rows from
Interview_Feedback. - Check that records with
Feedback Submitted (Y/N)not equal toYproceed through Validate Slack Identifier. - Verify that emails are sent via Send Email Prompt and Slack messages post via Dispatch Slack Prompt.
- Confirm Refresh Reminder Flag updates the sheet and sets
Feedback Submitted (Y/N)toY. - Toggle the workflow to Active to start scheduled runs at hour
18.
Watch Out For
- Google Sheets permissions can be deceptively strict. If the workflow reads fine but fails on the update, check the connected Google account has edit access to the exact spreadsheet and tab.
- If you’re relying on the 6:00 PM schedule, time zones can bite you. Confirm the n8n instance timezone and the Schedule Trigger settings so you don’t nudge panelists at midnight.
- Slack DMs can fail when the Slack ID is wrong or the bot lacks permission to message users. Check your Slack app scopes (DM permissions) and verify the slack_id column is consistently populated.
Common Questions
About 30 minutes if your Sheet and accounts are ready.
Yes. You’ll mostly be connecting Google Sheets, Slack, and Gmail, then matching the right columns to the right fields.
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 Slack and Google Workspace access (usually already covered in your org).
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.
You can. Most teams start by changing the schedule time in the Scheduled Nudge Trigger, then customizing the Slack DM and Gmail copy to include a scorecard link. If your tracker uses different column names, update the Google Sheets nodes (Retrieve Feedback Records and Refresh Reminder Flag) to map your fields correctly. You can also tweak the IF checks so “Submitted” values like “Done” or a timestamp count as complete.
Usually it’s an invalid Slack ID or missing permission for the bot to send DMs. Double-check the slack_id values in Google Sheets and confirm your Slack app scopes allow direct messages. If it worked before and suddenly stopped, re-authenticate the Slack credentials in n8n.
Plenty for small and mid-sized hiring teams. On n8n Cloud, capacity depends on your plan’s monthly executions; on self-hosted n8n there’s no fixed execution cap, it depends on your server. In practice, a daily run that checks a sheet and sends a handful of DMs/emails is very lightweight.
Often, yes, because this flow needs branching logic (Slack if there’s a Slack ID, Gmail if there isn’t) and a reliable write-back to Google Sheets so you don’t double-remind. n8n handles that kind of conditional logic cleanly, and self-hosting can be a big deal if you want lots of automations without worrying about task limits. Zapier or Make can still work if you prefer a very guided UI and you’re okay paying for higher-volume runs. The bigger question is maintenance: who will own it when the sheet changes or Slack scopes update? Talk to an automation expert if you want a quick recommendation based on your setup.
Once this is running, interview feedback stops being a daily follow-up project. The workflow keeps things moving, and you get to focus on making the decision, not hunting down the last scorecard.
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.
