What makes N8N EVOL I notable?

962 downloads. Trust evidence available

How should N8N EVOL I be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

N8N EVOL I

A harness to help coding agents build, deploy, maintain, and debug multi-workflow n8n-powered automation systems. No lock-in — work from the agent, continue... Skill: N8N EVOL I Owner: mwamedacen Summary: A harness to help coding agents build, deploy, maintain, and debug multi-workflow n8n-powered automation systems. No lock-in — work from the agent, continue... Tags: latest:2.0.0 Version history: v2.0.0 | 2026-05-25T22:16:50.188Z | user Queue primitives and lifecycle support added + breaking change on interpolation syntax - Introduced primitives and helper scripts to suppo

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

962

Updated

Oct 12, 2026

Version

2.0.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 962 downloads reported by the source. Last updated 10/12/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 12, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 12, 2026
Adoption signal: 962 downloadsadoption · observed Oct 12, 2026
Latest release: 2.0.0release · observed May 25, 2026
Handshake status: UNKNOWNsecurity

What changed

Newest first. Only changes that point at a source are listed.

Release 2.0.0release
Queue primitives and lifecycle support added + breaking change on interpolation syntax - Introduced primitives and helper scripts to support queue-based workflows (using Redis Streams). - Added lifecycle skills for queue creation, publishing, and consumption: `create-queue`, `add-queue-publish-to-workflow`, `add-queue-consumer-to-workflow`. - Added reference docs: patterns/queues and integrations/redis/queue-pattern. - Included primitive workflow templates for queue ack, publish, pop, sample producer/consumer, and error handler queue cleanup. - New lifecycle skill: `manage-variables` for n8n runtime variables. - Updated main skill index to list and describe new queue-related features.
Observed May 25, 2026 · source

Install and run

Setup complexity: low.

clawhub skill install s1796g7dypaz4std6t3senhtn5860gse:n8n-evol-i

Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-mwamedacen-n8n-evol-i/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

152,792 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: n8n-evol-I
description: A harness to help coding agents build, deploy, maintain, and debug multi-workflow n8n-powered automation systems. No lock-in — work from the agent, continue from the n8n UI, hand back to the agent at any time.
---

# n8n-evol-I skill router

This is the entry point. When the user asks anything n8n-related, route to the matching sub-skill.

## Mental model

- The skill package (this directory) is **read-only**. You never edit files here.
- The user's project state lives in `${PWD}/n8n-evol-I-workspace/` (created by `init.md`).
- Helpers are Python scripts under `helpers/`. Invoke them with `python3 ${CLAUDE_PLUGIN_ROOT}/helpers/<name>.py [args]` (plugin mode) or `python3 <path-to-harness>/helpers/<name>.py [args]` (skill mode).
- All helpers default to `--workspace ${PWD}/n8n-evol-I-workspace`. Pass `--workspace <path>` if the user runs from elsewhere.
- **Agent memory**: read `N8N-WORKSPACE-MEMORY.md` in the workspace at the start of every session; append a dated entry whenever you learn something durable about this project. Full guidance in `AGENTS.md` (also in the workspace root).

## Lifecycle skills (use when the user wants to do X)

| Skill | When |
|---|---|
| [init.md](skills/init.md) | First-time setup. Creates the workspace at `${PWD}/n8n-evol-I-workspace/`. |
| [bootstrap-env.md](skills/bootstrap-env.md) | Configure an environment (`dev` / `staging` / `prod`). Creates env YAML + `.env`, validates, mints placeholder workflow IDs. |
| [doctor.md](skills/doctor.md) | Health check. Run before/after major changes. |
| [create-new-workflow.md](skills/create-new-workflow.md) | Author a brand-new workflow. |
| [register-workflow-to-error-handler.md](skills/register-workflow-to-error-handler.md) | Wire `settings.errorWorkflow`. |
| [create-lock.md](skills/create-lock.md) | First-time setup for distributed locking (Redis-backed primitives). |
| [copy-primitive.md](skills/copy-primitive.md) | Copy a single primitive (any) into the workspace. General-purpose; doesn't register. |
| [add-lock-to-workflow.md](skills/add-lock-to-workflow.md) | Wrap a workflow's main flow in lock acquire/release. |
| [add-rate-limit-to-workflow.md](skills/add-rate-limit-to-workflow.md) | Gate a workflow's main flow with a Redis-backed fixed-window rate-limit check. |
| [create-queue.md](skills/create-queue.md) | First-time setup for queue primitive (Redis Streams + atomic-INCR semaphore). |
| [add-queue-publish-to-workflow.md](skills/add-queue-publish-to-workflow.md) | Wrap a workflow with a producer-side XADD call. |
| [add-queue-consumer-to-workflow.md](skills/add-queue-consumer-to-workflow.md) | Turn a workflow into a schedule-polled queue consumer with bounded concurrency. |
| [tidy-workflow.md](skills/tidy-workflow.md) | Apply n8n's canvas-layout algorithm to a workflow template to clean up node positions. |
| [deploy.md](skills/deploy.md) | Deploy one workflow to one env. |
| [activate-single-workflow-in-env.md](skills/activate-si

README.md

<img width="1376" height="768" alt="n8n_evol_I_hero" src="https://github.com/user-attachments/assets/0a28f1f6-106f-4f84-9ce1-cf7eebcf4cd6" />

# N8N EVOL I

A harness to help coding agents build, deploy, maintain, and debug multi-workflow n8n-powered automation systems.

No lock-in. Build with your agent and push upstream to n8n; tweak directly in the n8n UI and pull downstream back into your workspace. Round-trips are template-stable, so humans and agents can work the same project in parallel without stepping on each other's edits.

```mermaid
flowchart LR
    Agent <-->|edits / resync| Workspace
    Workspace <-->|deploy / resync| n8n[(n8n instance)]
    n8n <-->|UI edits| Human
```

## Features

- **Multi-environment workflows.** Per-env YAML in `n8n-config/<env>.yml` (instance URL, workflow IDs, credential refs); every helper accepts `--env`. See [`bootstrap-env.md`](skills/bootstrap-env.md).

  ```yaml
  # n8n-config/dev.yml
  instance: acme.dev.n8n.cloud
  envSuffix: " (dev)"          # appended to every workflow name
  workflows:
    lead_enrichment:
      id: wf_def456
      displayName: "Lead Enrichment"
    lead_persister:
      id: wf_abc123
      displayName: "Lead Persister"
  ```

- **Build-time substitution.** Code, prompts, schemas, templates, and env values live in workspace files; `{{@js|py|txt|json|html|env|uuid:...}}` placeholders are substituted at deploy time. Template-stable round-trips. See [`code-node-discipline.md`](skills/patterns/code-node-discipline.md).

  ```jsonc
  // n8n-workflows-template/lead_enrichment.template.json
  {
    "name": "{{@env:workflows.lead_enrichment.displayName}}{{@env:envSuffix}}",
    "nodes": [
      {
        "name": "Webhook",
        "type": "n8n-nodes-base.webhook",
        "parameters": { "path": "lead", "httpMethod": "POST" }
      },
      {
        "name": "Score Lead",
        "type": "@n8n/n8n-nodes-langchain.openAi",
        "parameters": {
          "messages": [
            { "role": "system", "content": "{{@txt:n8n-prompts/prompts/score_lead.txt}}" }
          ]
        }
      },
      {
        "name": "Normalize Fields",
        "type": "n8n-nodes-base.code",
        "parameters": {
          "jsCode": "{{@js:n8n-functions/js/normalize_lead.js}}\n\nreturn normalize(items);"
        }
      },
      {
        "name": "Persist via Sub-workflow",
        "type": "n8n-nodes-base.executeWorkflow",
        "parameters": {
          "workflowId": "{{@env:workflows.lead_persister.id}}"
        }
      }
    ]
  }
  ```

- **Dependency-ordered deployment.** `deploy_all.py` rolls out an env in tier order (set per-workflow in `deployment_order.yml`) so callees deploy before callers. See [`deploy_all.md`](skills/deploy_all.md).

  ```mermaid
  graph LR
    A[tier 0: leaves] --> B[tier 1: handlers] --> C[tier 2: callers]
  ```

- **Execution debugging.** Structured symptom → root-cause flow (dependency graph, candidate pre-screen, causal-linkage, sub-agent cross-check), backed by `list_ex

skills/integrations/airtable/README.md

---
name: integration-airtable
description: Airtable nodes — PAT credential, base / table IDs.
user-invocable: false
---

# Airtable

## Node type

`n8n-nodes-base.airtable`.

## Credential type

`airtableTokenApi` — Personal Access Token (PAT) from `airtable.com/create/tokens`.

For setup, see [`skills/manage-credentials.md`](../../manage-credentials.md). Scopes minimum: `data.records:read` and (if writing) `data.records:write`. Each token can be limited to specific bases — granular tokens are best practice.

## Base + table IDs

Airtable URLs: `https://airtable.com/<baseId>/<tableId>/<viewId>`. The n8n Airtable node takes `base` (= `baseId`) and `table` (= `tableId` or table name).

Store in env YAML:

```yaml
airtable:
  ordersBase: "appabc..."
  ordersTable: "tblxyz..."
```

## Field-name vs field-id

Records returned by the API use field NAMES by default. The Airtable node also supports `returnFieldsByFieldId: true` if your field names change frequently — this returns IDs instead and is more stable.

skills/integrations/datadog/README.md

---
name: integration-datadog
description: Datadog as the audit destination for n8n error handlers — events POST via HTTP Request, region selection, tag conventions for aggregation.
user-invocable: false
---

# Datadog

## Node type

`n8n-nodes-base.httpRequest`. There is no dedicated `n8n-nodes-base.datadog` node — Datadog is HTTP-shaped.

## Credential type

`httpHeaderAuth` with header `DD-API-KEY: <api_key>`. Get the key from Datadog → Organization Settings → API Keys.

For most error-handling use cases the API key alone is sufficient. The Application Key (`DD-APPLICATION-KEY`) is only required for endpoints that read data on your behalf (querying logs, dashboards, etc.) — POSTing events doesn't need it.

Store as `.env.<env>`:

```bash
# .env.<env>
DD_API_KEY=<your-key>
```

Resolve via `{{@env:credentials.datadog.id}}` / `{{@env:credentials.datadog.name}}` after running `manage-credentials` to register the n8n credential. See [`skills/manage-credentials.md`](../../manage-credentials.md).

## Endpoint

Errors as **events** (recommended for human-readable incident streams):
```
POST https://api.datadoghq.com/api/v1/events
```

Errors as **logs** (alternative — better when you want full-text search across high-volume errors):
```
POST https://api.datadoghq.com/api/v2/logs
```

The events endpoint shows up in Datadog's Event Stream and can drive monitor alerts directly. The logs endpoint shows up in Log Explorer and indexes the body for full-text search. Pick events if your error volume is low (incidents, not noise); pick logs if you want every error retained and queryable.

### Region selection

Datadog hosts per region. The endpoint changes accordingly:

| Region | Base URL |
|---|---|
| US1 (default) | `https://api.datadoghq.com` |
| US3 | `https://api.us3.datadoghq.com` |
| US5 | `https://api.us5.datadoghq.com` |
| EU1 | `https://api.datadoghq.eu` |
| AP1 | `https://api.ap1.datadoghq.com` |
| US-Gov | `https://api.ddog-gov.com` |

Make region env-configurable so a single template runs in EU staging + US prod:

```yaml
# n8n-config/<env>.yml
datadog:
  endpoint: "https://api.datadoghq.com"
  apiKeyEnv: "DD_API_KEY"
```

Then `={{ $env.DD_ENDPOINT || 'https://api.datadoghq.com' }}` in the URL field, or use a `{{@env:datadog.endpoint}}` placeholder.

## Worked example: HTTP Request POST event

Inside an n8n error handler, fed by the `Build Context` Code node from [`patterns/error-handling.md`](../../patterns/error-handling.md):

```json
{
  "type": "n8n-nodes-base.httpRequest",
  "typeVersion": 4.2,
  "parameters": {
    "method": "POST",
    "url": "={{ ($env.DD_ENDPOINT || 'https://api.datadoghq.com') + '/api/v1/events' }}",
    "authentication": "genericCredentialType",
    "genericAuthType": "httpHeaderAuth",
    "sendHeaders": true,
    "headerParameters": {
      "parameters": [
        { "name": "Accept", "value": "application/json" },
        { "name": "Content-Type", "value": "application/json" }
      ]
    },
    "sendBody": true,

skills/integrations/google-drive/README.md

---
name: integration-google-drive
description: Google Drive + Sheets nodes. OAuth scopes, folder-vs-file IDs.
user-invocable: false
---

# Google Drive (and Sheets)

## Node types

- `n8n-nodes-base.googleDrive` — file ops on Drive.
- `n8n-nodes-base.googleSheets` — Sheets read/write.

## Credential type

`googleApi` (single credential covers Drive + Sheets if scopes include both).

For setup, see [`skills/manage-credentials.md`](../../manage-credentials.md). OAuth scopes minimum:

- Drive: `https://www.googleapis.com/auth/drive`
- Sheets: `https://www.googleapis.com/auth/spreadsheets`

## File / folder IDs

A Drive URL `https://drive.google.com/drive/folders/<ID>` gives the folder ID. A Sheets URL `https://docs.google.com/spreadsheets/d/<ID>/edit` gives the spreadsheet ID.

Store IDs in env YAML:

```yaml
gdrive:
  reportsFolder: "1abc..."
  weeklyReport: "1xyz..."  # spreadsheet
```

## App verification

Using sensitive scopes (full Drive access, etc.) requires Google's app verification for production-tier apps. For internal-team-only projects, configure the OAuth client as "internal" within a Workspace org to bypass verification.

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.

MCPOPENCLAW

Github ReposUpdated 7mo agoRank 70

CopilotKit

The Frontend for Agents & Generative UI. React + Angular