@n8n/instance-ai 1.12.2 → 1.12.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@n8n/instance-ai",
-  "version": "1.12.2",
+  "version": "1.12.4",
   "main": "dist/index.js",
   "module": "src/index.ts",
   "types": "dist/index.d.ts",
@@ -52,12 +52,12 @@
     "xlsx": "https://cdn.sheetjs.com/xlsx-0.20.2/xlsx-0.20.2.tgz",
     "zod": "3.25.67",
     "zod-from-json-schema-v3": "npm:zod-from-json-schema@^0.0.5",
-    "@n8n/agents": "0.12.1",
+    "@n8n/api-types": "1.27.2",
     "@n8n/mcp-browser": "0.10.0",
-    "@n8n/api-types": "1.27.0",
+    "@n8n/agents": "0.12.2",
     "@n8n/utils": "1.35.0",
-    "@n8n/workflow-sdk": "0.20.0",
-    "n8n-workflow": "2.27.0"
+    "@n8n/workflow-sdk": "0.20.2",
+    "n8n-workflow": "2.27.2"
   },
   "devDependencies": {
     "@ai-sdk/anthropic": "^3.0.81",
@@ -70,9 +70,9 @@
     "tsx": "^4.19.3",
     "vitest": "^4.1.1",
     "vitest-mock-extended": "^3.1.0",
-    "@n8n/ai-workflow-builder": "1.27.1",
-    "@n8n/typescript-config": "1.6.0",
-    "@n8n/vitest-config": "1.15.0"
+    "@n8n/ai-workflow-builder": "1.27.3",
+    "@n8n/vitest-config": "1.15.0",
+    "@n8n/typescript-config": "1.6.1"
   },
   "license": "SEE LICENSE IN LICENSE.md",
   "homepage": "https://n8n.io",

package/skills/workflow-builder/SKILL.md

@@ -175,7 +175,12 @@ effect-specific gating, list itemization, and Code-node safety.
    task's final deliverable.
 7. Trace wiring before declaring done. For IF, Switch, Merge, AI-agent, loop, or
    multi-workflow wiring, trace each branch from source to target. Confirm IF
-   outputs use `.onTrue()` and `.onFalse()`, Switch outputs use zero-based
+   branches are wired on the workflow builder (`.to(ifNode).onTrue(...).onFalse(...)`
+   or `.to(ifNode.onTrue(...).onFalse(...))`), not as standalone calls on the IF
+   node variable after `export default`. Confirm branch action nodes appear in the
+   saved graph — not just trigger → middle nodes → IF. Confirm the IF node has
+   connections on both outputs (true and false). For escalation flows, confirm
+   every requested side effect is on a wired branch. Switch outputs use zero-based
    `.onCase(index, target)`, Merge modes match the data shape, and sub-nodes are
    attached to the correct parent.
 8. Fix errors. If `build-workflow` returns errors, repair with targeted patches
@@ -376,6 +381,9 @@ column names.
   Code node, even when the user asks to fetch inside a Code node.
 
 - Use `@n8n/workflow-sdk`.
+- `export default workflow(...)...` must be the last statement in the file, with
+  all wiring composed inside that chain. Statements after it (e.g.
+  `ifNode.onTrue(...)`) do not reach the builder and their nodes are dropped.
 - Do not specify node positions. They are auto-calculated by the layout engine.
 - Use `expr('{{ $json.field }}')` for n8n expressions. Variables must be inside
   `{{ }}`. `$json` is only the current item from the immediate predecessor.
@@ -458,7 +466,8 @@ Follow these rules strictly when generating workflows:
      feeding the per-item work and looping back via `nextBatch`.
    - Drop items that do not match a predicate: `filter`.
    - Two mutually exclusive paths that both do real work: IF with `.onTrue()`
-     and `.onFalse()`.
+     and `.onFalse()` wired on the workflow builder — never as standalone
+     statements on the IF node variable.
    - Many mutually exclusive paths keyed off a value: Switch with
      `.onCase(index, target)`.
    - An outcome that must happen even when zero items remain: a node that
@@ -587,7 +596,11 @@ export default workflow('id', 'name')
   .to(processResults);
 ```
 
-For IF:
+For IF, each branch is a complete processing path. Wire branches on the workflow
+builder, not as standalone calls on the IF node variable. Chain steps inside a
+branch with `.to()`, or pass an array for parallel fan-out.
+Never call `.onFalse()` more than once (same for `.onTrue()`); each repeat
+overwrites the previous target.
 
 ```ts
 const isImportant = ifElse({
@@ -606,12 +619,29 @@ const isImportant = ifElse({
   },
 });
 
-source.to(isImportant);
-isImportant.onTrue(handleImportant);
-isImportant.onFalse(ignore);
+export default workflow('id', 'name')
+  .add(startTrigger)
+  .to(isImportant)
+  .onTrue(handleImportant)                               // single step
+  .onFalse(sendHolding.to(createTicket.to(alertSlack))); // chained multi-step
+// Equivalent inline form: .to(isImportant.onTrue(a).onFalse(b))
+// Parallel fan-out on a branch: .onFalse([a, b, c])
+```
+
+Do NOT wire branches as standalone statements.
+Then branch nodes are omitted from the saved graph, and repeated `.onFalse()`
+calls keep only the last target.
+
+```ts
+// WRONG
+export default workflow('id', 'name').add(startTrigger).to(isImportant);
+isImportant.onTrue(handleImportant); // never reaches the builder
+isImportant.onFalse(sendHolding);    // overwritten
+isImportant.onFalse(alertSlack);     // only this one would wire
 ```
 
-For Switch, use zero-based `.onCase(index, target)` for each rule output.
+For Switch, wire cases the same way — `.to(switchNode).onCase(0, a).onCase(1, b)`
+or inline — using zero-based `.onCase(index, target)` for each rule output.
 
 For Split in Batches, use it for per-item side effects and loop back with
 `nextBatch`. Do not add a separate IF gate just to check whether items exist.