Add info on defining input items for sub-workflows

[imchairmanm]

No description provided.

[netlify]

✅ Deploy Preview for n8n-docs ready!

Name	Link
🔨 Latest commit	9e2d75a
🔍 Latest deploy log	https://app.netlify.com/sites/n8n-docs/deploys/67812617b6763f0008a44046
😎 Deploy Preview	https://deploy-preview-2745--n8n-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Overall readability score: 44.71 (🟢 +0)

File	Readability
subworkflow-data-flow.md	78.9 (🔴 -2.37)
subworkflow-usage.md	66.21 (🔴 -0.22)
n8n-nodes-base.executeworkflow.md	74.67 (🔴 -2.67)

View detailed metrics

🟢 - Shows an increase in readability
🔴 - Shows a decrease in readability

File	Readability	FRE	GF	ARI	CLI	DCRS
subworkflow-data-flow.md	78.9	65.42	7.83	8.2	9.27	6.28
	🔴 -2.37	🔴 -1.02	🔴 -1	🟢 +0	🟢 +0.11	🔴 -0.2
subworkflow-usage.md	66.21	55.24	8.91	11.6	11.83	6.47
	🔴 -0.22	🔴 -0.1	🟢 +0.11	🔴 -0.2	🔴 -0.46	🟢 +0.17
n8n-nodes-base.executeworkflow.md	74.67	58.89	7.22	9.7	10.77	6.25
	🔴 -2.67	🔴 -1.52	🔴 -0.52	🔴 -0.6	🔴 -0.35	🔴 -0.05

Averages:

	Readability	FRE	GF	ARI	CLI	DCRS
Average	44.71	35.58	11.38	14.6	14.21	8.43
	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0

View metric targets

Metric	Range	Ideal score
Flesch Reading Ease	100 (very easy read) to 0 (extremely difficult read)	60
Gunning Fog	6 (very easy read) to 17 (extremely difficult read)	8 or less
Auto. Read. Index	6 (very easy read) to 14 (extremely difficult read)	8 or less
Coleman Liau Index	6 (very easy read) to 17 (extremely difficult read)	8 or less
Dale-Chall Readability	4.9 (very easy read) to 9.9 (extremely difficult read)	6.9 or less

[evilnick]

Nice work. Some suggested edits in comments

[nik8n]

Looks mostly good @imchairmanm, thanks for the great work. I have a few feedback points:

1. In the section on "How to create a sub-workflow" we might want to mention that you can also simply create them from the Execute Workflow node, by choosing the option there.
2. You mention that "Debug in Editor" is only available in Pro and Enterprise. That is not true anymore. Users also get it on the registered Community version and on the Starter plan. Maybe that slipped through the cracks?
3. Does it make sense to have the same information in 4 different places? (Trigger, Node, Subworkflow, Flow-logic)

[imchairmanm]

Looks mostly good @imchairmanm, thanks for the great work. I have a few feedback points:

1. In the section on "How to create a sub-workflow" we might want to mention that you can also simply create them from the Execute Workflow node, by choosing the option there.
2. You mention that "Debug in Editor" is only available in Pro and Enterprise. That is not true anymore. Users also get it on the registered Community version and on the Starter plan. Maybe that slipped through the cracks?
3. Does it make sense to have the same information in 4 different places? (Trigger, Node, Subworkflow, Flow-logic)

Thanks for taking a look @nik8n! Let me respond to each individually:

1. Yes, that's a good call. I will add that 👍
2. I don't think I touched anything related to Debug in Editor (but I also didn't review anything that was already there). Thanks for the heads up, I'll adjust that as well.
3. Currently, they're mostly all pulling from the same snippets, so in terms of keeping the info in sync, that makes it easy. I didn't implement the current repetition, but if I could guess why it was initially created like that, I'd imagine it's because:
   • Users often have an easier time digesting info if it's in one place rather than spread out, and
   • We want to put info where users think it should be (where they're looking for it)

(Continuing w/ 3 above) with all of that being said, if you think it's confusing, we should reconsider.

[imchairmanm]

Okay, I believe I fixed all of the obvious issues identified. We can adjust where we display the info later if we think the current split is confusing.