Index / n8nClaw · updated Sep 3, 2026
n8nClaw
shabbirun/n8nclaw · warning · rank 35 of 43 by stars
A lightweight OpenClaw-inspired assistant built entirely as a single n8n visual workflow, with Telegram, WhatsApp, and Gmail channels plus tiered worker sub-agents. It trades code for drag-and-drop automation, leaning on Claude Sonnet 4.5 via OpenRouter and Supabase vector memory.
Facts
Repository
Runtime
Posture
Community
Security breakdown
Composite 45 / 100 · how these are scored
higher is safer
higher is safer
higher is safer
higher is safer
higher is riskier
Model access
Read from the repository, not written by a model · 1 files examined
No provider wiring was found in this repository. That is not the same as the project supporting none — it usually means the model call lives somewhere the detector does not read, such as an exported workflow or a binary dependency.
Decision
Why choose n8nClaw over OpenClaw?
Why choose this
- No-code visual workflow makes customization accessible to non-developers
- Single-file n8n workflow is easy to import and inspect
- Built-in multi-channel triggers (Telegram, WhatsApp, Gmail) via n8n nodes
Tradeoffs
- Depends on external services (OpenRouter, Supabase, Evolution API) rather than local-first
- No sandboxing or security hardening comparable to OpenClaw's ecosystem
- Very young project with only initial commits and no releases
Best fit
- n8n users who want an OpenClaw-style assistant without writing code
- Self-hosters who prefer visual, editable workflows
- Tinkerers wanting multi-channel messaging with minimal setup
Avoid if
- You need strong sandboxing or hardened security controls
- You want a mature plugin ecosystem or active community
- You need production-grade reliability and official releases
Evidence is limited to the README, a handful of initial commits, and zero Reddit mentions; web results are mostly about other OpenClaw clones. Assessments of security, stability, and community traction carry high uncertainty.
AI layer reviewed Aug 24, 2026 · how this is written
Star activity
228 stars today
Overview
n8nClaw reimagines OpenClaw as a single, self-hosted n8n workflow rather than a traditional codebase. It wires together Telegram, WhatsApp (via Evolution API), Gmail polling, and an hourly heartbeat trigger into a central AI agent node powered by Claude Sonnet 4.5 through OpenRouter, with Postgres-backed chat memory holding a 15-message context window.
The architecture includes tiered worker sub-agents, task and subtask databases, a configurable 'soul' personality field, and a scheduled memory pipeline that aggregates chat history, summarizes it with Haiku 4.5, embeds it via OpenAI, and stores it in a Supabase vector database for long-term RAG. Replies are routed back through the originating channel via a switch on the normalized message context.
Compared to OpenClaw, n8nClaw sacrifices local-first operation, sandboxing, and a mature skill ecosystem in exchange for approachability: everything is a visual, editable workflow that non-developers can import and modify. However, the project is extremely young — only initial commits exist, there are no official releases, and there is no measurable community discussion yet, so production readiness is unproven.