scenario-workflows
Scenario Workflows
Overview
A Scenario workflow is a saved node graph chaining several models into one call; users say "app" and mean one whose status is ready. workflow_run returns a job tracked like any other generation.
Only workflows_list, workflow_get and workflow_run are listed by default; approve and reject run through scenario_tools_search plus their executor lane. Connection and the core loop: the scenario skill. Creating, editing and publishing graphs: the scenario-workflow-authoring skill. If a sibling skill named here is missing from your available skills, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.
Quick reference
| Step | Call | Notes |
|---|---|---|
| 1. List | workflows_list status="ready" |
Always cap limit |
| 2. Read the contract | the record's inputs[] |
name is the run key |
| 3. Price and validate | workflow_run with dry_run=true |
Returns cost, creates no job |
| 4. Run | workflow_run with inputs |
Returns a job |
| 5. Wait | jobs_wait |
Re-call with pending_job_ids |
Ids are prefixed wflow_, not workflow_ as tool-doc examples show; copy them from workflows_list. search with target="workflows" returned 403 at authoring time, with or without public=true.