Workflow templates

Reusable blueprints and templates that create real workflows, tables, columns, and prompts.

Oxygen ships reusable patterns as blueprints and workflow templates. Applying one creates real workflows, tables, columns, prompts, and run configuration in your organization.

Templates are not a separate execution primitive. Once applied, the resulting workflow is inspectable and editable like one you defined by hand.

Blueprints

Blueprints are portable bundles for a GTM motion. They can include workflow definitions, table schemas, column definitions, prompts, and parameter inputs.

oxygen blueprints list --json
oxygen blueprints describe outbound-pilot --json
oxygen blueprints preflight outbound-pilot --input-json '{...}' --json
oxygen blueprints apply outbound-pilot --input-json '{...}' --json

Preflight first. It tells you what will be created, what context is missing, and what needs review before live work.

Workflow templates are the older seeded template surface and are still available through the CLI.

Step	Command	What it does
Search	`oxygen workflows templates search <query>`	Discover templates
Describe	`oxygen workflows templates describe <id>`	Full descriptor
Preflight	`oxygen workflows templates preflight <id> --input-json '{...}' --mode dry_run`	Predicts inputs, output tables/columns, credit cost, approval requirements
Apply	`oxygen workflows templates apply <id> --input-json '{...}'`	Creates the workflow disabled, plus its tables and columns
Run	`oxygen workflows templates run <id> --input-json '{...}' --mode live --max-credits N --approved`	Creates and immediately fires

Always preflight before apply.

Preflight response

{
  "ok": true,
  "issues": [],
  "tables": { "creates": ["dm_pilot_targets"], "modifies": [] },
  "columns": { "creates": ["dm_draft"], "modifies": [] },
  "approval": { "required": true, "reason": "live HeyReach send" },
  "credits": { "capRequired": true, "estimated_max": 25 },
  "context": { "missing_sections": [] }
}

ok: false means the inputs or workspace context are insufficient. Fix what issues lists, re-preflight.

What `apply` produces

A template that, say, builds an outbound pilot will:

Create the lead table.
Add a work-email enrichment column.
Add an AI scoring column.
Add a copy-drafting AI column.
Add a provider-action tool column for the outbound system.
Wire all five as a chained workflow with an approval gate before the sync step.

Inspect the result with oxygen workflows get <workflow-id> --json. Modify it like any other workflow.

Authoring new templates

For reusable motions inside your workspace, start from a blueprint or durable recipe. For one-off operator work, a table plus chained columns is usually enough.

Workflows — what a template compiles to.
Modes — smoke_test, dry_run, live for preflight and run.
Recipes — for custom logic that doesn't fit a template.

Workflow templates

Blueprints