Block 1 - Schedule Trigger1
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
Hourly Email Summary: This agent scans your inbox every 4 hour and summarizes new emails into a clean, actionable Slack message. Powered by GPT 4, it classifies emails by Urgency (High, Medium, Low...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.gmail, @n8n/n8n-nodes-langchain.openai, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.code, n8n-nodes-base.googlesheets, n8n-nodes-base.wait
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Siddhant.
Original n8n.io sourceHourly Email Summary: This agent scans your inbox every 4 hour and summarizes new emails into a clean, actionable Slack message. Powered by GPT-4, it classifies emails by Urgency (High, Medium, Low) and Intent (Awaiting Reply, To Respond, Comment, Notification, Marketing). No more inbox FOMO — just what you need to act fast.
Main Use Cases: • Stay on top of important threads without refreshing your inbox constantly • Prioritize tasks and replies based on urgency and context • Catch missed follow-ups by surfacing emails that need a response • Filter out noise like marketing emails or low-priority notifications • Enable async decision-making by keeping the team updated on critical emails via Slack • Reduce cognitive load by letting AI handle sorting and triaging ⸻
✅ Steps to Use
Step-by-Step Breakdown:
Uses a System Prompt to define its role as an AI Chief of Staff.
Uses a User Prompt that instructs GPT-4 to analyze each email and return a structured JSON with the following: • summary – One-line summary of the email • urgency – High / Medium / Low • category – Investor, Customer, Support, Spam, Other • Intent – One of: • To Respond: Needs your reply • Awaiting Reply: You’re waiting for a response • Notification: Auto-updates from tools or services • Meeting Update: Calendar or schedule changes • Marketing: Promotional or cold emails • FYI: Informational emails that don’t need action
The output is clean JSON with built-in guardrails to avoid hallucinations or irrelevant content. Only real message data is used for summaries and classification.
Sections with no relevant data are omitted to keep it concise.
🧩 What’s Next
This agent already cuts through inbox noise and gives you clarity — but there’s more you can build on top:
💡 Suggestions to Improve: • Train on your past threads to make prioritization even smarter • Allow custom rules per sender or domain (e.g. always mark investor emails as High) • Add emoji tags or reactions in Slack to quickly mark emails as done or follow-up • Support voice summary via Slack audio snippet or Loom integration
🚀 Next Features You Could Add: • Reply-from-Slack: One-click smart reply suggestions that can be sent right from Slack • Cross-inbox support: Add Outlook or multiple Gmail accounts • Weekend Digest: A weekly email or Slack drop with trends (top senders, most flagged categories) • Daily Timeline View: Generate a Notion page that logs the day’s most critical communication
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.
| Workflow | Automated email triage with Gmail, GPT-4o, and Slack urgency notifications |
|---|---|
| Complexity | advanced |
| Nodes | 17 |
| Categories | Ticket Management, AI Summarization |
| Author | Siddhant |
| Published | 28 Jul 2025 |
Use the JSON export at /data/workflows/6588/6588.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
Hourly Email Summary: This agent scans your inbox every 4 hour and summarizes new emails into a clean, actionable Slack message. Powered by GPT 4, it classifies emails by Urgency (High, Medium, Low...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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.