admin/n8n-enterprise-unlocked
1
0
Fork 0
mirror of https://github.com/Abdulazizzn/n8n-enterprise-unlocked.git synced 2025-12-16 17:46:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: includeOtherFields parameter of Workflow Configuration node (no-changelog) (#19149)

Browse Source
This commit is contained in:
Eugene
2025-09-05 08:53:12 +03:00
committed by GitHub
parent 59684039ee
commit 3175650a7a
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
packages/@n8n/ai-workflow-builder.ee/evaluations/chains/workflow-evaluator.ts
View File

@@ -121,7 +121,7 @@ Evaluate whether expressions correctly reference nodes and data using modern n8n
**Check for these violations:** **Check for these violations:**
- **Critical (-40 to -50 points)**: - **Critical (-40 to -50 points)**:
- Invalid JavaScript syntax that would cause runtime errors (unclosed brackets, syntax errors, malformed JSON) - Invalid JavaScript syntax that would cause runtime errors (unclosed brackets, syntax errors, malformed JSON)
- Referencing truly non-existent nodes or fields that would cause runtime errors - Referencing truly non-existent nodes or fields that would cause runtime errors (e.g. fields of the nodes that should be executed later in the flow)
- **Major (-20 to -25 points)**: - **Major (-20 to -25 points)**:
- Missing required = prefix for expressions (e.g., \`{{ $json.name }}\` instead of \`={{ $json.name }}\`) - Missing required = prefix for expressions (e.g., \`{{ $json.name }}\` instead of \`={{ $json.name }}\`)
- Using $fromAI in non-tool nodes (would cause runtime error) - Using $fromAI in non-tool nodes (would cause runtime error)

2
packages/@n8n/ai-workflow-builder.ee/src/tools/prompts/main-agent.prompt.ts
View File

@@ -201,7 +201,7 @@ Workflow configuration node usage example:
IMPORTANT: IMPORTANT:
- Workflow Configuration node is not meant for credentials or sensitive data. - Workflow Configuration node is not meant for credentials or sensitive data.
- Workflow Configuration node should always include parameter "includeOtherFields": true, to pass through any trigger data. - Always enable "includeOtherFields" setting of the Workflow Configuration node, to pass to the output all the input fields (this is a top level parameter, do not add it to the fields in 'Fields to Set' parameter).
- Do not reference the variables from the Workflow Configuration node in Trigger nodes (as they run before it). - Do not reference the variables from the Workflow Configuration node in Trigger nodes (as they run before it).
Why: Centralizes configuration, makes workflows maintainable, enables easy environment switching, and provides clear parameter visibility. Why: Centralizes configuration, makes workflows maintainable, enables easy environment switching, and provides clear parameter visibility.