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 '{...}' --jsonPreflight first. It tells you what will be created, what context is missing, and what needs review before live work.
Workflow templates (deprecated)
oxygen workflows templates ... is the older seeded template surface. Its subcommands are now deprecated aliases that route through the canonical blueprint surface above, and run has been removed. Use oxygen blueprints directly.
| Step | Deprecated alias | Use instead |
|---|---|---|
| Search | oxygen workflows templates search <query> | oxygen blueprints list |
| Describe | oxygen workflows templates describe <id> | oxygen blueprints describe <slug> |
| Preflight | oxygen workflows templates preflight <id> --input-json '{...}' | oxygen blueprints preflight <slug> |
| Apply | oxygen workflows templates apply <id> --input-json '{...}' | oxygen blueprints apply <slug> |
| Run | Removed — returns a typed 410 with error code workflow_template_run_deprecated | oxygen blueprints apply <slug>, then oxygen workflows call <workflow> |
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.