Insert a value
Use {{ event.field }} in message fields that support templates. Select an example and use the field picker to copy its exact path. A source’s fields differ from those of other sources.
Nested fields use dots, and array positions start at zero: {{ event.logs.0.address }}. The input.event and input.actions aliases also work in templates.
Use an earlier action
Outputs use actions followed by the action type and its count within the path, such as actions.transform_1 or actions.agent_1. The inspector shows the current key.
Only earlier outputs from this path are available. Reordering two actions of the same type or deleting one can change the numbering. Retest downstream messages after editing.
Arithmetic and missing values
Templates support arithmetic on numeric values. Division keeps up to 18 fractional digits and truncates. For example, {{ event.value_decimal / 1000 }} expresses an amount in thousands.
An unknown field renders empty and is reported as unresolved in previews. Division by zero or a nonnumeric operand also cannot produce a valid value. Fix these warnings before enabling; they are not automatically replaced with useful fallback text.
Optional data
Inspect several examples where possible. A sale price, USD estimate, or metadata field present on one event may be absent on another. Use Transform to produce fallback text when your message needs it.
In a batch, use event.count, event.events, and batch summary fields. Do not assume a single transfer’s transaction link or wallet fields exist at the top level.