Data access

How to reference dynamic data in Agent Builder steps. Trigger payloads, app secrets, step outputs, and platform context.

Steps use {{}} syntax to reference dynamic data from the trigger, app configuration, and previous step outputs. You can use these variables in any step’s parameters, prompts, or conditions.

Available contexts

Context	Syntax	Description
Trigger payload	{{payload.field}}	Data from the event that triggered the agent
Configuration	{{config.field}}	Agent-level configuration values
Secrets	{{secrets.field}}	App secrets (API keys, tokens)
Step output	{{steps.step_id.field}}	Output from a completed step
Iteration	{{iteration.item.field}}	Current item in a map step
Platform	{{platform.field}}	Platform-level context

Nested access

Variables support dot notation for nested fields:

{{payload.customer.email}}
{{steps.fetch-order.output.line_items}}
{{iteration.item.product.name}}

Example

An agent triggered by ORDER_CONFIRMED might use:

{
  "to": "{{payload.customer_email}}",
  "subject": "Order #{{payload.order_uid}} confirmed",
  "body": "Thank you, {{payload.customer_name}}. Your total is {{payload.total_amount}}."
}

Common patterns

Send notification on order

Trigger: ORDER_CONFIRMED

1. Send email

   App action: send email to {{payload.customer_email}}

2. Notify Slack

   App action: post to Slack #orders channel

Abandoned cart follow-up

Trigger: CART_CREATED

1. Wait

   Delay: 24 hours

2. Check conversion

   Choice: check if {{payload.cart_uid}} has been converted to an order

3. Send reminder

   App action: if not converted, send a reminder email

VIP order routing

Trigger: ORDER_CREATED

1. Analyze customer

   AI reasoning: analyze customer order history and determine VIP status

2. Branch on VIP status

   Choice: branch on {{steps.vip-check.output.is_vip}}

3. Route order

   App action (VIP path): assign to priority fulfillment queue. App action (standard path): standard fulfillment.