> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Dynamic values

> Reference data from a Ravenna workflow's trigger and earlier steps with dynamic values: ticket fields and identifiers, email details, action outputs, and loop items.

Use dynamic values to fill a step's inputs with data from the trigger or from earlier steps, so each run works with the ticket, person, or record that started it.

## Data flow model

Data from the trigger and from each action's output is available to downstream steps. Step inputs reference earlier data with dynamic values; they resolve at run time.

* **Trigger data** carries the event context: ticket fields (including Display ID like `BUGZ-123` and Short ID like `abc12345`), requester and actor info, custom field values, timestamps, and event-specific data such as which tags changed or which task completed.
* **Action output** varies by action: created IDs, API response data, Is Success indicators, AI-generated text.
* **Text fields interpolate.** A dynamic value inside a text field is replaced with its text form; text and several values can be mixed.
* **Whole-field values keep their type.** A field set to exactly one dynamic value receives the raw value (number, boolean, list), not a string.

## Scope rules

* A step can reference any ancestor step on its path: the trigger, its parents, and their ancestors.
* Steps on parallel branches can't reference each other.
* A converging step can reference all of its parents. Values from a parent that didn't complete are empty.
* Publish validation rejects references to steps that aren't upstream and to fields that don't exist.

## Missing values

* A reference that can't be resolved at run time becomes empty. In text it becomes blank.
* A required input that resolves to empty fails the step's input validation, so the step fails.
* In a condition on an incoming edge, an unresolvable reference fails that edge, so the step is skipped.
* Read a step's resolved inputs in the run log to see what each reference became.

## Recommendations

* Prefer Display ID in human-facing text and Short ID in URLs. Use Ticket ID only for API calls that need it.
* Use Email Details (Sent To, Recipients, Subject) to route or prioritize email-created tickets that share a channel.
* When a step converges several paths, reference only values from paths that always run, or guard optional ones with a condition.
* Inside a Loop, use the loop item and Loop Info rather than indexing into the original list.


## Related topics

- [Workflows](https://docs.ravenna.ai/documentation/automate/workflows/overview.md)
- [Test a workflow](https://docs.ravenna.ai/documentation/automate/workflows/test.md)
- [Roles](https://docs.ravenna.ai/documentation/tickets/roles.md)
- [Runs and logs](https://docs.ravenna.ai/documentation/automate/workflows/monitor.md)
- [Custom fields](https://docs.ravenna.ai/documentation/tickets/forms/custom-fields.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.