Effortless Email Management with AI
Configured with Agent, Chain Summarization, Document Default Data Loader, Email Read Imap, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Messaging
- Transform
- Data store
- AI & models
- Trigger
- Web / API
- Files / media
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Email Trigger (IMAP) | Messaging | Email Read Imap | See node parameters |
| Markdown | Transform | Markdown | See node parameters |
| Send Email | Messaging | Email Send | See node parameters |
| Qdrant Vector Store | Data store | Vector Store Qdrant | See node parameters |
| Embeddings OpenAI | AI & models | Embeddings Open Ai | See node parameters |
| Email Summarization Chain | AI & models | Chain Summarization | See node parameters |
| Write email | AI & models | Agent | See node parameters |
| OpenAI | AI & models | OpenAI Chat Model | See node parameters |
| Gmail | Messaging | Gmail | sendAndWait |
| Text Classifier | AI & models | Text Classifier | See node parameters |
| Edit Fields | Transform | Edit Fields | See node parameters |
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Create collection | Web / API | HTTP Request | POST |
| Refresh collection | Web / API | HTTP Request | POST |
| Get folder | Files / media | Google Drive | fileFolder |
| Download Files | Files / media | Google Drive | download |
| Default Data Loader | Files / media | Document Default Data Loader | See node parameters |
| Token Splitter | Transform | Text Splitter Token Splitter | See node parameters |
| Qdrant Vector Store1 | Data store | Vector Store Qdrant | See node parameters |
| Embeddings OpenAI1 | AI & models | Embeddings Open Ai | See node parameters |
| DeepSeek Chat Model | AI & models | LM Chat Deep Seek | See node parameters |
| Email Reviewer | AI & models | Agent | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
deepSeekApigmailOAuth2googleDriveOAuth2ApihttpHeaderAuthimapopenAiApiqdrantApismtp
Workflow notes
STEP 1
STEP 1
Create Qdrant Collection
Change:
- QDRANTURL
- COLLECTION
STEP 2
STEP 2
Documents vectorization with Qdrant and Google Drive
Change:
- QDRANTURL
- COLLECTION
STEP 3 - MAIN FLOW
STEP 3 - MAIN FLOW
How it works
This workflow automates the handling of incoming emails, summarizes their content, generates appropriate responses using a retrieval-augmented generation (RAG) approach, and obtains approval or suggestions before sending replies.
You can quickly integrate Gmail and Outlook via the appropriate trigger nodes
Sticky Note2
Chain that summarizes the received email
Sticky Note5
Agent that retrieves business information from a vector database and processes the response
Sticky Note1
Convert email to Markdown format for better understanding of LLM models
IMPORTANT
IMPORTANT
For the "Send Draft" node, you need to send the draft email to a Gmail address because it is the only one that allows the "Send and wait for response" function.
Sticky Note7
Based on the suggestion received, the text classifier can understand whether the feedback received approves the generated email or not.
Sticky Note8
The Email Reviewer agent, taking inspiration from human feedback, rewrites the email
Effortless Email Management with AI
Effortless Email Management with AI
Purpose and structure
This folder contains the Effortless Email Management with AI workflow. Its executable nodes use agent, chainSummarization, documentDefaultDataLoader, emailReadImap, emailSend, embeddingsOpenAi, gmail, googleDrive, httpRequest, lmChatDeepSeek, lmChatOpenAi, manualTrigger, markdown, set, textClassifier, textSplitterTokenSplitter, vectorStoreQdrant. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking ‘Test workflow’
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Emailreadimap/1427_Emailreadimap_Manual_Send_Webhook.json MIT; preserve source notices.