Marketplace
Browse installed pack content, add Process Flows to an environment, and deploy Workflows — all from the agentic Marketplace.
The Marketplace is the single place in the agentic app where you discover and activate pack-installed content for your workspace environment. It replaces the former separate Templates and Process Flows surfaces.
The Marketplace shows content that your org admin has already installed via Settings → Packs. If a Process Flow or Workflow you expect is missing, ask your admin to upload the corresponding pack.
Data sources and ontology packs install from the Analytics → Marketplace instead, which filters by content type. See Packs.
Opening the Marketplace
Click Marketplace in the agentic sidebar. The page lists everything available to your organization in a single table — one row per item. A free-text search plus a content-type filter (All / Process flows / Workflows) narrow the list:
- Process flows — structured, repeatable process flows (stages, tasks, personas). Authored via the SDK and shipped as packs.
- Workflows — executable block-graphs. Deploy them into the active environment to run as standalone automations or as the automation behind a process flow task.
All Add and Deploy actions target the active workspace environment.
Browsing content
Each row shows:
| Column | Meaning |
|---|---|
| Name + description | The template or workflow name and short description from the pack manifest |
| Content type | "Process flow" or "Workflow" |
| Stages | Stage count, for process flows |
| Pack | The pack id that ships this content, with the pack version it comes from (e.g. v1.2.0) |
| Action | An "Added" badge for process flows already opted into this environment, plus Add / Remove / Deploy buttons for workspace admins |
Process-flow rows without an "Added" badge are available but not yet activated in the current environment.
When several versions of the same pack are installed, the Marketplace lists each template or workflow once, from the latest installed version — older versions never appear as duplicate rows. Managing installed versions (updating, pinning, retiring) happens in Settings → Packs.
Adding a Process Flow
Adding a Process Flow opts it into the active workspace environment. Once added, the template appears in Process Flows and can be instantiated by any workspace member.
Search, or filter the list by Process flows. Rows without an "Added" badge are not yet active in this environment.
Click the Add button on the row. You need workspace admin role to add or remove templates.
The row updates immediately to show the "Added" badge. The template is now visible in Process Flows → New Process Flow.
Only workspace admins can add or remove templates. Workspace members can browse the Marketplace and instantiate templates that have already been added.
Removing a Process Flow
Click Remove on an already-added template row to withdraw it from the active environment. This hides it from the Process Flows creation flow but does not affect any running Process Flows — they hold a frozen snapshot of the template taken at instantiation time and continue to run unchanged.
Deploying a Workflow
Deploying a workflow materializes it into the active workspace environment. Deployed workflows become available in the workflow editor and as workflowId targets for process flow action templates.
Search, or filter the list by Workflows.
Click the Deploy button. You need workspace admin role. Deployment is idempotent — re-deploying the same workflow version is safe.
Once deployed, the workflow appears in the workflow editor and can be referenced by workflowId from process flow action templates of type workflow.
Process Flows
After adding a Process Flow, workspace members can start a new run from Process Flows in the sidebar. Each run is a Process Flow — a live, independent instance that carries a frozen snapshot of the template taken at instantiation time. Subsequent changes to the template (via a new pack version) do not affect running flows.
See Process Flows for how to author a Process Flow via the SDK.
Deleting a Process Flow
Deleting a Process Flow (from the card menu on the Process Flows page, or from the flow's header) is permanent and cannot be undone. To prevent accidents, you must type the flow's name to confirm. The deletion removes:
- The flow itself, with all its stages, tasks, actions, meetings, and extractions.
- The workspace knowledge base that was auto-created for the flow at instantiation time, including all its pages and uploaded documents.
Organization knowledge bases are never affected — if the flow's workspace KB promoted learnings to an org-KB domain, the promoted org-KB content stays.
Roles summary
| Action | Required role |
|---|---|
| Browse Marketplace | Workspace member |
| Add / Remove a Process Flow | Workspace admin |
| Deploy a Workflow | Workspace admin |
| Instantiate a Process Flow | Workspace member |
Where content comes from
All Marketplace content comes from the org pack catalog — the set of packs an org admin has installed via Settings → Packs. There is no in-app content creation. To author new Process Flows or Workflows, use the Authoring SDK and publish a pack.