How kjudeh/whatsapp-ai-receptionist works
This repository is a Railway deployment template for a WhatsApp AI receptionist. A customer message reaches Evolution API, which forwards events to the imported n8n workflow; the workflow filters messages, handles handoff and office-hours behavior, calls an AI provider when appropriate, and sends replies through Evolution. The README documents persistent session and application data in PostgreSQL, Evolution caching in Redis, and instance files on a volume. The workflow JSON and service directories are present, but source excerpts were unavailable, so internal wiring beyond documented relationships is not inferred.
Main entry points: evolution Evolution API · whatsapp-ai-receptionist.json Reception workflow · n8n n8n runtime
Components 15
WhatsApp messaging
- Evolution API
services/evolution - Instance manager
services/evolution
Reception workflow
- n8n runtime
services/n8n - Reception workflow
workflows/whatsapp-ai-receptionist.json - Message filters
workflows/whatsapp-ai-receptionist.json - Human handoff
workflows/whatsapp-ai-receptionist.json - Office-hours reply
workflows/whatsapp-ai-receptionist.json - Business context
workflows/whatsapp-ai-receptionist.json
Persistent state
- PostgreSQL
- Redis
- Instance volume
Other components
- Customer
- AI provider
- Business owner
Connections 17
- Customer → WhatsApp: sends message
- WhatsApp → Evolution API: delivers message
- Business owner → Instance manager: pairs device
- Instance manager → Evolution API: configures instance
- Evolution API → n8n runtime: forwards webhook
- n8n runtime → Reception workflow: runs
- Reception workflow → Message filters: filters event
- Reception workflow → Human handoff: checks keyword
- Reception workflow → Office-hours reply: checks schedule
- Reception workflow → Business context: provides context
- Reception workflow → AI provider: requests answer
- Reception workflow → Evolution API: sends reply
- Evolution API → WhatsApp: sends message
- Evolution API → PostgreSQL: stores session data
- n8n runtime → PostgreSQL: stores workflow data
- Evolution API → Redis: uses cache
- Evolution API → Instance volume: persists instance files