> For the complete documentation index, see [llms.txt](https://docs.playtavern.com/tavern/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playtavern.com/tavern/core-concepts/entities/flowentity.md). # FlowEntity The Flow Entity is a special Entity. This Entity stores all data associated with the current Flow, allowing for component functions to be chained together. For example, the first component might set a value that the second component can then read. The Flow Entity is created by a Game when a Game is initialized, and exposes the key `playerParams`. All Components can read and write to this Entity to maintain any state associated with the current Flows execution context, such as any parameters passed in by the player or any outputs for the next component. \ \ Conceptually, this Entity behaves as an event bus. It enables a Component to share data, and other Components to retrieve that data. This doesn't happen in parallel, it is very sequential, and requires the configuration of a Flow to account for the data available. --- # 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.playtavern.com/tavern/core-concepts/entities/flowentity.md?ask=&goal= ``` `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.