Inline resource blocks (before / after)

before: and after: are expression lists that run around a resource's main action - before: prepares data before the action runs, after: processes output after it completes.

Works in workflow and agent mode.

• before: runs before the main action (chat, httpClient, sql, file, etc.)
• after: runs after the main action

Both accept bare scalar expressions. Each item executes in sequence and can call set() to store values, perform calculations, or read from memory and session.

Basic usage

actionId: preProcessor
name: Pre-Processor
after:
  - set('normalized_input', lower(get('q')))
  - set('timestamp', info('timestamp'))
  - set('user_id', get('userId', 'session'))

chat:
  prompt: "Process: {{ get('normalized_input') }}"

When to use expr blocks

1. Data transformation

Transform data before using it:

# resources/example.yaml
after:
  - set('cleaned_data', trim(get('rawData')))
  - set('request_time', info('timestamp'))

httpClient:
  url: "https://api.example.com/process"
  data:
    input: get('cleaned_data')
    timestamp: get('request_time')

2. Memory/Session operations

Store values for later use:

# resources/example.yaml
after:
  - set('last_query', get('q'), 'memory')
  - set('query_count', (get('query_count', 'memory') ?? 0) + 1, 'memory')
  - set('user_preferences', get('prefs'), 'session')

chat:
  prompt: "User asked {{ get('query_count') }} times. Query: {{ get('q') }}"

3. Calculations

Perform calculations before execution:

# resources/example.yaml
after:
  - set('total', get('price') * get('quantity'))
  - set('discount', get('total') * 0.1)
  - set('final_price', get('total') - get('discount'))

apiResponse:
  response:
    total: get('total')
    discount: get('discount')
    final_price: get('final_price')

4. Conditional logic

Set values based on conditions:

# resources/example.yaml
after:
  - set('mode', get('env') == 'production' ? 'strict' : 'debug')
  - set('cache_ttl', get('mode') == 'strict' ? '1h' : '5m')

httpClient:
  url: "https://api.example.com/data"
  cache:
    ttl: get('cache_ttl')

Execution order

Expressions in each block run top to bottom. The full per-resource order is:

Common patterns

Pattern 1: data normalization

# resources/example.yaml
after:
  - set('normalized_email', lower(trim(get('email'))))
  - set('normalized_name', trim(get('name')))

sql:
  query: |
    INSERT INTO users (email, name) 
    VALUES ($1, $2)
  params:
    - get('normalized_email')
    - get('normalized_name')

Pattern 2: Counter/State management

# resources/example.yaml
after:
  - set('request_id', info('ID'))
  - set('request_count', (get('request_count', 'memory') ?? 0) + 1, 'memory')
  - set('last_request_time', info('timestamp'), 'memory')

chat:
  prompt: "Request #{{ get('request_count') }}: {{ get('q') }}"

Pattern 3: data aggregation

# resources/example.yaml
after:
  - set('items', get('previousResource'))
  - set('total_items', len(get('items')))
  - set('total_value', sum(map(get('items'), .price)))

apiResponse:
  response:
    summary:
      count: get('total_items')
      total: get('total_value')

Pattern 4: error handling preparation

# resources/example.yaml
after:
  - set('fallback_value', get('default', 'memory') ?? 'N/A')
  - set('retry_count', get('retry_count', 'memory') ?? 0)

httpClient:
  url: "https://api.example.com/data"
  retry:
    maxAttempts: 3

Expression-only resources

You can create resources that only execute expressions (no main action):

actionId: setupContext
name: Setup Context
after:
  - set('session_id', info('ID'))
  - set('start_time', info('timestamp'))
  - set('environment', get('ENV', 'env') ?? 'development')
  - set('user_context', get('user', 'session') ?? {})

This resource returns {"status": "expressions_executed"} and can be used as a dependency for other resources.

Accessing expr results

Values set in expr blocks are immediately available via get():

# resources/example.yaml
after:
  - set('processed_data', lower(trim(get('raw_data'))))

# Use the processed data
chat:
  prompt: "Analyze: {{ get('processed_data') }}"

Best practices

1. Keep expressions simple

# Good: Simple, clear expressions
after:
  - set('normalized', trim(get('input')))
  - set('count', len(get('items')))

# Avoid: Complex logic (use Python resource instead)
# after:
#   - set('result', get('a') * get('b') / get('c') + get('d') - ...)

2. Use for side effects

# Good: Storing state
after:
  - set('last_action', get('action'), 'memory')
  - set('timestamp', info('timestamp'), 'session')

# Avoid: Complex data processing (use Python)

3. Order matters

Expressions execute in sequence:

# Correct order
after:
  - set('step1', trim(get('input')))
  - set('step2', lower(get('step1')))
  - set('final', replace(get('step2'), ' ', '_'))

# Wrong: step2 depends on step1, must come after

Limitations

• No return values: Expressions do not return values (use set() to store results)
• Sequential execution: Expressions run one after another
• Error handling: If an expression fails, the resource fails
• Complex logic: For complex operations, use Python resources

Examples

Example 1: request logging

actionId: loggedRequest
name: Logged Request
after:
  - set('request_id', info('ID'))
  - set('request_time', info('timestamp'))
  - set('request_log', {
      'id': get('request_id'),
      'time': get('request_time'),
      'query': get('q')
    }, 'memory')

chat:
  prompt: "{{ get('q') }}"

Example 2: data validation and transformation

actionId: validatedInput
name: Validated Input
after:
  - set('email', lower(trim(get('email'))))
  - set('age', int(get('age')))
  - set('is_valid', get('email') contains '@' && get('age') >= 18)

validations:
  check:
    - get('is_valid') == true
  error:
    code: 400
    message: Invalid email or age

chat:
  prompt: "Process user: {{ get('email') }}, age {{ get('age') }}"

Example 3: session management

actionId: sessionHandler
name: Session Handler
after:
  - set('session_id', get('session_id', 'session') ?? info('sessionId'), 'session')
  - set('visit_count', (get('visit_count', 'session') ?? 0) + 1, 'session')
  - set('last_visit', info('timestamp'), 'session')

apiResponse:
  response:
    session_id: get('session_id')
    visit_count: get('visit_count')
    last_visit: get('last_visit')

See also

• Expressions - Expression syntax and operators
• Unified API - Using get() and set()
• Resources overview - Resource structure
• Validation and control flow - Preflight checks