> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/page-flow/references/value-types.md).

# Value Types

In Page Flow/Cloud Flow the Output blocks send out values with a certain type and the Value Parameters within blocks accept data again of certain types. The following table describes the available types:

<table><thead><tr><th width="126">Type</th><th>Description</th></tr></thead><tbody><tr><td>text</td><td>Any textual data including letters, numbers, special characters, etc.</td></tr><tr><td>numeric</td><td>Numeric data including <a href="https://en.wikipedia.org/wiki/Integer">integers</a> and <a href="https://en.wikipedia.org/wiki/Real_number">real numbers</a>.</td></tr><tr><td>object</td><td>An entity containing named properties and their values.</td></tr><tr><td>list</td><td>Collection of values</td></tr><tr><td>boolean</td><td>A binary value e.g. <em>true</em> or <em>false</em> / ON or OFF/ yes or no / etc</td></tr><tr><td>element</td><td>An entity that represents an element on a page or form</td></tr><tr><td>any</td><td>A generic value that can be of any of the above types</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zingy.ai/app-editor/page-flow/references/value-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.