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.

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:

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.

Updating an ontology pack to a newer version

Enabling an ontology pack for a workspace-environment installs a workspace-scoped copy of its ontology and bindings — that is the copy the Ontology Designer and graph show (labelled "… (Workspace · <env>)"). Uploading a newer pack version in Settings → Platform → Packs updates the org catalog, but it does not silently change your workspace copy. Instead, when a newer catalog version is available you'll see an Update affordance in two places:

• the Ontology Designer (/ontology) shows a "Newer version available → Update to v<x>" banner above the workbench whenever the selected ontology is behind its pack's catalog version;
• the Marketplace pack row shows an Update to v<x> button next to the Installed badge.

Clicking Update re-applies the pack's bindings (identity columns, column map, transforms, binding context, source) to your workspace-environment in place — no need to unbind or re-pick anything. Updates are always an explicit click, so a workspace ontology you've customised is never overwritten without your action.

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.

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.

Deployed workflows carry a Marketplace badge in the workflow selector — hover it to see the source pack and template. They can be opened, edited, and renamed like any workflow, but they cannot be deleted from the selector or the API: their lifecycle belongs to the Marketplace, and re-deploying the pack version overwrites them in place.

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.

Tracing a Process Flow's origin

Every workspace member who can open a Process Flow can select Debug in its header. The right-side panel shows the source pack and template, who created the instance, and—when retained execution data proves the link—the triggering workflow, trigger type, execution status, timestamps, and a link to replay the execution in the workflow editor.

The panel includes only bounded, secret-redacted error summaries; it does not expose webhook payloads, headers, or workflow inputs and outputs. If the creating execution is no longer retained, it reports the origin as unavailable instead of guessing from nearby timestamps.

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.

Roles summary

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.