@elizaos/plugin-n8n-workflow 1.1.0 → 1.2.1

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.
package/README.md CHANGED
@@ -904,8 +904,9 @@ src/
904
904
  scripts/
905
905
  ├── crawl.ts # Master crawl (runs all 3 steps below)
906
906
  ├── crawl-nodes.ts # Step 1: Extract node defs from n8n-nodes-base
907
- ├── crawl-schemas.ts # Step 2: Extract output schemas from __schema__/ dirs
908
- └── capture-trigger-schemas.ts # Step 3: Capture trigger schemas from live n8n
907
+ ├── crawl-output-schemas.ts # Step 2: Extract output schemas from __schema__/ dirs
908
+ ├── crawl-triggers-live.ts # Step 3: Capture trigger schemas from live n8n
909
+ └── crawl-triggers-static.ts # Alternative: Extract trigger schemas from code + OpenAPI specs
909
910
  ```
910
911
 
911
912
  ---
@@ -921,8 +922,8 @@ Runs three steps:
921
922
  | Step | Script | Generates | Requires |
922
923
  |------|--------|-----------|----------|
923
924
  | 1/3 | `crawl-nodes.ts` | `defaultNodes.json` — 457 node definitions with parameters, versions, credentials | n8n-nodes-base package |
924
- | 2/3 | `crawl-schemas.ts` | `schemaIndex.json` — output schemas per node/resource/operation | n8n-nodes-base `__schema__/` dirs + langchain overrides |
925
- | 3/3 | `capture-trigger-schemas.ts` | `triggerSchemaIndex.json` — trigger output schemas | `N8N_HOST` + `N8N_API_KEY` env vars |
925
+ | 2/3 | `crawl-output-schemas.ts` | `schemaIndex.json` — output schemas per node/resource/operation | n8n-nodes-base `__schema__/` dirs + langchain overrides |
926
+ | 3/3 | `crawl-triggers-live.ts` | `triggerSchemaIndex.json` — trigger output schemas | `N8N_HOST` + `N8N_API_KEY` env vars |
926
927
 
927
928
  **Step 3 is skipped** if `N8N_HOST` / `N8N_API_KEY` are not set (a warning is printed).
928
929
 
@@ -932,7 +933,7 @@ The LLM receives output schemas during workflow generation to prevent hallucinat
932
933
 
933
934
  - **n8n-nodes-base nodes**: Schemas are crawled from `__schema__/` directories in the npm package
934
935
  - **@n8n/n8n-nodes-langchain nodes**: No `__schema__/` dirs exist — schemas are defined in `src/data/langchain-output-schemas.json` and merged at crawl time
935
- - **Trigger nodes**: Schemas are captured from real n8n executions via `capture-trigger-schemas.ts`
936
+ - **Trigger nodes**: Schemas are captured from real n8n executions via `crawl-triggers-live.ts`
936
937
 
937
938
  The generation prompt includes output schemas for all relevant nodes, so the LLM uses correct field paths like `$json.output[0].content[0].text` instead of inventing wrong ones like `$json.choices[0].message.content`.
938
939