Skip to main content

Automated daily Outlook calendar meeting digest

Workflow preview

Workflow preview
100%
Automated daily Outlook calendar meeting digest preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Automated Daily Outlook Calendar Meeting Digest Overall Goal This workflow automatically runs at a scheduled time (daily at 8 AM by default), calculates the current day's date range, fetches all ca...

Best for

  • Personal Productivity automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.microsoftoutlook, n8n-nodes-base.code, n8n-nodes-base.set, n8n-nodes-base.emailsend, n8n-nodes-base.scheduletrigger, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Akhil Varma Gadiraju.

Original n8n.io source

1.1 Workflow description

Title
Automated daily Outlook calendar meeting digest
Workflow name
Automated daily Outlook calendar meeting digest

Automated Daily Outlook Calendar Meeting Digest

Overall Goal

This workflow automatically runs at a scheduled time (daily at 8 AM by default), calculates the current day's date range, fetches all calendar events from a specified Microsoft Outlook account for that day, formats these events into a user-friendly HTML email, and then sends this digest to a designated email address.


How it Works (Step-by-Step Breakdown):

Node: Schedule Trigger (Schedule Trigger Node)

  • Type: n8n-nodes-base.scheduleTrigger
  • Purpose: Automatically starts the workflow at a predefined time.
  • Configuration:
    • Rule > Interval > Trigger At Hour: 8
      (Triggers every day at 8:00 AM according to the n8n server's timezone)
  • Output: Triggers the workflow execution at the scheduled time.

Node: Code (Code Node)

  • Type: n8n-nodes-base.code
  • Purpose: Dynamically calculates the start and end timestamps for "today," based on when the workflow is triggered.
  • Configuration (JS Code):
    • Gets the current date and time (workflow runtime).
    • Sets today to beginning of current day (00:00:00).
    • Sets tomorrow to beginning of next day (00:00:00).
    • Converts these to ISO string format (e.g., 2023-10-27T00:00:00Z).
  • Output: JSON object with today and tomorrow ISO date strings.

Node: Microsoft Outlook (Microsoft Outlook Node)

  • Type: n8n-nodes-base.microsoftOutlook
  • Purpose: Fetch calendar events from Outlook within the calculated date range.
  • Configuration:
    • Resource: Event
    • Filters (Custom):
      start/dateTime ge '{{$json.today}}' and start/dateTime lt '{{$json.tomorrow}}'
      

    (OData filter to fetch events starting on or after today and before tomorrow, i.e., all today's events.)

  • Output: List of event objects from Outlook.

Node: Edit Fields (Set Node)

  • Type: n8n-nodes-base.set
  • Purpose: Transform and simplify the event data structure from Outlook.
  • Configuration: Maps fields from Outlook event to new field names:
    • id
    • subject
    • description (from bodyPreview)
    • meeting_start
    • meeting_end
    • attendees
    • meeting_organizer
    • meeting_organizer_email
    • meeting_link
  • Output: List of JSON objects with simplified meeting details.

Node: Generate HTML (Code Node)

  • Type: n8n-nodes-base.code
  • Purpose: Generate a single HTML email body summarizing all meetings and create the email subject line.
  • Configuration (JS Code):
    • Processes all meeting items from "Edit Fields" node.
    • Defines generateMeetingReminderEmail function to format each meeting into an HTML "card."
    • Escapes HTML special characters, formats times, attendees, etc.
    • Concatenates all cards into a full HTML document.
    • Generates subject line (e.g., "🗓️ Your Meetings Today – Friday, Oct 27").
  • Output: JSON object with:
    {
      "subject": "email subject string",
      "html": "generated HTML content string"
    }
    

Node: Send Email (Email Send Node)

  • Type: n8n-nodes-base.emailSend
  • Purpose: Send the generated HTML digest email to the designated recipient.
  • Configuration:
    • From Email: [email protected]
    • To Email: [email protected]
    • Subject: {{ $json.subject }} (dynamic from Generate HTML node)
    • HTML: {{ $json.html }} (dynamic from Generate HTML node)
  • Output: Email sending status.

Sticky Notes

  • Update Time: Near "Schedule Trigger" node; configure trigger time as needed.
  • Update Email Details: Near "Send Email" node; change sender and receiver email addresses.

How to Customize It

  • Schedule (Schedule Trigger node):
    Modify the trigger hour, minutes, or days of week to change when the workflow runs.

  • Date Range (Code node):
    Adjust JS to change date range (e.g., next business day, upcoming week).

  • Outlook Calendar (Microsoft Outlook node):
    Specify Calendar ID or refine OData filters for event selection.

  • Event Details (Edit Fields node):
    Add/remove/modify event fields extracted.

  • Email Appearance and Content (Generate HTML node):
    Change CSS styling, meeting details, or subject line logic.

  • No Meetings Scenario:
    Use an "If" node after "Edit Fields" to handle no-meeting days (e.g., send "No meetings today!" email or skip email).

  • Email Recipients (Send Email node):
    Update "From" and "To" emails; multiple recipients separated by commas.


Error Handling

  • Use "Error Trigger" nodes to catch and handle failures (Outlook API, SMTP errors).
  • Send alerts or log errors accordingly.

Use Cases

  • Automated Daily Personal Meeting Briefing: Get daily email summaries of your meetings.
  • Automated Team Meeting Digest: Send daily team calendar digest emails.
  • Proactive Daily Planning: Automatically stay informed of your day’s schedule.

Required Credentials

Add these credentials in your n8n instance under Credentials:

  • Microsoft Outlook (OAuth2 API):

    • Used by: "Microsoft Outlook" node
    • Credential Name in Workflow: Outlook (ID: JcYqVJwcwZIhB8oy)
    • Requires OAuth2 with Calendars.Read permission.
  • SMTP:

    • Used by: "Send Email" node
    • Credential Name in Workflow: SMTP account (ID: vCexcphurglwGBfk)
    • Requires SMTP server details (host, port, username, password).

Ensure these credentials are configured correctly with required permissions. Activate the workflow for scheduled execution.


Made with ❤️ using n8n by Akhil.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Microsoft Outlook

Type / Role
n8n-nodes-base.microsoftOutlook - microsoftOutlook
Config choices
Version 2

Block 2 - Code

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 3 - Edit Fields

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 4 - Send Email

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

Block 5 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 6 - Generate HTML

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 7 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 8 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Automated daily Outlook calendar meeting digest
Complexity intermediate
Nodes 8
Categories Personal Productivity
Author Akhil Varma Gadiraju
Published 27 May 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/4420/4420.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automated daily Outlook calendar meeting digest do?

Automated Daily Outlook Calendar Meeting Digest Overall Goal This workflow automatically runs at a scheduled time (daily at 8 AM by default), calculates the current day's date range, fetches all ca...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Personal Productivity use case.