Block 1 - Gmail Trigger
- Type / Role
- n8n-nodes-base.gmailTrigger - gmailTrigger
- Config choices
- Version 1.3
This workflow is provided as-is. Please review and test before using in production.
Categorise and route emails with GPT 5 This workflow demonstrates how to use AI text classifier to classify incoming emails, and uses a multi agent architecture to respond for each email category r...
n8n-nodes-base.gmailtrigger, n8n-nodes-base.noop, @n8n/n8n-nodes-langchain.embeddingsopenai, n8n-nodes-base.gmail, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.stickynote, n8n-nodes-base.gmailtool, @n8n/n8n-nodes-langchain.vectorstorepinecone
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Zawanah.
Original n8n.io sourceThis workflow demonstrates how to use AI text classifier to classify incoming emails, and uses a multi-agent architecture to respond for each email category respectively.
Business owners with a lot of incoming emails, or anyone who has huge influx of emails
Any incoming emails will be read by the text classifier powered by GPT 5, and routed according to the defined categories where respective agents will take next steps.
Other than Gmail, it is possible to connect to Outlook as well. Other than Pinecone vector database, there are other vector database that should serve the same purpose eg. supabase, qdrant, weviate
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.
Showing the first 24 of 41 workflow blocks. Download the JSON for the full node graph.
| Workflow | 📩 Automated email management system with GPT-5, multi-agent AI & Pinecone DB |
|---|---|
| Complexity | advanced |
| Nodes | 41 |
| Categories | Ticket Management, AI Chatbot |
| Author | Zawanah |
| Published | 12 Sept 2025 |
Use the JSON export at /data/workflows/8490/8490.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.
Categorise and route emails with GPT 5 This workflow demonstrates how to use AI text classifier to classify incoming emails, and uses a multi agent architecture to respond for each email category r...
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 Chatbot use case.