YAML Schema

This section contains the complete YAML schema definitions for all available block types in Agent Forge. Each block type has specific configuration requirements and output formats.

Core Blocks

These are the essential building blocks for creating workflows:

Title

Starter Block Workflow entry point supporting manual triggers, webhooks, and schedules

Target

file:///yaml/blocks/starter

Title

Agent Block AI-powered processing with LLM integration and tool support

Target

file:///yaml/blocks/agent

Title

Function Block Custom JavaScript/TypeScript code execution environment

Target

file:///yaml/blocks/function

Title

Response Block Format and return final workflow results

Target

file:///yaml/blocks/response

Logic & Control Flow

Blocks for implementing conditional logic and control flow:

Title

Condition Block Conditional branching based on boolean expressions

Target

file:///yaml/blocks/condition

Title

Router Block AI-powered intelligent routing to multiple paths

Target

file:///yaml/blocks/router

Title

Loop Block Iterative processing with for and forEach loops

Target

file:///yaml/blocks/loop

Title

Parallel Block Concurrent execution across multiple instances

Target

file:///yaml/blocks/parallel

Integration Blocks

Blocks for connecting to external services and systems:

Title

API Block HTTP requests to external REST APIs

Target

file:///yaml/blocks/api

Title

Webhook Block Webhook triggers for external integrations

Target

file:///yaml/blocks/webhook

Advanced Blocks

Specialized blocks for complex workflow patterns:

Title

Evaluator Block Validate outputs against defined criteria and metrics

Target

file:///yaml/blocks/evaluator

Title

Workflow Block Execute other workflows as reusable components

Target

file:///yaml/blocks/workflow

Common Schema Elements

All blocks share these common elements:

Basic Structure

block-id:
  type: <block-type>
  name: <display-name>
  inputs:
    # Block-specific configuration
  connections:
    # Connection definitions

Connection Types

• success: Target block for successful execution

• error: Target block for error handling (optional)

• conditions: Multiple paths for conditional blocks

Environment Variables

Use double curly braces for environment variables:

inputs:
  apiKey: '{{API_KEY_NAME}}'
  endpoint: '{{SERVICE_ENDPOINT}}'

Block References

Reference other block outputs using the block name in lowercase:

inputs:
  userPrompt: <blockname.content>
  data: <functionblock.output>
  originalInput: <start.input>

Validation Rules

All YAML blocks are validated against their schemas:

1. Required fields: Must be present

2. Type validation: Values must match expected types

3. Enum validation: String values must be from allowed lists

4. Range validation: Numbers must be within specified ranges

5. Pattern validation: Strings must match regex patterns (where applicable)

Quick Reference

Block Types and Properties

Block Type	Primary Output	Common Use Cases
starter	.input	Workflow entry point
agent	.content	AI processing, text generation
function	.output	Data transformation, calculations
api	.output	External service integration
condition	N/A (branching)	Conditional logic
router	N/A (branching)	Intelligent routing
response	N/A (terminal)	Final output formatting
loop	.results	Iterative processing
parallel	.results	Concurrent processing
webhook	.payload	External triggers
evaluator	.score	Output validation, quality assessment
workflow	.output	Sub-workflow execution, modularity

Required vs Optional

• Always required: type, name

• Usually required: inputs, connections

• Context dependent: Specific input fields vary by block type

• Always optional: error connections, UI-specific fields