docs: add Packaging Subflows as Custom Nodes page - #8355
Conversation
Document the Subflow exporter (shipped in 2.21): package a Node-RED subflow as a custom node published to the Team's Custom Nodes registry, how the name/version behave, and installing it via Manage palette. Notes that packaging is Hosted-Instance-only while the published nodes install on any instance type. Cross-links from Custom Node Packages. Screenshots reused from the 2.21 changelog. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Docs state what the feature is, not who's entitled to it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
This is a Self Hosted Enterprise only feature, (it is available to both Hub and Edge on the new tiers). The reason it was available to Pro on FFC is that there was never a hard link between what we choose to offer to Pro teams on FFC and what was in a Pro Self Hosted license because FFC always ran with a full Enterprise License. |
|
Subflow export should be available on all new tiers. Fleet should have this too. |
Fleet is just edge with bulk device pricing, they have identical features |
|
@hardillb did you want to change something about this PR? I dont think I mentioned anything about tiers in the docs, just what the feature is. |
|
No, just commenting on the licence availability |
3 participants
What & why
Adds a user-docs page for the Subflow exporter (shipped in 2.21) — packaging a Node-RED subflow as a custom node published to the Team's Custom Nodes registry. This was previously only covered in the release changelog/blog, with no reference doc.
Paired with website PR FlowFuse/website#5723 (Application Guide), whose Subflow link points at this new page — that PR is held until this one merges so the link doesn't 404.
Changes
docs/user/packaging-subflows.md— Packaging Subflows as Custom Nodes@flowfuse-<team id>/<node-name>naming; same-name republish updates, version bump for updates)docs/user/custom-npm-packages.md— note cross-linking to the new pageKey nuance called out
Packaging is Hosted-Instance-only, but the published nodes install and run on any instance type (Hosted or Remote).