How leandrobon/waflow works
Project type and purpose
• WAFlow is a full-stack sandbox application for local development and testing of webhook-based WhatsApp-style bots. It consists of three .NET services (Simulator API, Blazor UI, Example Bot), all wired together via Docker Compose or local URLs.
File structure
• Top-level services:
• WAFlow.Simulator – Minimal API (.NET) for injecting messages, dispatching webhooks, and storing message feeds in memory.
• WAFlow.Chat – Blazor UI (Razor components) for chat interface, polling the simulator, import/export JSON, and environment status.
• EchoBot.Example – Minimal API example webhook that auto-registers with the simulator and echoes inbound text.
• Shared artifacts: docker-compose.yml, solution file, per-service Dockerfiles, appsettings.json, launchSettings.json.
• Patterns: microservices (three independent processes), in-memory persistence, HTTP-based interfaces, polling vs. webhook callbacks.
Key insights from the README
• Ports: UI (5056), Simulator (5080), EchoBot (5199).
• In Docker: inter-service communication via service DNS on port 8080 (http://sim:8080, http://echobot:8080).
• Core flows: UI → poll Simulator → display messages; Simulator → invoke webhook; webhook → post back to Simulator; UI → import/export/reset.
Detailed capture of essential elements
• Both registry and message store sub-components inside the Simulator boundary.