Store chat data in Supabase PostgreSQL for WhatsApp/Slack chatbot
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 6 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Google Gemini Chat Model, Postgres Chat Memory and Supabase.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Set sample Input Variables (Edit Fields (Set)): sets 3 fields: session_id, name, chatInput
- Sample Agent (AI Agent): runs an AI agent, with model: GeminiFlash2.; memory: Supabase Postgres Database
- Update additonal Values e.g. Name, Address ... (Supabase): update
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- AI Agent v1 (old agent modes) in Sample 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.
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) Sample Agent (v1.7) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (6)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Postgres Chat Memory
@n8n/n8n-nodes-langchain.memoryPostgresChat - Supabase
n8n-nodes-base.supabase - AI Agent
@n8n/n8n-nodes-langchain.agent
From the author
n8n Template: Store Chat Data in Supabase PostgreSQL for WhatsApp/Slack Integration This n8n template captures chat data (like user ID, name, or address) and saves it to a Supabase PostgreSQL database. It’s built for testing now but designed to work with…