@n8n-as-code/n8nac 2.0.0 → 2.0.1-next.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +4 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -8,6 +8,8 @@ Use OpenClaw to build, update, validate, and manage n8n workflows with the same
8
8
 
9
9
  Version 2 removes the facade-specific OpenClaw runtime tool path. The plugin now delegates instance, auth, project, tunnel, credential, and presentation operations to `n8n-manager`, while workspace sync context is stored through `n8nac workspace` in `~/.openclaw/n8nac/`.
10
10
 
11
+ Documentation: [OpenClaw guide](https://n8nascode.dev/docs/usage/openclaw/) · [n8n-manager guide](https://n8nascode.dev/docs/usage/n8n-manager/) · [CLI workspace commands](https://n8nascode.dev/docs/usage/cli/#workspace)
12
+
11
13
  ## Install
12
14
 
13
15
  ```bash
@@ -71,6 +73,8 @@ All files live in `~/.openclaw/n8nac/`:
71
73
  Instances and API keys are not stored in this workspace. They live in the global
72
74
  `n8n-manager` configuration under `~/.n8n-manager`.
73
75
 
76
+ To pin this workspace to one global instance, run `n8n-manager instances list`, then `n8nac workspace pin-instance --instance-id <instanceId>` from `~/.openclaw/n8nac/` or through the agent skill shell.
77
+
74
78
  ## Agent skills
75
79
 
76
80
  The plugin does not register a facade-specific agent tool. Agents should use
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@n8n-as-code/n8nac",
3
- "version": "2.0.0",
3
+ "version": "2.0.1-next.10",
4
4
  "description": "OpenClaw plugin for n8n-as-code — create and manage n8n workflows from OpenClaw",
5
5
  "keywords": [
6
6
  "n8n",