Community package gallery

Install a working process in minutes. Share yours.

The gallery is where the UserTasks community uploads and shares solutions. Start from 56 official packages across 7 areas, each a complete workflow with its forms, rules, data, integrations and emails: Workday, SAP S/4HANA, ServiceNow and Salesforce flows, or packages that need no integrations at all.

Show
Starts

56 packages

How it works

Download, install, connect, run

  1. Step 1

    Download

    Pick a package and download its .utpkg file: one signed ZIP with the workflow and everything it uses.

  2. Step 2

    Install

    Drag the file onto Automations → Packages (or pick it from Browse gallery there), or run usertasks packages install. The file is verified before anything is written.

  3. Step 3

    Connect

    Give the base URLs and tokens of your systems and pick who receives each task. Or keep it incomplete and finish later.

  4. Step 4

    Run

    Start it from the Run dialog, your portal, the API, a webhook or its schedule. Adapt the rules and tables to your policy.

shell
curl -fLO https://usertasks.com/gallery/expense-claims-1.1.0.utpkg
usertasks packages inspect expense-claims-1.1.0.utpkg
usertasks packages install expense-claims-1.1.0.utpkg

Trust

Signed packages, verifiable downloads

Official packages are built from the sources in the UserTasks repository and signed with the UserTasks Gallery ed25519 key. Community packages carry their author's signature when they have one, and their checksum either way. The signature covers a SHA-256 checksum of the manifest, which lists the hash of every file, so any change breaks verification.

Preview builds

Development build: these packages are not signed. Verify the sha256 checksums below. Each package page lists its file SHA-256 and package checksum.

Machine-readable list: /gallery/index.json

Community

Share your solution

Built something others could use? Share it with the community. Every package is checked automatically and approved by a moderator before it is listed as Community.

Upload on usertasks.com

Sign in, upload the .utpkg you built in Automations → Packages, and add a title, description, category, tags, screenshots and a licence (Apache-2.0 by default). We validate it straight away; a moderator reviews it and you get an email with the decision.

Share your solution

Contribute an official package

Official packages are sources in the repository: add a folder to gallery/packages (gallery.json, README and the config-as-code assets) and open a pull request. CI validates and verifies it, and maintainers sign the release.

The public repository link appears here once it is launched.

Questions

About packages

What is in a package?
A .utpkg file holds a workflow and everything it uses: sub-workflows, decision tables, data tables with sample rows, REST integrations with their API references and response models, email templates and AI agents. It is a signed ZIP in the same config-as-code layout the CLI and GitHub sync use.
Do packages contain credentials?
No. Every secret is removed when a package is built and becomes a requirement. The install wizard (or the CLI) asks for base URLs, API tokens and the people who receive each task, or installs the package incomplete until you finish setup.
Can I change a package after installing it?
Yes. Installed assets are ordinary workflows, tables and integrations in your workspace. Edit them in the designer; installing a newer version later upgrades in place and flags anything you changed so you can keep it.
Does it work on a self-hosted instance?
Yes. Packages install the same way on UserTasks cloud and on any self-hosted deployment, from Automations → Packages (drag the file in, or Browse gallery), the REST API or the CLI. Browse gallery on a self-hosted instance shows the Official packages it ships with plus the Community packages from usertasks.com (GALLERY_INDEX_URL; set it to off for air-gapped instances).
What is the difference between Official and Community packages?
Official packages are built by the UserTasks team from the sources in the repository and signed with the UserTasks Gallery key. Community packages are shared by UserTasks users: every one passes the same automatic checks (valid workflows and node settings, no secrets, placeholder hosts, size limits) and a moderator approves it before it is listed. Review a community package before running it, as you would any code from the internet.
What does No integrations needed mean?
The package uses only built-in features: forms, task forms, data tables with sample rows, decision tables, SLAs and escalations, email templates, schedules, sub-workflows and retention policies. It has no third-party API and asks for nothing on install, so it works as soon as it is installed.

Build your own: Packages documentation