n8nClaw
shabbirun/n8nclaw
A visual, no-code reinterpretation of OpenClaw that runs entirely inside n8n workflows. It wires Telegram, WhatsApp, Gmail, and an hourly heartbeat into a Claude-powered agent with Postgres memory and Supabase RAG.
Why choose n8nClaw over OpenClaw?
Quick recommendation layer first, deeper analysis second. Use this before diving into metrics and architecture details.
- Visual workflow editing in n8n lowers coding barrier
- Leverages existing n8n integrations for channels
- Easy to audit logic as flowchart rather than code
- No compiled binary; requires running n8n stack
- Less secure isolation than containerized alternatives
- No plugin/skill ecosystem like OpenClaw
- No-code enthusiasts wanting OpenClaw-like assistant
- Self-hosters already running n8n
- Teams needing multi-channel (Telegram/WhatsApp/Gmail) bots
- Users wanting compiled binary or low-memory edge deploy
- Those needing strong sandboxing/security defaults
- Projects requiring official releases/long-term support
Evidence limited to README and initial commits; no releases or community discussion directly about n8nClaw. Web mentions refer to OpenClaw generically, creating uncertainty about project maturity.
AI decision layer last reviewed Jul 13, 2026. Use this as a lead, not as a production-grade verdict.
Source window: GitHub metadata, README, recent commits, latest release, Reddit, Brave search
Community sentiment
Security radar
How it\'s evaluated
Isolation from host OS. 10 = Fully virtualized (Docker/Wasm); 1 = Direct local execution.
Safety of external connections. 10 = End-to-end encrypted/Scoped; 1 = Plaintext/Broad access.
Traffic control. 10 = Air-gapped/Offline-first; 1 = Unrestricted internet access.
Privacy level. 10 = Zero telemetry/Zero tracking; 1 = Extensive logging/reporting.
Command safety. 10 = No unsupervised shell; 1 = Raw, unmonitored shell access.
Scale: 10 = maximum safety, 1 = high risk
Star Growth (2026)
ClawVerse news
Latest articles and global buzz
Trending Mentions
Technical showdowns
n8nClaw is a lightweight alternative to OpenClaw implemented entirely as an n8n workflow export. Instead of a compiled agent runtime, it uses n8n's visual automation canvas to connect Telegram, WhatsApp (via Evolution API), Gmail, and an hourly schedule trigger into a central Claude Sonnet 4.5 agent powered by OpenRouter. The agent maintains short-term context in Postgres chat memory (15 messages) and offloads long-term recall to a Supabase vector store via a scheduled summarization pipeline using Haiku.
The architecture emphasizes no-code customization: users edit fields like 'soul' for personality, and tiered worker sub-agents handle research, email, and document tasks. Unlike OpenClaw's native multi-platform binaries, n8nClaw requires a self-hosted or cloud n8n instance with associated Postgres and Supabase credentials, making it accessible to those already in the n8n ecosystem but heavier to bootstrap for newcomers.
Compared to OpenClaw, n8nClaw trades standalone efficiency and a dedicated skill registry for visual transparency and reuse of n8n's integration library. It currently lacks official releases, security hardening, and community traction beyond its GitHub stars.