Hub publishing checklist
Review a Workflow Template or Work Pack before submitting it to the public catalog.
Use this checklist for Workflow Templates and Work Packs. Plugin distribution has a separate installation and review path.
- Identity: Give the package a stable ID and a new version when its content changes. Confirm the publisher and package kind in the exported file.
- Import: Import the exact file in a clean desktop project. Check package validation, node bindings, required connections, and where the first output lands.
- Safety: Remove account IDs, tokens, private URLs, file paths and live data from the package and screenshots. Require explicit confirmation before real sends, writes or publishing. Prove the sample with a test account or a draft path.
- Listing: Describe the inputs, outputs, prerequisites and external effects. Use a representative cover and write reproducible instructions.
- Submission: Use an authorized publisher or review channel when available. Treat a pending submission as pending. Confirm the published release and version in Hub before sharing its link.
If a publish or import check fails, fix the pack and validate the resulting bytes again. A published workflow in your desktop library is independent of a public Hub release.