← All N8N workflows
AI & researchAgentChain LLMHTTP RequestLM Chat Google GeminiMemory Buffer Window

Activate workflow to use!

Configured with Agent, Chain LLM, HTTP Request, LM Chat Google Gemini, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
TriggerWhatsApp TriggerWhats App TriggerMessagingGet Audio URLWhats AppMessagingGet Video URLWhats AppMessagingGet Image URLWhats AppWeb / APIDownload VideoHTTP RequestWeb / APIDownload AudioHTTP RequestWeb / APIDownload ImageHTTP RequestData storeWindow Buffer MemoryMemory Buffer WindowTransformGet User's MessageEdit FieldsTransformSplit Out Message PartsSplit OutIntegrationWikipediaTool WikipediaRoutingRedirect Message TypesSwitchWaitGet TextWaitMessagingRespond to UserWhats AppAI & modelsImage ExplainerChain LLMTransformFormat ResponseEdit FieldsAI & modelsGoogle Gemini ChatModelLM Chat Google GeminiWeb / APIGoogle Gemini AudioHTTP RequestWeb / APIGoogle Gemini VideoHTTP RequestAI & modelsGoogle Gemini ChatModel1LM Chat Google GeminiAI & modelsGoogle Gemini ChatModel2LM Chat Google GeminiTransformFormat Response1Edit FieldsAI & modelsText SummarizerChain LLMAI & modelsAI AgentAgent

Node categories in this workflow

  • Trigger
  • Messaging
  • Web / API
  • Data store
  • Transform
  • Integration
  • Routing
  • Wait
  • AI & models

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
WhatsApp TriggerTriggerWhats App TriggerSee node parameters
Get Audio URLMessagingWhats Appmedia / mediaUrlGet
Get Video URLMessagingWhats Appmedia / mediaUrlGet
Get Image URLMessagingWhats Appmedia / mediaUrlGet
Download VideoWeb / APIHTTP RequestSee node parameters
Download AudioWeb / APIHTTP RequestSee node parameters
Download ImageWeb / APIHTTP RequestSee node parameters
Window Buffer MemoryData storeMemory Buffer WindowSee node parameters
Get User's MessageTransformEdit FieldsSee node parameters
Split Out Message PartsTransformSplit OutSee node parameters
WikipediaIntegrationTool WikipediaSee node parameters
Redirect Message TypesRoutingSwitchSee node parameters
Get TextWaitWaitSee node parameters
Respond to UserMessagingWhats Appsend
Image ExplainerAI & modelsChain LLMSee node parameters
Format ResponseTransformEdit FieldsSee node parameters
Google Gemini Chat ModelAI & modelsLM Chat Google GeminiSee node parameters
Google Gemini AudioWeb / APIHTTP RequestPOST
Google Gemini VideoWeb / APIHTTP RequestPOST
Google Gemini Chat Model1AI & modelsLM Chat Google GeminiSee node parameters
Google Gemini Chat Model2AI & modelsLM Chat Google GeminiSee node parameters
Format Response1TransformEdit FieldsSee node parameters
Text SummarizerAI & modelsChain LLMSee node parameters
AI AgentAI & modelsAgentSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • googlePalmApi
  • whatsAppApi
  • whatsAppTriggerApi

Workflow notes

1. WhatsApp Trigger

1. WhatsApp Trigger

Learn more about the WhatsApp Trigger

To start receiving WhatsApp messages in your workflow, there are quite a few steps involved so be sure to follow the n8n documentation. When we recieve WhatsApp messages, we'll split out the messages part of the payload and handle them depending on the message type using the Switch node.

2. Transcribe Audio Messages 💬

2. Transcribe Audio Messages 💬

For audio messages or voice notes, we can use GPT4o to transcribe the message for our AI Agent.

3. Describe Video Messages 🎬

3. Describe Video Messages 🎬

For video messages, one approach is to use a Multimodal Model that supports parsing video. Currently, Google Gemini is a well-tested service for this task. We'll need to use the HTTP request node as currrently n8n's LLM node doesn't currently support video binary types.

4. Analyse Image Messages 🏞️

4. Analyse Image Messages 🏞️

For image messages, we can use GPT4o to explain what is going on in the message for our AI Agent.

5. Text summarizer 📘

5. Text summarizer 📘

For text messages, we don't need to do much transformation but it's nice to summarize for easier understanding.

6. Generate Response with AI Agent

6. Generate Response with AI Agent

Read more about the AI Agent node

Now that we'll able to handle all message types from WhatsApp, we could do pretty much anything we want with it by giving it our AI agent. Examples could include handling customer support, helping to book appointments or verifying documents.

In this demonstration, we'll just create a simple AI Agent which responds to our WhatsApp user's message and returns a simple response.

7. Respond to WhatsApp User

7. Respond to WhatsApp User

Read more about the Whatsapp node

To close out this demonstration, we'll simple send a simple text message back to the user. Note that this WhatsApp node also allows you to send images, audio, videos, documents as well as location!

Try It Out!

Try It Out!

This n8n template demonstrates the beginnings of building your own n8n-powered WhatsApp chatbot! Under the hood, utilise n8n's powerful AI features to handle different message types and use an AI agent to respond to the user. A powerful tool for any use-case!

  • Incoming WhatsApp Trigger provides a way to get messages into the workflow.
  • The message received is extracted and sent through 1 of 4 branches for processing.
  • Each processing branch uses AI to analyse, summarize or transcribe the message so that the AI agent can understand it.
  • The AI Agent is used to generate a response generally and uses a wikipedia tool for more complex queries.
  • Finally, the response message is sent back to the WhatsApp user using the WhatsApp node.

Need Help?

Join the Discord or ask in the Forum!

Activate workflow to use!

Activate workflow to use!

You must activate the workflow to use this WhatsApp Chabot. If you are self-hosting, ensure WhatsApp is able to connect to your server.

🚨 Google Gemini Required!

🚨 Google Gemini Required!

Not using Gemini? Feel free to swap this out for any Multimodal Model that supports Video.

🚨 Google Gemini Required!

🚨 Google Gemini Required!

Not using Gemini? Feel free to swap this out for any Multimodal Model that supports Audio.

Activate workflow to use!

Activate workflow to use!

Purpose and structure

This folder contains the Activate workflow to use! workflow. Its executable nodes use agent, chainLlm, httpRequest, lmChatGoogleGemini, memoryBufferWindow, set, splitOut, switch, toolWikipedia, wait, whatsApp, whatsAppTrigger. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

WhatsApp Trigger

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Wait/0602_Wait_Splitout_Send_Webhook.json MIT; preserve source notices.

More in AI & research