Index / n8nClaw · updated Oct 2, 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 agents. It trades code for drag-and-drop automation, making it approachable for no-code tinkerers.

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

Facts

Repository

Contributors2
Open issues1
Last commitFeb 10, 2026

Runtime

Languagen8n Workflow (JSON)
Memory150 MB
Boot time300 ms
Deploymentself-hosted · cloud
Setup difficultyMedium
Plugin ecosystemEmerging

Posture

Local-firstNo
Cloud dependencyRequired
Multi-userYes
Privacy postureMixed

Community

Sentiment40% positive
Reddit mentions0
Web results10

Security breakdown

Composite 45 / 100 · how these are scored

Sandboxing3 / 10

higher is safer

API security4 / 10

higher is safer

Network isolation4 / 10

higher is safer

Telemetry safety5 / 10

higher is safer

Shell access risk5 / 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

  • No-code visual workflow is easier to inspect and modify than a codebase
  • Leverages n8n's large integration ecosystem out of the box
  • Single-file workflow export makes setup conceptually simple

Tradeoffs

  • Depends on many external services (OpenRouter, Supabase, Evolution API, Postgres)
  • Only initial commits; no releases, tests, or ongoing maintenance signal
  • No sandboxing or security architecture compared to OpenClaw

Best fit

  • n8n users wanting a ready-made AI assistant workflow
  • No-code builders who prefer visual automation over writing code
  • Self-hosters wanting Telegram/WhatsApp/Gmail agent channels quickly

Avoid if

  • You need a production-grade, actively maintained codebase
  • You want strong sandboxing or security guarantees
  • You don't already run n8n, Postgres, and Supabase infrastructure
Mixed Evidence35%

Evidence is limited to the README and two initial commits; there are no releases, no Reddit discussion, and web mentions are about OpenClaw generally rather than this project. Assessments of security, stability, and community traction are therefore low-confidence.

AI layer reviewed Sep 21, 2026 · how this is written

Star activity

230 stars today

Overview

Overview

n8nClaw is a lightweight reimagining of OpenClaw built entirely as an n8n visual workflow rather than a traditional codebase. It wires together Telegram, WhatsApp (via Evolution API), Gmail, and an hourly heartbeat trigger into a central AI agent powered by Claude Sonnet 4.5 through OpenRouter, with Postgres-backed chat memory (15-message window) and a configurable 'soul' personality field.

The architecture includes tiered sub-agents (research, email, document management, generic workers), task and subtask databases, 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 RAG. This gives it persistent long-term memory and autonomous task processing similar in spirit to OpenClaw.

The key trade-off versus OpenClaw is approachability versus robustness: everything is editable in n8n's drag-and-drop canvas, but the project depends on a stack of external services (n8n, Postgres, Supabase, OpenRouter, Evolution API), has no releases or tests, and consists of only initial commits. It is best viewed as an interesting starter template for no-code builders rather than a mature OpenClaw alternative.

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.