AI Email processing autoresponder with approval (Yes/No)
Configured with Agent, Chain Summarization, Email Read Imap, Email Send, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Messaging
- Transform
- AI & models
- Data store
- Routing
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 |
| DeepSeek R1 | AI & models | OpenAI Chat Model | 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 |
| Set Email | Transform | Edit Fields | See node parameters |
| Approve? | Routing | If | See node parameters |
| Send Draft | Messaging | Gmail | sendAndWait |
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
gmailOAuth2imapopenAiApiqdrantApismtp
Workflow notes
Main Flow
Main Flow
Preliminary step:
Create a vector database on Qdrant and tokenize the documents useful for generating a response
How it works
This workflow is designed to automate the process of handling incoming emails, summarizing their content, generating appropriate responses with RAG, and obtaining approval (YES/NO button) before sending replies.
This workflow is designed to handle general inquiries that come in via corporate email via IMAP and generate responses using RAG. You can quickly integrate Gmail and Outlook via the appropriate trigger nodes
Sticky Note1
Convert email to Markdown format for better understanding of LLM models
Sticky Note2
Chain that summarizes the received email
Sticky Note3
Agent that retrieves business information from a vector database and processes the response
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.
AI Email processing autoresponder with approval (Yes/No)
AI Email processing autoresponder with approval (Yes/No)
Purpose and structure
This folder contains the AI Email processing autoresponder with approval (Yes/No) workflow. Its executable nodes use agent, chainSummarization, emailReadImap, emailSend, embeddingsOpenAi, gmail, if, lmChatOpenAi, markdown, set, 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
Inspect connections; no recognized trigger.
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/1588_Emailreadimap_Markdown_Send.json MIT; preserve source notices.