> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/flow-interaction-output-variables.md).

# Flow Interaction Output Variables

## Overview

Every interactive Avonni Flow Screen Component exposes a single output attribute named **Flow Interaction Output Variables** (`flowInteractionOutputVariables`). It is a set of ten generic slots — **Variable 1** through **Variable 10** — that let you pass data **back to your screen flow** from a flow you launched through an interaction.

You don't set these slots directly. They are filled by the [**Open Flow Dialog**](/flow/component-builder/interactions-panel/open-flow-dialog.md) and [**Open Flow Panel**](/flow/component-builder/interactions-panel/open-flow-panel.md) interactions when the launched flow finishes — so the same component that opened the flow also carries its results.

***

## How it works

1. **Launch a flow** from the component using an **Open Flow Dialog** or **Open Flow Panel** interaction.
2. In the launched flow, mark the variable you want to return as **Available for Output**.
3. In the interaction's **Output Variables** setting, add a row that maps:
   * **Name** — the launched flow's output variable **API Name** (must match exactly).
   * **Variable Number** — the slot (1–10) where the returned value is stored.
4. When the launched flow **finishes**, each mapped value lands in its slot. Every slot is a **typed holder** (the `FlowInteractionOutputVariable` Apex type) that stores the value in the field matching its type — text, number, boolean, date, date/time, or a collection of those.

## Reading a slot in your flow

A slot (`variable1`…`variable10`) is **not a bare value** — it is a typed holder. To read it, append the property that matches the **type of the value you assigned** to that slot. For example, if Variable 1 holds a Boolean:

```
{!<ComponentName>.flowInteractionOutputVariables.variable1.booleanValue}
```

Pick the property by the value's type:

| If the value is… | Single value    | Collection (Allow Multiple Values) |
| ---------------- | --------------- | ---------------------------------- |
| **Text**         | `textValue`     | `textCollectionValue`              |
| **Number**       | `numberValue`   | `numberCollectionValue`            |
| **Boolean**      | `booleanValue`  | `booleanCollectionValue`           |
| **Date**         | `dateValue`     | `dateCollectionValue`              |
| **Date/Time**    | `dateTimeValue` | `dateTimeCollectionValue`          |

In the Flow Builder value picker, drill into the component → **Flow Interaction Output Variables** → the **Variable Number** you chose → the typed property above. Use it in decisions, assignments, or any later element like any other flow variable.

{% hint style="warning" %}
The property you read must match the type of the value you assigned to that slot. These slots hold only text, number, boolean, date, date/time, and collections of those — **Salesforce records (SObjects) are not supported**. To return a record from a launched flow, output its fields as individual scalar values (or its Id as Text).
{% endhint %}

## Notes

* **API Names must match exactly** between the launched flow's output variable and the **Name** you enter in the interaction.
* The launched flow variable must be marked **Available for Output**.
* Output capture from **Open Flow Panel** requires Avonni Components package **v6+**.
* A component exposes the same ten slots regardless of type — assign a distinct **Variable Number** to each output you capture so they don't overwrite one another.

## Related

* [Open Flow Dialog](/flow/component-builder/interactions-panel/open-flow-dialog.md)
* [Open Flow Panel](/flow/component-builder/interactions-panel/open-flow-panel.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/flow-interaction-output-variables.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.