This article provides a complete, practical walkthrough of the Datetime Googlecalendar Send Scheduled n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:
   Automating Monthly Absence Reporting with n8n and Google Calendar
   
   Meta Description:
   Discover how to automate employee holiday and illness absence reporting using n8n and Google Calendar. This article walks through a powerful workflow that sends absence summaries to payroll each month—saving HR departments hours of manual work.
   
   Keywords:
   n8n workflow automation, Google Calendar integration, payroll automation, absence tracking, sick leave report, holiday tracking, HR automation, no-code automation tools, n8n employee tracking, email automation
   
   Third-Party APIs Used:
   
   - Google Calendar API
   - SMTP Email Service (e.g., Mailtrap or a designated SMTP server)
   
   Article:
   
   Efficient HR processes are critical to the smooth operation of any organization. One recurring task that often consumes time and effort is tracking and reporting employee absences due to holidays and illnesses. By leveraging n8n—a powerful, open-source automation tool—you can automate this process seamlessly, saving time and reducing errors. In this article, we walk through a real-world n8n workflow that identifies holiday and sick leave events in Google Calendar and emails a structured summary to the payroll department every month.
   
   🎯 The Objective
   
   The goal of this workflow is to automatically:
   - Retrieve all employee calendar events from the previous month.
   - Filter and categorize events marked as “Holiday” or “Illness.”
   - Calculate the number of days each employee was absent.
   - Consolidate the data into a readable format.
   - Email the summarized report directly to the payroll team on the 1st of every month at 8 AM.
   
   🕹️ Breakdown of the Workflow
   
   Let’s explore the key components that power this automation:
   
   1. Scheduled Trigger (CRON Node)
      - The workflow begins with a "1st of Every Month at 8am" trigger. This CRON node ensures the workflow runs on the first day of each month at exactly 08:00 AM.
   
   2. Calculate the Previous Month
      - A DateTime node calculates the start date by subtracting one month from the current date, setting the time range for our data query.
   
   3. Retrieve Google Calendar Events
      - The Google Calendar node pulls all events that fall within the calculated date range. It uses OAuth2 credentials to access the calendar and can retrieve events across various employee-shared calendars.
   
   4. Filter Relevant Events
      - The “Check Summary for Illness or Holiday” switch node checks each calendar event summary for the keywords “Holiday” or “Illness.” Depending on the content, the workflow routes the events down separate paths.
   
   5. Extract and Transform Data
      - Separate set nodes (“Filter Holiday Days” and “Filter Illness Days”) extract:
        - Employee name
        - Duration of absence (calculated from event start and end dates)
        - Absence type (Holiday or Illness)
   
   6. Aggregate Absence Durations
      - Each record is then processed by respective code nodes (“Combine Holiday Counts” and “Combine Illness Counts”). These nodes:
        - Identify unique employee names
        - Sum up the number of days each employee was absent for the event type
   
   7. Merge and Format Message
      - Both streams (Holiday and Illness data) merge into one.
      - A code node, “Build the message to send,” creates a user-friendly message summarizing all absences, organized by type with names and day counts.
   
   8. Email the Payroll Team
      - Finally, the “Send email to payroll” node sends the formatted message to the payroll-team@mydomain.tld via SMTP. For development, the setup may use Mailtrap; in production, this would typically be an internal SMTP server or a transactional email provider.
   
   📧 Sample Output
   
   The email body might look like this:
   
   Here is a breakdown of absences for the last month.
   
   Holiday Events  
   John Doe had 3 days  
   Jane Smith had 2 days  
   
   Illness Events  
   Alice Brown had 1 day  
   
   🔒 Authentication and Permissions
   
   This workflow uses two authenticated services:
   - OAuth2 to access Google Calendar: Proper permissions must be granted for the app to read calendar data.
   - SMTP credentials for sending email.
   
   ⚙️ Why Use This Automation?
   
   - Accuracy: Reduces human error in absence tracking
   - Time-saving: Automates an otherwise manual monthly report
   - Scalable: Easily adapt this workflow to include more calendar types or event tags
   - Transparent: Provides a clear audit trail through email and log history
   
   🧩 Going Beyond
   
   Here are a few ways to extend or improve this workflow:
   - Include part-day absences by processing event timestamps more granularly.
   - Integrate with Slack or Microsoft Teams for real-time notifications.
   - Automatically update HR databases using APIs or direct database connections.
   - Build a dashboard in tools like Google Sheets or Airtable for historical tracking.
   
   Conclusion
   
   Automating monthly absence summaries with n8n and Google Calendar is a smart move for any HR or payroll team. With relatively little setup, this workflow eliminates repetitive work and ensures timely, data-driven insights into employee absences. The combination of date filters, event parsing, data transformation, and email delivery demonstrates the power and flexibility of n8n as a no-code/low-code automation solution.
   
   If your team is still relying on manual review or spreadsheets for attendance tracking, it’s time to put automation to work. With n8n, what used to be a tedious monthly obligation becomes a hands-free, reliable utility.
   
   Get started today—and let your workflows do the work.

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.