34bb613c57
- 20 new high-quality edges across 8 project clusters - Edge types: BUILDS_ON, RELATED_TO, ALTERNATIVE_TO, REQUIRES - Updated relation metadata on connected memories - New episode entries and memory files from recent sessions Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
| id | type | title | tags | importance | confidence | created | updated | relations | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| e085b8bf-6fbf-4fb7-aded-4d2d651fc2e6 | fix | n8n Execute Sub-workflow requires workflowSelector object and active sub-workflow |
|
0.7 | 0.8 | 2026-02-20T05:11:47.869751+00:00 | 2026-02-20T05:12:35.788366+00:00 |
|
Problem
When creating an n8n Execute Sub-workflow node (typeVersion 1.1+) via the API/MCP, passing workflowId as a plain string like "BhzYmWr6NcIDoioy" causes: "No information about the workflow to execute found. Please provide either the 'id' or 'code'!"
Even after fixing the format, if the sub-workflow is not activated, it fails with: "Workflow is not active and cannot be executed."
Solution
Two fixes required:
- workflowId format: Must be a workflowSelector object, not a plain string:
{
"workflowId": {
"__rl": true,
"value": "BhzYmWr6NcIDoioy",
"mode": "id"
}
}
- Sub-workflow must be active: Even though sub-workflows don't have their own triggers, n8n requires them to be activated before a parent can call them. Activate via API:
curl -X POST "http://HOST:5678/api/v1/workflows/WORKFLOW_ID/activate" \
-H "X-N8N-API-KEY: $KEY"
Context
- n8n-nodes-base.executeWorkflow typeVersion 1.1+ uses workflowSelector
- typeVersion 1.0 used plain string (but shows "outdated" warning)
- The
callerPolicy: "workflowsFromSameOwner"setting enforces same-owner access