Automate
Workflows
Node types, branching, approval steps and what the MVP builder supports.
Availability note — these docs describe both working and planned product areas. Account authentication, administrator-managed AIHK/AICA tenant regions and keys, signed-in Composer runs and public Guard scans are connected. Skills, Memory, Agents, Workflows, Apps, billing, the public SDK/CLI and the unified API are previews unless a section explicitly says otherwise.
Roadmap and package-contract reference: this page describes the intended GenCMS runtime. The current deployment persists workspace records and drafts but does not execute marketplace Skills, index Memory for retrieval, publish packages, or run Agents, Workflows or Apps. See the deployed API reference for the routes available today.
A Workflow connects steps into a repeatable process. The MVP node set is deliberately small — this is not a general automation platform.
| Node | Purpose |
|---|---|
| Input | Typed entry point — file, URL, text or structured record |
| Model | A direct model call with a prompt |
| Skill | An installed Skill at a pinned version |
| Memory retrieval | Fetch context from named collections |
| Condition | Branch on a value from a previous step's typed output |
| Human approval | Pause until a person approves, edits or rejects |
| HTTP call | Send or fetch from an external endpoint |
| Output | Export, publish, email or return to the caller |
Website URL ↓ Fetch page ↓ Skill: SEO Audit ↓ Memory: Brand Rules ↓ Skill: Content Rewrite ↓ Human approval ↓ Export / publish
Execution states
Long-running Workflows report a real state rather than an indefinite spinner: queued, validating, retrieving_context, scanning, selecting_model, running, validating_output, completed, failed.
A human approval node holds the run without consuming credits. The Workflow resumes from the same state when the approval arrives, including through the API.