Generate incident response reports with Supabase, Gemini and Claude
Needs changesWhat this workflow does
This AI workflow has 53 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Embeddings Google Gemini, Supabase, Supabase Vector Store and Supabase: Insert and 2 more.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Code: runs custom JavaScript code
- Create a row (Supabase): uses Supabase
- Config (Edit Fields (Set)): sets 14 fields: github_repo, github_baseUrl, model_chat…
- Historical Incidents RAG Agent (AI Agent): runs an AI agent, with model: Threat Intel Model; 1 tool (Resolved Incidents Vector Store); output parser: Structured Output Parser
- Playbook Routing Agent (AI Agent): runs an AI agent, with model: Playbook RAG Model; 1 tool (Reference Playbooks Vector Store); output parser: Structured Output Parser
- Threat Intel Enrichment Agent (AI Agent): runs an AI agent, with model: Historical RAG Model; 1 tool (Search in Tavily); output parser: Structured Output Parser
- Historical RAG Data Formatter (Edit Fields (Set)): sets 1 field: past_incident_data
- Fetch Full Playbook from Supabase (Supabase): get
- Threat Intel Data Formatter (Edit Fields (Set)): sets 1 field: external_threat_data
- Edit Fields (Edit Fields (Set)): sets 1 field: message
…plus 21 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
2 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- AI Agent v1 (old agent modes) in Historical Incidents RAG Agent (v1.7), Playbook Routing Agent (v1.7): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
- Supabase: Insert in Supabase Vector Insert (Resolved Incidents), Supabase Vector Insert (Playbooks Ingestion): replace with Supabase Vector Store (Insert Documents).
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) Historical Incidents RAG Agent (v1.7), Playbook Routing Agent (v1.7) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
| Supabase: Insert Supabase Vector Insert (Resolved Incidents), Supabase Vector Insert (Playbooks Ingestion) | Supabase Vector Store (Insert Documents) |
Rarely used nodes in this template: @n8n/n8n-nodes-langchain.vectorStoreSupabaseInsert
Nodes used (20)
- Default Data Loader
@n8n/n8n-nodes-langchain.documentDefaultDataLoader - Embeddings Google Gemini
@n8n/n8n-nodes-langchain.embeddingsGoogleGemini - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Supabase
n8n-nodes-base.supabase - Merge
n8n-nodes-base.merge - Basic LLM Chain
@n8n/n8n-nodes-langchain.chainLlm - AI Agent
@n8n/n8n-nodes-langchain.agent - Tavily Tool
@tavily/n8n-nodes-tavily.tavilyTool - Supabase Vector Store
@n8n/n8n-nodes-langchain.vectorStoreSupabase - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Recursive Character Text Splitter
@n8n/n8n-nodes-langchain.textSplitterRecursiveCharacterTextSplitter - Supabase: Insert
@n8n/n8n-nodes-langchain.vectorStoreSupabaseInsert - Wait
n8n-nodes-base.wait - OpenRouter Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenRouter - No Operation, do nothing
n8n-nodes-base.noOp - Webhook
n8n-nodes-base.webhook
From the author
Quick Overview This workflow ingests incident and playbook content from GitHub into Supabase (including pgvector embeddings with Google Gemini) and, on a webhook trigger, enriches a test incident with historical matches, a routed response playbook, and live…