Block 1 - Template Header
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Description This workflow automates the first line of customer support by intelligently drafting email replies. It bridges the gap between your CRM (Supabase), your technical documentation (Vector ...
n8n-nodes-base.stickynote, n8n-nodes-base.microsoftoutlooktrigger, n8n-nodes-base.set, n8n-nodes-base.microsoftoutlook, n8n-nodes-base.googlesheets, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.vectorstoresupabase
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Matthew.
Original n8n.io sourceThis workflow automates the first line of customer support by intelligently drafting email replies. It bridges the gap between your CRM (Supabase), your technical documentation (Vector Store), and your inbox (Outlook). By analyzing the sender's identity and the technical content of the query, it ensures that every draft reply is personalized, accurate, and follows strict business rules.
contacts table using the sender's email to retrieve their name, organization, and department.[YOUR_COMPANY] and [YOUR_NAME] placeholders with your actual brand identity.If node after the Agent to send a Slack or Teams notification if the AI detects the urgency is "high."primary_product_codes identified by the AI.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 | Draft personalized Outlook support email replies with Supabase RAG and OpenAI |
|---|---|
| Complexity | intermediate |
| Nodes | 13 |
| Categories | Ticket Management, AI RAG |
| Author | Matthew |
| Published | 20 Jan 2026 |
Use the JSON export at /data/workflows/12839/12839.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.
Description This workflow automates the first line of customer support by intelligently drafting email replies. It bridges the gap between your CRM (Supabase), your technical documentation (Vector ...
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 RAG use case.