Dynamic variables in JSON and text

Choose a nested field or list item

1. Open a command value or function output and choose JSON, Text or multiline text.

2. Place the cursor where the reference belongs. Select existing text or a JSON field value if you want to replace it.

3. Click Insert variable below the editor.

4. Search for a variable, field or item. For example, search payload.items to find payload.items[0].sku.

5. Choose the reference and click Insert. Continue editing, then save the command or output.

   

Object fields use dots: payload.customer.name. List items use an index: payload.items[0].sku is the first item's SKU; [1] is the second item. Parent objects and lists remain selectable when you want the complete value.

The picker uses the current workflow scope. A variable created later, inside another branch, or by a disabled command is not offered. Earlier variables can have fields defined with the Object/List editors or inside JSON, including fields whose current value is null. Choosing a field inserts its reference, not its current value.

For example, an earlier Create Variable command can define a JSON variable called payload:

{

  "customer": { "name": "Ada", "address": { "city": "London" } },

  "items": [

    { "sku": "FIRST", "quantity": 3 },

    { "sku": "SECOND", "quantity": 1 }

  ],

  "enabled": false,

  "optional": null

}

The picker can then offer payload.customer.address.city, payload.items[0].quantity, payload.items[1].sku, payload.enabled and payload.optional, as well as their parent values.

Build a dynamic JSON value

Place the cursor inside a JSON text value, or select a complete value within an object or list. The picker supplies the required quotes and enables Resolve variables when insertion succeeds.

You can also enter references manually, keeping them inside JSON strings:

{

  "quantity": "{{ payload.items[0].quantity }}",

  "first_sku": "{{ payload.items[0].sku }}",

  "message": "Hello {{ payload.customer.name }}",

  "enabled": "{{ payload.enabled }}",

  "optional": "{{ payload.optional }}"

}

With the example data above, the result is:

{

  "quantity": 3,

  "first_sku": "FIRST",

  "message": "Hello Ada",

  "enabled": false,

  "optional": null

}

A complete placeholder preserves its value's type, including objects, lists, numbers, booleans and null. A placeholder mixed with other text produces text. Use complete placeholders for objects and lists; they cannot be inserted into a longer sentence.

Leave Resolve variables off to keep JSON literal. Existing saved JSON stays literal until you enable resolution or successfully insert a reference. Cancelling the picker leaves the contents and setting unchanged. JSON field names remain literal; the picker does not insert references into keys. To use a variable as the entire output, choose the Variable type instead of JSON.

Compose text with references

In a Text or multiline text value, position the cursor or select text to replace, then use Insert variable. Surrounding words and punctuation are preserved.

For example, choose payload.customer.name after Hello to create Hello {{ payload.customer.name }}!. With the example data, the result is Hello Ada!. A function input named customer_name appears as $inputs.customer_name; the picker adds that prefix for you. Text values do not need the JSON Resolve variables checkbox.

Available fields and safe use

The picker discovers fields from declared object/list shapes, local JSON definitions and available database result schemas. Literal lists expose their defined indexes. For a list described only by a schema, [0] is a suggested first item, not a guarantee that the list contains data. Check that a result exists before reading an optional field or list item.

Fields known only when an HTTP request, connector or other command runs cannot be discovered from an unspecified shape. You can still enter a known path manually, or use an earlier structured variable. Large or deeply nested shapes have bounded suggestions to keep the editor responsive.

References use field names and fixed non-negative list indexes. Calculations, function calls and variable indexes are not supported inside JSON placeholders. Calculate a value in an earlier command, then reference its result. A missing reference stops the command with an error; an existing null is preserved. Quotes and line breaks in referenced values are handled automatically, and inserted text is not expanded a second time.

Static, global-value and secret-value editors do not offer the picker. Server workflows can reference available workspace secret names without displaying their values. Workspace secrets are unavailable to page workflows. For page workflows, use a qualified input such as $inputs.name or a distinct variable name such as customerName when a bare name conflicts with a browser global.

See Variables for creating and editing variables, and Global variables for shared values.