WorkflowTemplate catalog and marketplace
Blueprints are complete example workflows. Catalog WorkflowTemplates are single steps Dagweave maintains. Marketplace listings are WorkflowTemplates your team publishes for others to install.
Blueprints
Section titled “Blueprints”Choose Library from the workflow menu and pick one. It replaces the canvas. There are blueprints for approvals, CI, scheduled jobs, ETL and GitOps, on every plan.
The catalog
Section titled “The catalog”The catalog has 74 WorkflowTemplates for object storage, databases, LLMs, chat notifications, Docker, Kubernetes, Helm and more. Browse catalog WorkflowTemplates lists them all.
Add one from the Catalog group in the step picker. A dialog asks for required parameters, which you can change later. On save, Dagweave copies the WorkflowTemplate into your team’s WorkflowTemplates. That copy only changes when Dagweave releases a new catalog version.
A catalog step’s Info tab shows its changelog.
Catalog steps have no ports, so you can’t wire their output into another step. If a later step needs a working tree, use the git-checkout and git-commit-push steps.
Anyone can browse the catalog. Six WorkflowTemplates are free: http-request-curl,
download-file, git-clone, run-shell-tests, timed-wait and
conditional-when. That’s enough to build and run a workflow end to end. The
other 68 need Production or Business. On other plans, saving a workflow that uses one
fails with a 402.
Browse and install from the marketplace
Section titled “Browse and install from the marketplace”Needs Production or Business. Open the workflow menu, choose Library, and go to the Marketplace tab. Installing a listing copies it into your team’s WorkflowTemplates, where you can edit it like your own.
You see listings from your teams and, if your team is in an organisation, from every team in it. View shows a listing’s steps before you install it. A listing from your own team says Your team’s listing and has no Install button, because it’s already yours. After you install one, the copy is under My WorkflowTemplates in the step picker.
Publish to the marketplace
Section titled “Publish to the marketplace”Open the workflow menu, choose Publish as WorkflowTemplate, name it, and pick who can use it. Only your team is the default. When you’re in more than one team, you can also let your team’s members use it in their other teams too. List it in the marketplace needs Business, and the listing is still only shown to members of your team, who can install a copy into their other teams. If your team is in an organisation, Everyone in the organisation lists it for every team in it. That also needs Business.
WorkflowTemplate versions
Section titled “WorkflowTemplate versions”Each publish gets a versioned name like base-v2. Publishing unchanged content
returns the existing version. Workflows on an old version keep using it. The
marketplace shows the latest.
Choose WorkflowTemplates from the workflow menu to see them all. Open shows the latest version’s steps, read-only. Click a row’s summary to list the workflows that use it, each one a link, and every version with its own Open. A template another team shares with you says Shared by that team, and only that team can publish or unpublish it.
A step that calls one of your WorkflowTemplates shows its version on the canvas, and its Info tab says whether a newer one is published. Use v3 moves that step to it. Update N workflows to v3 in the WorkflowTemplates list does the same for every workflow that uses an older version. Workflows that come from Git are skipped, since a change to them goes to Git.