sales-demos-orchestrator-workflowlisted

Load the Automation Orchestrator demo workflows from config-as-code — inventory/group_vars/aap/ao_workflows.yml — into an environment's AO, resolving job template, credential, integration and approver names to that environment's IDs, or remove them. Runs playbooks/ao_workflows.yml. TRIGGER when: the user wants the AO demo workflow recreated on a new or rebuilt environment, asks to load, import, restore or refresh AO workflows, wants a fallback copy before presenting the AO demo, asks where the rehearsed workflow is saved, or asks about issue #474. SKIP: if AO is not installed or not configured — that is sales-demos-orchestrator then sales-demos-orchestrator-config — or if the user wants to build a workflow live on the AO canvas, which is the demo itself (see the sales.demos-docs Automation Orchestrator guide).
ericcames/sales.demos · ★ 1 · AI & Automation · score 67

Install: claude install-skill ericcames/sales.demos

# sales-demos-orchestrator-workflow Creates or updates every workflow in [`inventory/group_vars/aap/ao_workflows.yml`](../../../inventory/group_vars/aap/ao_workflows.yml) in this environment's Automation Orchestrator. Takes **under a minute**. This skill contains **no logic**. All the work is in [`playbooks/ao_workflows.yml`](../../../playbooks/ao_workflows.yml). See `CLAUDE.md` → *Skills and playbooks*. ## Why the workflow is stored by name, not exported AO's export embeds values that only exist in the environment it came from — AO integration and credential UUIDs, AAP's numeric job template IDs, and the approver's federated username. Imported anywhere else, every one is wrong. The committed file names things instead, and the playbook looks each one up: | In the file | Resolved from | |---|---| | `job_template` | AAP job template ID, through `GET /api/v1/proxies/aap/job_templates` | | `credential` | AO credential ID, `GET /api/v1/credentials` | | `integration` | AO integration ID, `GET /api/v1/integrations` | | `project` | AO project ID, `GET /api/v1/projects` | | `approvers_sso` | The federated AO user each AAP username became on first SSO login, `GET /api/v1/users` | **Node IDs are chosen in the file** (`activity_scan`, …) and expressions reference them. AO references steps by ID, never by display name. ## What it does 1. Asserts the target environment and the connection variables. 2. Reads the AO Route and logs in to AO as the local `admin`. 3. Looks up projects,