> For the complete documentation index, see [llms.txt](https://docs.renderdraw.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.renderdraw.us/usage-scenarios/use-cases/2d/data-interaction-within-a-flow.md).
# Data interaction within a Flow
### From the Configuration of the scene, make sure you setup the scene for use within a Lightning flow
1. Ensure you have the show next option selected; this will allow the user to see the proceed button (shown as save)
**a.** Optionally set the text and the icon for the next button. The icons are available at
2. Check the "Use with Lightning flow" option to ensure that when a user presses proceed, the Canvas object is generated and sent to the next step of the lightning flow
3. The Next button has been displayed to the user for interaction.
{% hint style="info" %}
You can redirect the user flow to the 2D canvas within a flow if you modify the Canvas object properties. The canvas will redraw based on the properties passed
{% endhint %}
Our interactions pass a apex object back and forth, and this object is detailed here:
[Canvas](/api-documentation/data-objects-used-throughout-the-suite/canvas.md)
This Canvas object contains the latest information from the canvas directly.
The standard data flow goes something like this:
Where we are using the Canvas object as a variable and mapping properties from it's sub-objects (in this case, draggable items) into products in a custom configuration scenario.
Setting up a Canvas object is as simple as defining the variable:
and then mapping before and after the canvas interaction
