# `JoobQ.Workflow.Ref`
[🔗](https://github.com/azutoolkit/joobqui/tree/master/sdks/elixir/blob/main/lib/joobq/workflow/ref.ex#L2)

A reference to data a workflow node reads, a `${...}` path the gateway and the engine know: the run's input
(`input/0,1`), a step's output (`output/1,2`), the update being handled (`update_input/0,1`) or any path
(`ref/1`, also `${signals...}` and `${updates...}`). Build them with the functions of `JoobQ.Workflow`.

A key is a name (atom or string), a dotted path of names, or a list index (a non-negative integer); each segment
is ASCII letters, digits, `_`, `-`, `:`, `[` or `]`, as the gateway takes them. A step name may not contain `.`.

# `t`

```elixir
@type t() :: %JoobQ.Workflow.Ref{expr: String.t()}
```

# `references`

```elixir
@spec references(term()) :: [String.t()]
```

The references a node's input makes, in a stable order: maps are walked by key (sorted), lists and tuples in order
(keyword lists included), each reference once. The gateway keeps them as sent and they are part of the blueprint's version.

# `steps`

```elixir
@spec steps(term()) :: [String.t()]
```

The steps the references of `spec` read (`${steps.<name>...}`).

---

*Consult [api-reference.md](api-reference.md) for complete listing*
