Skip to main content

​
Basic Structure

Tasks in workflows follow a consistent structure and can be defined in three ways: 
workflow:
  tasks:
    - id: send_notification
      type: basic
      use: compozy/tools:[email protected]
      with:
        message: "{{ tasks.process_data.output }}"
      on_success:
        next: cleanup

​
Key Elements

Tasks

The actual work to be performed - see Task Types

Flow Control

How tasks connect and interact with each other
For configuration of triggers, environment variables, and other base structure elements, please refer to the Base Structure documentation.

​
Basic Workflow Patterns

​
Sequential Processing

Create linear workflows where tasks execute one after another: 
workflow:
  tasks:
    - id: fetch_data
      type: basic
      use: compozy/tools:[email protected]
      schema:
        input:
          type: object
          properties:
            url: string
      with:
        url: "{{ env.API_URL }}"
      on_success:
        next: process_data

    - id: process_data
      type: basic
      use: compozy/tools:[email protected]
      with:
        data: "{{ tasks.fetch_data.output }}"
      on_success:
        next: save_results
      retry:
        attempts: 3
        backoff: exponential
        interval: 1s

​
Conditional Logic

Add decision points to your workflow using decision tasks: 
workflow:
  tasks:
    - id: check_data
      type: decision
      condition: "{{ tasks.validate_input.output.is_valid }}"
      routes:
        "true": process_valid
        "false": handle_invalid
      on_condition_match:
        next: log_decision

    - id: process_valid
      type: basic
      use: compozy/tools:[email protected]
      on_error:
        next: handle_error

    - id: handle_invalid
      type: basic
      use: compozy/tools:[email protected]

​
Parallel Processing

Execute tasks concurrently using parallel tasks: 
workflow:
  tasks:
    - id: process_batch
      type: parallel
      config:
        max_concurrent: 3
        fail_fast: false
      execute:
        - use: compozy/tools:[email protected]
          retry:
            attempts: 3
        - use: compozy/tools:[email protected]
          retry:
            attempts: 2
      on_error:
        next: handle_batch_error

​
Composability

Break down workflows into reusable components: 
# tasks/shared.yaml
tasks:
  - id: document_processor
    type: basic
    use: compozy/tools:[email protected]
    schema:
      input:
        type: object
        properties:
          format:
            type: string
            enum: [pdf, docx]
    with:
      format: pdf

# workflow.yaml
workflow:
  tasks:
    - id: process_document
      import: ./tasks/shared.yaml
      with:
        document: "{{ trigger.document }}"
      on_success:
        next: notify_complete

​
Memory Integration

Workflows can reference memory systems defined in the base configuration: 
workflow:
  memory: chat_memory    # Reference to memory defined in base config
  tasks:
    - id: chat_task
      type: basic
      use: compozy/tools:[email protected]
      with:
        context: "{{ memory.chat_memory.current_thread }}"
        history: "{{ memory.chat_memory.last_messages }}"
        relevant: "{{ memory.chat_memory.semantic_search }}"

​
Best Practices

1

Task Design

  • Keep tasks focused and single-purpose
  • Use appropriate task types
  • Define clear input/output schemas
2

Error Handling

  • Configure retry policies
  • Implement fallback mechanisms
  • Use error routing effectively
3

Performance

  • Use parallel tasks when possible
  • Configure appropriate concurrency
  • Implement efficient batching
4

Maintainability

  • Break down complex workflows
  • Use schema validation
  • Document task requirements

​
References

Task Types

Learn about different types of tasks

Composability

Break down workflows into components

Error Handling

Implement error handling strategies

Base Structure

Learn about triggers, env vars, and base configuration