You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix: forward workflow settings outside the typed create schema (v2.74.1)
n8n_create_workflow declared settings as a closed z.object, so keys such as
availableInMCP, callerPolicy and timeSavedPerExecution were stripped before
the payload reached the API client, while updateSettings forwarded them.
The typed keys stay validated; everything else now passes through, as on the
update path. Tool schema and docs mention availableInMCP.
Fixesczlonkowski#1026
Conceived by Romuald Członkowski - www.aiadvisors.pl/en
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5E2LQVUpMQDBDueBzieGp
* test: give the second memory node its own id in the multiple-memory fixture
n8n 2.36 rejects a workflow whose nodes share an id, so the live
integration test "should validate memory connections" has failed on main
since the 2.36 update. The helper defaults every memory node to
'memory-1'; the second one now gets 'memory-2'.
Conceived by Romuald Członkowski - www.aiadvisors.pl/en
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5E2LQVUpMQDBDueBzieGp
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## [Unreleased]
9
9
10
+
## [2.74.1] - 2026-08-27
11
+
12
+
### Fixed
13
+
14
+
-**`n8n_create_workflow` silently dropped workflow settings outside its own list** (#1026). The create input schema was a closed object with eight settings keys, so `availableInMCP`, `callerPolicy`, `callerIds`, `timeSavedPerExecution`, `customTelemetryTags`, `redactionPolicy` and `timeSavedMode` were stripped before the payload reached the API client. A workflow created with `settings.availableInMCP: true` therefore never appeared in n8n's instance-level MCP server, while the same key set through `updateSettings` worked. The typed keys are still validated; every other key is now forwarded, as on the update path; the create cleaner still drops the derived properties n8n ignores on write. The tool schema and documentation now mention `availableInMCP`.
settings: {type: 'object',description: 'Optional workflow settings (timezone, error handling, etc.). Every key the n8n Public API accepts is forwarded, including availableInMCP, which exposes the workflow to n8n\'s instance-level MCP server.'},
25
25
nodeGroups: {type: 'array',description: 'Optional canvas groups (n8n 2.28+): [{name, nodeIds, description?}]. Members are node IDs from nodes[] and must form a connected run with no trigger among them. Dropped with a warning on n8n older than 2.28.'},
26
26
projectId: {type: 'string',description: 'Optional project to create the workflow in (enterprise feature). Defaults to the personal project.'},
27
27
parentFolderId: {type: 'string',description: 'Optional folder to place the workflow in (n8n 2.32+; rejected with a 400 on older instances). Omit for the project root. Manage folders with n8n_manage_folders.'}
@@ -72,7 +72,8 @@ n8n_create_workflow({
72
72
timezone: "America/New_York",
73
73
errorWorkflow: "error_handler_workflow_id",
74
74
saveDataSuccessExecution: "all",
75
-
saveDataErrorExecution: "all"
75
+
saveDataErrorExecution: "all",
76
+
availableInMCP: true // expose to n8n's instance-level MCP server
- **updateSettings**: Modify workflow settings (merged over the current ones). Any key the n8n Public API accepts is forwarded, e.g. \`availableInMCP: true\` exposes the workflow to n8n's instance-level MCP server.
54
54
- **updateName**: Rename the workflow
55
55
- **setNodeGroups**: Replace the workflow's canvas groups (n8n 2.28+). Full replacement — pass every group to keep, or \`[]\` to ungroup everything. Each group takes \`name\` plus either \`nodeNames\` or \`nodeIds\`, and an optional \`description\` (max 155 chars, n8n 2.32+; dropped automatically on older instances). Group members must form a connected run with no trigger among them; n8n validates that on save and its message is returned unchanged if a group you asked for is rejected.
description: 'Optional workflow settings (execution order, timezone, error handling). Any other key the n8n Public API accepts is forwarded as well, e.g. availableInMCP (expose the workflow to n8n\'s instance-level MCP server), callerPolicy, callerIds.',
0 commit comments