Back to Catalog

Dynamically send out-of-office / vacation message using Gmail & Google Calendar

Rosh RagelRosh Ragel
109 views
2/3/2026
Official Page

What it Does

Automatically checks your Google Calendar to determine if you're officially off work for the rest of today. If so, it auto-sends a personalized out‑of‑office reply via Gmail, telling senders when you’ll be back—based on your next calendar entry within the next 2 weeks.

Prerequisites

To use this template, you'll need:

  • Gmail credentials (for the trigger and reply nodes)
  • Google Calendar credentials (for both calendar checks)
  • A dedicated work calendar selected in the Calendar nodes

Workflow Logic

  1. Gmail Trigger
  • Monitors incoming emails every minute
  • Can be filtered (e.g., labels or VIP senders)
  1. Calendar Check #1
  • Inspects if any events remain today
  1. Calendar Check #2
  • If no remaining events, scan the next 14 days for the next event
  1. Function Node
  • Formats the return date as Weekday, Month D, YYYY (e.g., “Thursday, July 24, 2025”)
  1. Gmail Send
  • Sends a customized out‑of‑office email, using the formatted date
  • Optionally includes n8n attribution (editable)

User Setup Instructions

  • Gmail Trigger: Connect your Gmail account and add any desired filters (labels, senders).
  • Google Calendar Nodes: Connect your calendar account and select your “work” calendar in both nodes.
  • Function Node: No changes needed unless you prefer a different date format.
  • Gmail Send Node: Edit the message template and toggle attribution as desired.

Customization - Options

Edit the final email content and tone in the Send node

  • Adjust calendar lookahead in Calendar Check #2 (default is 14 days)
  • Add Gmail filters to restrict auto-replies (e.g. only specific senders or labels)

Why It's Useful

Ideal for freelancers, consultants, or remote workers who don’t follow a strict 9–5, yet want automated responses aligned with their actual availability, not a static setting. It’s dynamic, real-time, and easy to tweak.

Classification

Use Case: Calendar-driven out-of-office automation

Recommended audience: Business professionals, freelancers, remote employees

Dynamically Send Out-of-Office/Vacation Messages Using Gmail & Google Calendar

This n8n workflow automates the process of sending out-of-office (OOO) or vacation messages via Gmail, based on your Google Calendar events. It intelligently checks your calendar for specific keywords and, if found, enables or disables your Gmail vacation responder accordingly.

What it does

  1. Monitors Gmail for new emails: The workflow is triggered whenever a new email arrives in your Gmail inbox.
  2. Checks Google Calendar for OOO events: For each new email, it queries your Google Calendar for events happening now that contain specific keywords like "OOO", "Out of Office", or "Vacation".
  3. Determines OOO status: It uses a Code node to process the calendar events and determine if you are currently in an "Out of Office" state.
  4. Conditionally sends OOO messages: An IF node then checks the OOO status:
    • If OOO: It enables your Gmail vacation responder with a predefined message.
    • If NOT OOO: It ensures your Gmail vacation responder is disabled.
  5. Provides a visual note: A Sticky Note reminds users to configure the keywords in the Code node.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • Google Account: A Google account with access to both Gmail and Google Calendar.
  • Gmail Credential: An n8n credential configured for your Google Account to access Gmail.
  • Google Calendar Credential: An n8n credential configured for your Google Account to access Google Calendar.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Click on the "Gmail Trigger" node and select your Gmail Google OAuth2 credential.
    • Click on the "Google Calendar" node and select your Google Calendar Google OAuth2 credential.
    • Click on the "Gmail" node and select your Gmail Google OAuth2 credential.
  3. Customize OOO Keywords:
    • Open the "Code" node.
    • Locate the section where keywords for "Out of Office" events are defined.
    • Modify the array of keywords (['OOO', 'Out of Office', 'Vacation']) to match the terms you use in your Google Calendar events to signify out-of-office periods.
  4. Customize Vacation Responder Message:
    • Open the "Gmail" node (the one connected to the "True" branch of the "If" node).
    • In the "Operation" field, ensure "Update Vacation Responder" is selected.
    • Edit the "Subject" and "Message" fields to your desired out-of-office reply.
  5. Activate the workflow: Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the n8n editor.

The workflow will now automatically check your calendar for OOO events whenever you receive an email and manage your Gmail vacation responder accordingly.

Related Templates

Automated YouTube video uploads with 12h interval scheduling in JST

This workflow automates a batch upload of multiple videos to YouTube, spacing each upload 12 hours apart in Japan Standard Time (UTC+9) and automatically adding them to a playlist. ⚙️ Workflow Logic Manual Trigger — Starts the workflow manually. List Video Files — Uses a shell command to find all .mp4 files under the specified directory (/opt/downloads/单词卡/A1-A2). Sort and Generate Items — Sorts videos by day number (dayXX) extracted from filenames and assigns a sequential order value. Calculate Publish Schedule (+12h Interval) — Computes the next rounded JST hour plus a configurable buffer (default 30 min). Staggers each video’s scheduled time by order × 12 hours. Converts JST back to UTC for YouTube’s publishAt field. Split in Batches (1 per video) — Iterates over each video item. Read Video File — Loads the corresponding video from disk. Upload to YouTube (Scheduled) — Uploads the video privately with the computed publishAtUtc. Add to Playlist — Adds the newly uploaded video to the target playlist. 🕒 Highlights Timezone-safe: Pure UTC ↔ JST conversion avoids double-offset errors. Sequential scheduling: Ensures each upload is 12 hours apart to prevent clustering. Customizable: Change SPANHOURS, BUFFERMIN, or directory paths easily. Retry-ready: Each upload and playlist step has retry logic to handle transient errors. 💡 Typical Use Cases Multi-part educational video series (e.g., A1–A2 English learning). Regular content release cadence without manual scheduling. Automated YouTube publishing pipelines for pre-produced content. --- Author: Zane Category: Automation / YouTube / Scheduler Timezone: JST (UTC+09:00)

ZaneBy Zane
226

Automate event RSVPs with email validation & badge generation using VerifiEmail & HTMLCssToImage

Validated RSVP Confirmation with Automated Badge Generation Overview: This comprehensive workflow automates the entire event RSVP process from form submission to attendee confirmation, including real-time email validation and personalized digital badge generation. ✨ KEY FEATURES: • Real-time Email Validation - Verify attendee emails using VerifiEmail API to prevent fake registrations • Automated Badge Generation - Create beautiful, personalized event badges with attendee details • Smart Email Routing - Send confirmation emails with badges for valid emails, rejection notices for invalid ones • Comprehensive Logging - Track all RSVPs (both valid and invalid) in Google Sheets for analytics • Dual Path Logic - Handle valid and invalid submissions differently with conditional branching • Anti-Fraud Protection - Detect disposable emails and invalid domains automatically 🔧 WORKFLOW COMPONENTS: Webhook Trigger - Receives RSVP submissions Email Validation - Verifies email authenticity using VerifiEmail API Conditional Logic - Separates valid from invalid submissions Badge Creator - Generates HTML-based personalized event badges Image Converter - Converts HTML badges to shareable PNG images using HTMLCssToImage Email Sender - Delivers confirmation with badge or rejection notice via Gmail Data Logger - Records all attempts in Google Sheets for tracking and analytics 🎯 PERFECT FOR: • Conference organizers managing hundreds of RSVPs • Corporate event planners requiring verified attendee lists • Webinar hosts preventing fake registrations • Workshop coordinators issuing digital badges • Community event managers tracking attendance 💡 BENEFITS: • Reduces manual verification time by 95% • Eliminates fake email registrations • Creates professional branded badges automatically • Provides real-time RSVP tracking and analytics • Improves attendee experience with instant confirmations • Maintains clean, verified contact lists 🛠️ REQUIRED SERVICES: • n8n (cloud or self-hosted) • VerifiEmail API (https://verifi.email) • HTMLCssToImage API (https://htmlcsstoimg.com) • Gmail account (OAuth2) • Google Sheets 📈 USE CASE SCENARIO: When someone submits your event RSVP form, this workflow instantly validates their email, generates a personalized badge with their details, and emails them a confirmation—all within seconds. Invalid emails receive a helpful rejection notice, and every submission is logged for your records. No manual work required! 🎨 BADGE CUSTOMIZATION: The workflow includes a fully customizable HTML badge template featuring: • Gradient background with modern design • Attendee name, designation, and organization • Event name and date • Email address and validation timestamp • Google Fonts (Poppins) for professional typography 📊 ANALYTICS INCLUDED: Track metrics like: • Total RSVPs received • Valid vs invalid email ratio • Event-wise registration breakdown • Temporal patterns • Organization/company distribution ⚡ PERFORMANCE: • Processing time: ~3-5 seconds per RSVP • Scales to handle 100+ concurrent submissions • Email delivery within 10 seconds • Real-time Google Sheets updates 🔄 EASY SETUP: Import the workflow JSON Configure your credentials (detailed instructions included) Create your form with required fields (name, email, event, designation, organization) Connect the webhook Activate and start receiving validated RSVPs! 🎓 LEARNING VALUE: This workflow demonstrates: • Webhook integration patterns • API authentication methods • Conditional workflow branching • HTML-to-image conversion • Email automation best practices • Data logging strategies • Error handling techniques ---

Jitesh DugarBy Jitesh Dugar
67

Automatically detect & classify GitHub API errors with GPT-4o to Airtable, Notion & Slack

Automatically detect, classify, and document GitHub API errors using AI. This workflow connects GitHub, OpenAI (GPT-4o), Airtable, Notion, and Slack to build a real-time, searchable API error knowledge base — helping engineering and support teams respond faster, stay aligned, and maintain clean documentation. ⚙️📘💬 🚀 What This Template Does 1️⃣ Triggers on new or updated GitHub issues (API-related). 🪝 2️⃣ Extracts key fields (title, body, repo, and link). 📄 3️⃣ Classifies issues using OpenAI GPT-4o, identifying error type, category, root cause, and severity. 🤖 4️⃣ Validates & parses AI output into structured JSON format. ✅ 5️⃣ Creates or updates organized FAQ-style entries in Airtable for quick lookup. 🗂️ 6️⃣ Logs detailed entries into Notion, maintaining an ongoing issue knowledge base. 📘 7️⃣ Notifies the right Slack team channel (DevOps, Backend, API, Support) with concise summaries. 💬 8️⃣ Tracks & prevents duplicates, keeping your error catalog clean and auditable. 🔄 💡 Key Benefits ✅ Converts unstructured GitHub issues into AI-analyzed documentation ✅ Centralizes API error intelligence across teams ✅ Reduces time-to-resolution for recurring issues ✅ Maintains synchronized records in Airtable & Notion ✅ Keeps DevOps and Support instantly informed through Slack alerts ✅ Fully automated, scalable, and low-cost using GPT-4o ⚙️ Features Real-time GitHub trigger for API or backend issues GPT-4o-based AI classification (error type, cause, severity, confidence) Smart duplicate prevention logic Bi-directional sync to Airtable + Notion Slack alerts with contextual AI insights Modular design — easy to extend with Jira, Teams, or email integrations 🧰 Requirements GitHub OAuth2 credentials OpenAI API key (GPT-4o recommended) Airtable Base & Table IDs (with fields like Error Code, Category, Severity, Root Cause) Notion integration with database access Slack Bot token with chat:write scope 👥 Target Audience Engineering & DevOps teams managing APIs Customer support & SRE teams maintaining FAQs Product managers tracking recurring API issues SaaS orgs automating documentation & error visibility 🪜 Step-by-Step Setup Instructions 1️⃣ Connect your GitHub account and enable the “issues” webhook event. 2️⃣ Add OpenAI credentials (GPT-4o model for classification). 3️⃣ Create an Airtable base with fields: Error Code, Category, Root Cause, Severity, Confidence. 4️⃣ Configure your Notion database with matching schema and access. 5️⃣ Set up Slack credentials and choose your alert channels. 6️⃣ Test with a sample GitHub issue to validate AI classification. 7️⃣ Enable the workflow — enjoy continuous AI-powered issue documentation!

Rahul JoshiBy Rahul Joshi
41