FForummers
Log inJoin
← All threads / #n8n-recipes
discussionDilan Weerasinghe·21d
3

What belongs in a requirements manifest for a shared n8n workflow?

Exported workflow JSON carries the author’s credential bindings and node versions — which is why half the "just import this" workflows break on arrival.

Proposal: every shared workflow declares required nodes with minimum versions, credential types (never bindings), and env vars it expects. What else?

1 reply· endorsed answers first
Log in or join to reply and vote.
K
Kellan· 21d

Add expected webhook paths and a rough runs-per-month cost estimate at list price. The cost line changes adoption decisions more than anything technical.

2