@n8n-as-code/n8nac 2.1.0 → 2.1.1-next.22

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/package.json +1 -1
  2. package/skills/n8n-architect/SKILL.md +6 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@n8n-as-code/n8nac",
3
- "version": "2.1.0",
3
+ "version": "2.1.1-next.22",
4
4
  "description": "OpenClaw plugin for n8n-as-code — create and manage n8n workflows from OpenClaw",
5
5
  "keywords": [
6
6
  "n8n",
package/skills/n8n-architect/SKILL.md CHANGED
@@ -24,7 +24,8 @@ Use `npx --yes n8nac` as the primary interface. Use `npx --yes @n8n-as-code/n8n-
24
24
  npx --yes n8nac env status --json
25
25
  ```
26
26
 
27
- - Use the returned `workflowDir` for workflow files. Do not reconstruct it from `syncFolder`, `instanceIdentifier`, or `projectName`.
27
+ - Use the returned `workflowDir` for workflow files. Treat it as an opaque backend-derived path that may contain generated or hashed segments.
28
+ - `syncFolder` is only the user-configured sync root, not the workflow directory. Do not reconstruct `workflowDir` from `syncFolder`, environment name/id, `instanceIdentifier`, `instanceUserIdentifier`, `projectId`, or `projectName`.
28
29
  - Never write `n8nac-config.json`, `~/.n8n-manager`, or n8n-manager secret files by hand.
29
30
 
30
31
  ## Workspace Readiness
@@ -81,7 +82,7 @@ npx --yes n8nac env status --json
81
82
  10. Configure the environment with:
82
83
 
83
84
  ```bash
84
- npx --yes n8nac env add <name> --base-url <url> --sync-folder workflows/<name>
85
+ npx --yes n8nac env add <name> --base-url <url> --sync-folder workflows
85
86
  npx --yes n8nac env auth set <name> --api-key-stdin
86
87
  npx --yes n8nac env use <name>
87
88
  ```
@@ -89,7 +90,7 @@ npx --yes n8nac env use <name>
89
90
  For a managed local instance:
90
91
 
91
92
  ```bash
92
- npx --yes n8nac env add Local --managed-instance <id> --sync-folder workflows/local
93
+ npx --yes n8nac env add Local --managed-instance <id> --sync-folder workflows
93
94
  npx --yes n8nac env use Local
94
95
  ```
95
96
 
@@ -102,7 +103,7 @@ Use `npx --yes n8nac env ...` for workspace environments, remote URLs, active en
102
103
  ```bash
103
104
  npx --yes n8nac env status --json
104
105
  npx --yes n8nac env list
105
- npx --yes n8nac env add <name> --base-url <url> --sync-folder workflows/<name>
106
+ npx --yes n8nac env add <name> --base-url <url> --sync-folder workflows
106
107
  npx --yes n8nac env auth set <name> --api-key-stdin
107
108
  npx --yes n8nac env use <name>
108
109
  ```
@@ -116,7 +117,7 @@ npx --yes n8nac env use <name>
116
117
  Attach a managed local instance to the workspace with `npx --yes n8nac env ...`:
117
118
 
118
119
  ```bash
119
- npx --yes n8nac env add Local --managed-instance <id> --sync-folder workflows/local
120
+ npx --yes n8nac env add Local --managed-instance <id> --sync-folder workflows
120
121
  npx --yes n8nac env use Local
121
122
  ```
122
123