Package gallery

Install a working process in minutes.

30 ready-made packages across 6 areas, each a complete workflow with its rules, data, integrations and emails. Download one, connect your systems and run it on the same fast, headless engine — from a form, your API, a schedule or a data change.

Starts

30 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.0.0.utpkg
usertasks packages inspect expense-claims-1.0.0.utpkg
usertasks packages install expense-claims-1.0.0.utpkg

Trust

Signed packages, verifiable downloads

Gallery packages are built from the sources in the UserTasks repository and signed with the UserTasks Gallery ed25519 key. 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

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.

Build your own: Packages documentation