n8n WhatsApp Absence Reasons to Google Sheets (Gemini + Redis)

Automatically message parents on WhatsApp for student absences—then write the reason back to Google Sheets using Gemini + Redis deduplication

This n8n workflow checks your Google Sheets attendance tracker daily, sends WhatsApp messages to parents of absent students, and—after interpreting parent replies—updates the absence reasons directly in Google Sheets. It uses Google Gemini for response understanding and Redis for buffering, deduplication, and chat memory to keep conversations clean and reliable.

What this workflow does

• Runs every day at 10:30 AM and reads the attendance sheet in Google Sheets.
• Filters students marked absent who do not yet have a recorded reason.
• Sends a WhatsApp message to the student’s parent and stores outbound chat context in Redis chat history.
• Triggers on incoming WhatsApp messages, extracts details, and replies with a warning if the message is not text.
• Uses Redis to:
  • Ignore duplicate WhatsApp webhooks
  • Buffer multiple parent messages for up to 5 minutes
  • Debounce rapid replies so only the latest batch is used
• Acquires a short Redis lock per phone number, combines buffered messages, clears the buffer, and then looks up the student record in Google Sheets by parent phone number.
• Sends the conversation to Google Gemini (with Redis-based chat memory) to classify whether a valid absence reason was provided.
• If valid, updates the student row in Google Sheets and sends a confirmation WhatsApp reply; otherwise, asks a clarification question.

Use cases

• School attendance automation: collect absence reasons from parents via WhatsApp and keep a clean Google Sheets record.
• SaaS ops or automation engineers: reliable WhatsApp webhook handling with Redis deduplication and message buffering.

Technical details

• n8n workflow with nodes including: if, set, no op, wait, Redis, WhatsApp
• Google Sheets read/update for attendance and absence reasons
• Google Gemini to interpret parent replies
• Redis for deduplication, buffering (up to 5 minutes), debouncing, and chat memory