Gmail Triage: Gemini SLA Emails + Google Calendar Tasks (n8n)

Instantly triage “Inquiry Received” emails with Gemini, set SLAs, and create Calendar follow-ups—automatically in n8n

This n8n workflow watches your Gmail inbox for new inquiries, uses Google Gemini to categorize and draft replies, calculates an SLA deadline, and then logs everything to Google Sheets, creates a Google Calendar task, and escalates high-priority cases to Discord.

What this workflow does

• Gmail trigger (every minute): Runs once per minute and looks for unread Gmail messages with the subject “Inquiry Received”.
• AI classification & summarization: Sends the sender, subject, and email body to Google Gemini via an LLM chain to return structured JSON containing category, priority, summary, and an AI-generated reply draft.
• SLA deadline calculation: Computes a follow-up deadline based on priority:
  • High: +4 hours
  • Medium: next day at 18:00
  • Low: +3 days at 18:00
• Google Calendar event: Creates an event from now until the calculated deadline, embedding the ticket details in the event description.
• Google Sheets logging: Appends a row to Google Sheets including received time, triage results, the deadline, and the Google Calendar link.
• Gmail draft reply: Generates a draft reply in the original email thread using the Gemini reply text.
• Discord alert for High priority: If priority is High, posts an urgent notification with the deadline and inquiry summary.

Use cases

• SaaS support teams routing inbound leads or customer questions labeled by subject.
• Automation engineers building a reliable Gmail-to-SLA pipeline with LLM triage.
• Operators who want guaranteed follow-up via Google Calendar and audit logs in Google Sheets.

Technical details

• n8n nodes / tech stack: if, code, gmail, discord, sticky note, gmail trigger
• Integrations: Gmail, Google Gemini (Google AI), Google Calendar, Google Sheets
• Sheets requirements: Ensure the sheet has columns like received_at, priority, category, sender, subject, summary (and related SLA/event fields as used by the append step).