@n8n-as-code/n8nac 2.2.1 → 2.3.0-rc.1

package/index.ts

@@ -2,7 +2,7 @@ import { accessSync, constants, mkdirSync } from "node:fs";
 import { join } from "node:path";
 import { N8N_FACADE_SETUP_MODES } from "@n8n-as-code/workflow-core";
 import { createTelemetryClient } from "@n8n-as-code/telemetry";
-import type { OpenClawPluginApi } from "openclaw/plugin-sdk";
+import type { OpenClawPluginApi } from "openclaw/plugin-sdk/core";
 import { registerN8nAcCli } from "./src/cli.js";
 import { getWorkspaceDir, isWorkspaceInitialized, readWorkspaceBinding } from "./src/workspace.js";
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@n8n-as-code/n8nac",
-  "version": "2.2.1",
+  "version": "2.3.0-rc.1",
   "description": "OpenClaw plugin for n8n-as-code — create and manage n8n workflows from OpenClaw",
   "keywords": [
     "n8n",
@@ -25,11 +25,11 @@
   },
   "dependencies": {
     "@n8n-as-code/telemetry": "2.0.1",
-    "@n8n-as-code/workflow-core": "2.0.0"
+    "@n8n-as-code/workflow-core": "2.0.1-rc.1"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",
-    "openclaw": "^2026.2.26",
+    "openclaw": "2026.8.2",
     "typescript": "^5.8.0",
     "vitest": "^1.6.1"
   },

package/skills/n8n-architect/SKILL.md

@@ -168,6 +168,7 @@ npx --yes n8nac push <path-to-workflow.workflow.ts> --verify
 ```
 
 - `push` requires the full workflow file path, either absolute or context-root-relative. Do not pass a bare filename.
+- On n8n 2.x, pushing to a **published** workflow also releases it to production — the API re-publishes on update. Treat every push to a published workflow as a deploy. Use `push --draft` when the user wants to check the change in n8n first: it re-pins the previously published version so production keeps running what it already ran.
 - For a new workflow, create the file inside the `workflowsPath` returned by `env status --json`, then confirm it with `npx --yes n8nac list --local`.
 - If push/pull reports a conflict, use explicit resolution commands. Do not overwrite remote changes blindly.
 - `pull` and conflict resolution operate on a single workflow ID.
@@ -265,6 +266,7 @@ npx --yes n8nac skills examples download <id>
 - AI sub-nodes connect with `.uses()`, never `.out().to()`.
 - `ai_tool` and `ai_document` connections are arrays: `ai_tool: [this.Tool.output]`.
 - Other AI connection types are single refs, such as `ai_languageModel: this.Model.output`.
+- They also accept an array when a node exposes several inputs of the same type, where the position is the input index: `ai_languageModel: [this.Model.output, this.FallbackModel.output]` (fallback model, Model Selector).
 - Check `node-info` for connection-dependent boolean flags before declaring `.uses()` connections.
 
 Every `.workflow.ts` file starts with a `<workflow-map>` block. Read that map first, locate the property name you need, then read only the relevant class section.
@@ -371,8 +373,9 @@ defineRouting() {
 
 - Use `.uses()` for language models, memory, tools, parsers, embeddings, vector stores, retrievers, and other AI sub-nodes.
 - Never connect AI sub-nodes with `.out().to()`.
-- `ai_tool` and `ai_document` must be arrays.
-- Most other AI connection types are single refs.
+- `ai_tool` and `ai_document` must be arrays; every entry lands on input index 0.
+- Most other AI connection types are single refs, or an array when the node exposes several inputs of the same type — position = input index.
+- `needsFallback: true` (Agent, Basic LLM Chain) needs a second model on input 1: `ai_languageModel: [this.Model.output, this.FallbackModel.output]`. Same for the Model Selector node.
 - Some nodes require boolean flags to expose AI ports or gated parameters. Check `node-info` before declaring `.uses()`.
 
 ## Common Mistakes To Avoid

package/src/cli.ts

@@ -1,4 +1,4 @@
-import type { OpenClawPluginApi } from "openclaw/plugin-sdk";
+import type { OpenClawPluginApi } from "openclaw/plugin-sdk/core";
 import type { TelemetryClient } from "@n8n-as-code/telemetry";
 import { isWorkspaceInitialized } from "./workspace.js";