afv-library/skills/agentforce-generate/assets/patterns/advanced-input-bindings.agent

# Advanced Input Bindings Pattern
# Demonstrates all parameter binding techniques for Agent Script actions
#
# ★ When To Use This Pattern:
#   - Learning different ways to pass values to actions
#   - Combining LLM slot filling with variable binding
#   - Chaining outputs between multiple actions
#   - Complex multi-input action scenarios
#
# ★ Key Insight:
#   - `...` (ellipsis) = LLM extracts value from conversation (slot filling)
#   - `"value"` = Fixed constant value
#   - `@variables.x` = Value from stored state
#   - `@outputs.x` = Value from previous action's output
#
# ★ Common Use Cases:
#   - Order lookup with user-provided order ID
#   - Multi-step workflows with data passing
#   - Conditional parameter binding
#
# This is a COMPLETE template - customize action targets and metadata.

system:
    instructions: |
        You are an order-processing assistant. Use slot filling for safe values
        present in the conversation, literals only for real constants, and
        stored state only for canonical action results required later.
    messages:
        welcome: "Hello! I can demonstrate safe order input bindings."
        error: "I couldn't process that request."

access:
    default_agent_user: "agent@company.salesforce.com"

config:
    developer_name: "Advanced_Input_Bindings_Agent"
    agent_label: "Advanced Input Bindings"
    description: "Demonstrates slot, literal, canonical-state, and action-output bindings"

variables:
    current_account_id: mutable string = ""
        description: "Canonical account ID returned by account resolution and required by later actions"

language:
    default_locale: "en_US"

start_agent order_processing:
    label: "Order Processing"
    description: "Demonstrates advanced input binding patterns"

    actions:
        # Action with multiple input types
        process_order:
            description: "Process an order with various input methods"
            inputs:
                order_id: string
                    description: "The order ID to process"
                amount: object
                    description: "Transaction amount in USD"
                    complex_data_type_name: "lightning__doubleType"
                account_id: string
                    description: "Customer account ID"
            outputs:
                confirmation_number: string
                    description: "Order confirmation number"
                processed_amount: object
                    description: "Final processed amount"
                    complex_data_type_name: "lightning__doubleType"
            target: "flow://Process_Order"

        get_account:
            description: "Look up account details"
            inputs:
                account_id: string
                    description: "Account ID to look up"
            outputs:
                account_name: string
                    description: "Account name"
                credit_limit: object
                    description: "Available credit"
                    complex_data_type_name: "lightning__doubleType"
            target: "flow://Get_Account_Details"

        resolve_account:
            description: "Resolve the account named by the user to a canonical account ID"
            inputs:
                account_reference: string
                    description: "Account name or reference from the conversation"
            outputs:
                account_id: string
                    description: "Canonical account ID"
            target: "flow://Resolve_Account"

        send_notification:
            description: "Send order notification"
            inputs:
                confirmation_number: string
                    description: "Order confirmation to include"
                recipient_account: string
                    description: "Account to notify"
            outputs:
                sent: boolean
                    description: "Whether notification was sent"
            target: "flow://Send_Order_Notification"

    reasoning:
        instructions: ->
            | Help the customer process their order.
            |
            | INPUT BINDING EXAMPLES:
            | 1. Slot filling (...) - LLM extracts from conversation
            | 2. Fixed values - Always use a constant
            | 3. Stored state - Use the available value
            | 4. Output chaining - Use results from previous action
            |
            | Ask for order details and process appropriately.

        actions:
            # Persist only a canonical action output that later bindings consume.
            resolve_account: @actions.resolve_account
                with account_reference=...
                set @variables.current_account_id = @outputs.account_id

            # ★ PATTERN 1: Slot Filling (LLM extracts from conversation)
            # User says "Process order ORD-12345" -> LLM fills order_id="ORD-12345"
            slot_fill_lookup: @actions.process_order
                with order_id=...
                with amount=...
                with account_id=...

            # ★ PATTERN 2: Fixed Value (constant)
            # Always uses the same account for default lookups
            fixed_account: @actions.get_account
                with account_id="001DEFAULT000001"

            # ★ PATTERN 3: Variable Binding (from stored state)
            # Uses the canonical account ID returned by resolve_account
            variable_binding: @actions.get_account
                with account_id=@variables.current_account_id
                available when @variables.current_account_id != ""

            # ★ PATTERN 4: Output Chaining (from previous action)
            # Uses confirmation_number from process_order to send notification
            chained_output: @actions.process_order
                with order_id=...
                with amount=...
                with account_id=@variables.current_account_id
                run @actions.send_notification
                    with confirmation_number=@outputs.confirmation_number
                    with recipient_account=@variables.current_account_id
                available when @variables.current_account_id != ""

            # ★ PATTERN 5: Mixed Binding (combining patterns)
            # Some inputs from LLM, some from variables, some fixed
            mixed_binding: @actions.process_order
                with order_id=...                              # LLM slot fills
                with amount=...                                # LLM slot fills
                with account_id="001INTERNAL00001"              # Fixed value

# ★ Insight: Binding Pattern Decision Tree
#
# Need the LLM to extract from conversation?     -> Use `...`
# Value is always the same constant?             -> Use "value"
# Value was captured in a previous step?         -> Use @variables.x
# Value comes from another action's output?      -> Use @outputs.x (in callback)
#
# ★ Common Mistake: Using @outputs.x outside of a `run` callback
# @outputs.x is only available inside the action's callback chain
# Store important outputs in @variables for use elsewhere