Block 1 - WhatsApp Trigger
- Type / Role
- n8n-nodes-base.whatsAppTrigger - whatsAppTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Workflow Execution Link: Watch Execution Video Workflow Pre requisites Step 1: Supabase Setup First, replace the keys in the "Save the embedding ...
n8n-nodes-base.whatsapptrigger, n8n-nodes-base.googledocs, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.supabase, n8n-nodes-base.aggregate, n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by iamvaar.
Original n8n.io sourceFirst, replace the keys in the "Save the embedding in DB" & "Search Embeddings" nodes with your new Supabase keys. After that, run the following code snippets in your Supabase SQL editor:
Create the table to store chunks and embeddings:
CREATE TABLE public."RAG"
(
id bigserial PRIMARY KEY,
chunk text NULL,
embeddings vector(1024) NULL
)
TABLESPACE pg_default;
Create a function to match embeddings:
DROP FUNCTION IF EXISTS public.matchembeddings1(integer, vector);
CREATE OR REPLACE FUNCTION public.matchembeddings1(
match_count integer,
query_embedding vector
)
RETURNS TABLE (
chunk text,
similarity float
)
LANGUAGE plpgsql
AS $$
BEGIN
RETURN QUERY
SELECT
R.chunk,
1 - (R.embeddings <=> query_embedding) AS similarity
FROM public."RAG" AS R
ORDER BY R.embeddings <=> query_embedding
LIMIT match_count;
END;
$$;
Create a new Google Doc with the complete knowledge base about your business and replace the document ID in the "Content for the Training" node.
Get a Together AI API key and paste it into the "Embedding Uploaded document" node and the "Embed User Message" node.
Go to https://business.facebook.com/latest/settings/apps, create an app, and select the use case "Connect with customer through WhatsApp". Copy the Client ID and Client Secret and add them to the first node.
Go to that newly created META app in the app dashboard, click on the use case, and then click on "customise...". Go to the API setup, add your number, and also generate an access token on that page. Now paste the access token and the WhatsApp Business Account ID into the send message node.
manualTrigger googleDocs code httpRequest supabase whatsAppTrigger if httpRequest httpRequest aggregate langchain agent lmChatGoogleGemini whatsApp 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 | Build a knowledge-based WhatsApp assistant with RAG, Gemini, Supabase & Google Docs |
|---|---|
| Complexity | advanced |
| Nodes | 15 |
| Categories | Internal Wiki, AI RAG |
| Author | iamvaar |
| Published | 23 Sept 2025 |
Use the JSON export at /data/workflows/8865/8865.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.
Workflow Execution Link: Watch Execution Video Workflow Pre requisites Step 1: Supabase Setup First, replace the keys in the "Save the embedding ...
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 Internal Wiki, AI RAG use case.