Skip to main content

Triage VIP Outlook emails using Excel, GPT-4o and Microsoft To Do

Workflow preview

Workflow preview
100%
Triage VIP Outlook emails using Excel, GPT-4o and Microsoft To Do preview
Open on n8n.io

1. Workflow Overview

Quick overview This workflow polls Microsoft Outlook every 5 minutes, deduplicates email threads, checks senders against a VIP list in Microsoft Excel, uses OpenAI (GPT 4o) to detect urgency, and c...

Best for

  • Ticket Management automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.microsoftoutlooktrigger, n8n-nodes-base.code, n8n-nodes-base.microsoftexcel, n8n-nodes-base.html, n8n-nodes-base.openai, n8n-nodes-base.if, n8n-nodes-base.microsofttodo, n8n-nodes-base.errortrigger

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mychel Garzon.

Original n8n.io source

1.1 Workflow description

Title
Triage VIP Outlook emails using Excel, GPT-4o and Microsoft To Do
Workflow name
Triage VIP Outlook emails using Excel, GPT-4o and Microsoft To Do

Quick overview

This workflow polls Microsoft Outlook every 5 minutes, deduplicates email threads, checks senders against a VIP list in Microsoft Excel, uses OpenAI (GPT-4o) to detect urgency, and creates a Microsoft To Do task for urgent VIP emails while emailing an admin on workflow errors.

How it works

  1. An Outlook trigger polls your inbox every 5 minutes and passes new emails downstream.
  2. A deduplication node checks each email's conversation ID against a rolling in-memory list, dropping any threads already processed in a previous run. The list is capped at 100 entries.
  3. The full priority sender list is read in a single batch from Microsoft Excel, building a fast lookup set of known email addresses — one API call, zero rate-limit risk.
  4. A code node cross-references each email against the sender set, tags matches as priority, and filters out all non-priority emails so only relevant messages continue.
  5. The HTML body of each priority email is stripped of markup and converted to clean plain text before being passed to the AI node.
  6. GPT-4o analyzes the plain text and returns a structured JSON response with an is_urgent boolean and a short summary. A parse node cleans the output and maps both fields onto the item.
  7. An IF node routes urgent emails to Microsoft To Do, creating a flagged task with the sender name and subject. Non-urgent emails exit silently with no action taken.

Setup

  1. Connect your Microsoft Outlook OAuth2 credential to both the Outlook Trigger node and the Send Error Email node. Replace [email protected] in the error node with your actual admin address.
  2. Connect your Microsoft Excel credential to the Excel: Read VIP Sheet node and point it to your priority sender workbook and sheet. Open the Code: Tag & Filter VIPs node and change the VIP_COLUMN value from 'email' to match your actual column header.
  3. Connect your OpenAI credential to the AI: Analyze Urgency node, then connect your Microsoft To Do credential to the Create VIP To Do Task node and select the target task list.

Requirements

  • Microsoft Outlook OAuth2 account with inbox access
  • Microsoft Excel file with a column of priority sender email addresses
  • OpenAI API key with access to GPT-4o
  • Microsoft To Do account with a configured task list

Customization

  • Change the polling interval in the Outlook Trigger node from 5 minutes to any frequency that suits your inbox volume.
  • Rename the VIP_COLUMN variable in the Code: Tag & Filter VIPs node to match any column header in your Excel sheet.
  • Modify the GPT-4o prompt in the AI: Analyze Urgency node to adjust what counts as urgent for your specific use case.
  • Update the To Do task title template in the Create VIP To Do Task node to include additional fields such as the email summary or received date.

Additional info

  • The deduplication node uses n8n static workflow data to persist processed conversation IDs across runs. The list is capped at 100 entries and rotates automatically to prevent memory bloat.
  • If the AI output cannot be parsed, the node defaults to is_urgent: false so the workflow never crashes on a malformed response.
  • The Error Trigger node is a global catcher — it fires on any node failure in the workflow and sends a formatted alert email to the configured admin address.

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 - Outlook Trigger

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

Block 2 - Deduplicate Threads

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

Block 3 - Excel: Read VIP Sheet

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

Block 4 - Code: Tag & Filter VIPs

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

Block 5 - Strip HTML Bloat

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

Block 6 - AI: Analyze Urgency

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

Block 7 - Parse AI Output

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

Block 8 - Is Urgent?

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

Block 9 - Create VIP To Do Task

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

Block 10 - Error Trigger

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

Block 11 - Send Error Email

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

Block 12 - Sticky Note

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

Block 13 - Sticky Note1

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

Block 14 - Sticky Note2

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

Block 15 - Sticky Note4

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

Block 16 - Sticky Note5

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

Block 17 - Sticky Note6

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

3. Summary Table

Workflow Triage VIP Outlook emails using Excel, GPT-4o and Microsoft To Do
Complexity advanced
Nodes 17
Categories Ticket Management, AI Summarization
Author Mychel Garzon
Published 21 May 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15895/15895.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 Triage VIP Outlook emails using Excel, GPT-4o and Microsoft To Do do?

Quick overview This workflow polls Microsoft Outlook every 5 minutes, deduplicates email threads, checks senders against a VIP list in Microsoft Excel, uses OpenAI (GPT 4o) to detect urgency, and c...

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 Ticket Management, AI Summarization use case.