Index / n8nClaw · updated Aug 17, 2026

n8nClaw

shabbirun/n8nclaw · warning · rank 35 of 43 by stars

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.

#n8n#openclaw-clone#no-code#multi-channel#self-hosted
Compare vs OpenClaw
GitHub ↗

Facts

Repository

Contributors2
Open issues0
Last commitFeb 10, 2026

Runtime

LanguageJSON
Memory80 MB
Boot time150 ms
Deploymentself-hosted · cloud
Setup difficultyMedium
Plugin ecosystemLimited

Posture

Local-firstNo
Cloud dependencyRequired
Multi-userYes
Privacy postureMixed

Security breakdown

Composite 30 / 100 · how these are scored

Sandboxing2 / 10

higher is safer

API security4 / 10

higher is safer

Network isolation3 / 10

higher is safer

Telemetry safety5 / 10

higher is safer

Shell access risk2 / 10

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

  • Visual workflow editing in n8n lowers coding barrier
  • Leverages existing n8n integrations for channels
  • Easy to audit logic as flowchart rather than code

Tradeoffs

  • No compiled binary; requires running n8n stack
  • Less secure isolation than containerized alternatives
  • No plugin/skill ecosystem like OpenClaw

Best fit

  • No-code enthusiasts wanting OpenClaw-like assistant
  • Self-hosters already running n8n
  • Teams needing multi-channel (Telegram/WhatsApp/Gmail) bots

Avoid if

  • Users wanting compiled binary or low-memory edge deploy
  • Those needing strong sandboxing/security defaults
  • Projects requiring official releases/long-term support
Low Confidence30%

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 layer reviewed Aug 2, 2026 · how this is written

Star activity

227 stars today

Overview

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.

Nominate a clone

Add a new Claw

Paste a GitHub repository and tell us why it belongs on the tracker.

Opens a prefilled issue on GitHub — every nomination is public. Comfortable with a PR? Adding the repo to projects.json is faster.