Workflows
Node Types
The 8 supported node types in Ask Sage Agent Builder workflows.
AutoFlow supports 8 node types defined in the workflow schema. Each type has specific config fields and produces specific outputs.
Node Types Reference
Node Conventions
v2 Identity Model (Current)
Every node has a three-layer identity:
| Field | Format | Example | Purpose |
|---|---|---|---|
id | UUID | "862ffdc5-f240-535b-ba94-05807abb7952" | Edge wiring and execution |
slug | snake_case | "extractor" | Variable references ({{extractor.response}}) |
key | string | "" | Reserved for future use |
label | Free text | "Extractor" | Human-readable display name |
- Slugs must be unique within a workflow and use
snake_caseformat - Labels are human-readable names shown in the Agent Builder UI
- Positions define visual placement in the canvas (
xandybetween -10000 and 10000) - All variable references use
{{slug.response}}syntax (slugs, not UUIDs)
Node Registry
All 8 node types are defined in the node registry (node_registry/asksage_nodes.yaml), which serves as the single source of truth for parameters, handles, and constraints. Per-node JSON Schemas are auto-generated from the registry into schemas/nodes/.
Legacy v1 Format
Older workflows use snake_case string IDs instead of UUIDs and lack the slug/key fields. The validator auto-detects v1 vs v2 format. See Schema Validation for details.