Exporting a workflow that calls a subworkflow results in "workflowId":"${undefined}"

[mig82]

Describe the problem/error/question

I use the N8N API to export workflows from one N8N instance and then import them into another.
I recently started using the "Execute sub-workflow" node and noticed that this results in the executeWorkflow node having the workflowId property set to what looks like an expression that resulted in null —i.e. "workflowId": "${undefined}"

What is the error message (if any)?

There's no error message.

Please share your workflow/screenshots/recording

Here's what I'm getting:

{
	"parameters": {
		"workflowId": "${undefined}",
		"workflowInputs": {
			"mappingMode": "defineBelow",
			"value": {},
			"matchingColumns": [],
			"schema": [],
			"attemptToConvertTypes": false,
			"convertFieldsToString": true
		},
		"options": {}
	},
	"type": "n8n-nodes-base.executeWorkflow",
	"typeVersion": 1.2,
	"position": [
		-100,
		4440
	],
	"id": "18f9c1ec-8ac3-4350-897f-c143d2945595",
	"name": "callMyOtherWorkflow"
}

Here's what I'd expect:

{
	"parameters": {
		"workflowId": {
			"__rl": true,
			"mode": "list",
			"value": "MX0GSNtBco17QSEb",
			"cachedResultName": "myOtherWorkflow"
		},
		"workflowInputs": {
			"mappingMode": "defineBelow",
			"value": {},
			"matchingColumns": [],
			"schema": [],
			"attemptToConvertTypes": false,
			"convertFieldsToString": true
		},
		"options": {}
	},
	"type": "n8n-nodes-base.executeWorkflow",
	"typeVersion": 1.2,
	"position": [-100, 4440],
	"id": "18f9c1ec-8ac3-4350-897f-c143d2945595",
	"name": "validateToken"
}

Share the output returned by the last node

N/A

Debug info

core

• n8nVersion: 1.92.2
• platform: npm
• nodeJsVersion: 18.20.7
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: community

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 168 hours
• maxCount: 50 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10.15; rv:139.0) gecko/20100101 firefox/139.0
• isTouchDevice: false

Generated at: 2025-07-06T18:20:24.890Z}

[Joffcom]

Hey @mig82,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-2944".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

[mig82]

For additional context, the endpoint I'm hitting to export the workflow is ${host}/api/v1/workflows? and I also just noticed that using the n8n CLI to export the workflow with the command n8n export:workflow does fill in the workflowId object correctly and doesn't present this issue. I hope this helps.

[n8n-assistant]

Hi @mig82 👋

Thanks so much for your patience while we’ve been improving n8n. We know it’s taken some time to review this issue, and we’re currently updating our triage process to better keep up with our growth.

There have been a lot of improvements in recent releases, so we’d really appreciate it if you could check whether this issue still occurs in the latest release.

When you have a moment, please copy and paste the checklist below as a comment so our system can update the status automatically:

[ ] I have updated to the latest stable version of n8n [please specify version number] and I am still experiencing this issue
[ ] Please close this issue – I am no longer experiencing it
[ ] Please close this issue – [please specify a reason]

If we don’t hear from you in the next 14 days this issue will be automatically closed, feel free to reopen - don’t forget to add the checklist above so that our automated systems notify us of the issue.

Thanks again for helping us keep n8n healthy and up-to-date 💚

[n8n-assistant]

As we haven’t heard back from you, we’re going to close this issue to keep things organized. But don’t worry, if you have more information or need further assistance, you’re welcome to reopen the issue anytime or create a new one. We’re always happy to help!

Thanks for reaching out and have a great day! If this was closed by mistake and you have been waiting for us let me know and I can also re-open it.