Community gallery

Share your solution

The gallery is where the UserTasks community uploads and shares solutions. Upload a package you built, tell people what it does, and once a moderator approves it, it is listed as a Community package for every UserTasks workspace, cloud and self-hosted.

Upload a package

What we check automatically

A valid .utpkg: checksums match, a signature (optional) verifies, at most 5 MB
Real workflows: known node types, valid node settings, one trigger, every outcome and branch connected
Everything it points at is inside the package (tables, forms, references, sub-workflows, templates)
No secrets: credentials are placeholders, integrations use placeholder hosts (*.example.com)
No raw HTTP or placeholder steps, custom code, MCP servers or log destinations
Forms, lookups and buttons are valid; screenshots are real images (SVGs sanitised)

Then a moderator reviews it

The package is installed in a scratch workspace and run with your sample input where possible. A moderator approves it or explains what to change, and you get an email either way. Approved packages show your name, the licence, version history and downloads. Anyone can report a listed package.

Contribute an official package with a pull request

Official packages are folders in the repository's gallery/packages: a gallery.json (metadata, sample input, expected run), a README and the config-as-code assets. CI validates every package and verifies it end to end on a local stack; maintainers sign releases with the UserTasks Gallery key.

shell

usertasks config export --workflow <id> --out gallery/packages/my-package/assets
# add gallery/packages/my-package/gallery.json and README.md
npm run gallery:build -- --validate my-package
npm run gallery:build -- --out /tmp/g my-package && npm run gallery:verify -- --dir /tmp/g my-package
git checkout -b gallery/my-package && git commit -am "Gallery: my package" && git push

Contributing guide

The CONTRIBUTING guide's Gallery packages section and gallery/README.md list the rules: placeholder hosts, placeholder or routed assignees, response models on every reference, and a sample input that reaches the first task.

The public repository link appears here once it is launched.