> 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/toolbox-blocks/popup-form-data.md).

# Popup Form Data

{% hint style="info" %}
**Block Information**

Available in: Page Flow

Toolbox Category: Action

Block Type: [Output](/app-editor/page-flow/block-anatomy.md#output-block)

Output Type: [*object*](/app-editor/page-flow/references/value-types.md)
{% endhint %}

**`Popup Form Data`** is an [output block](/app-editor/page-flow/block-anatomy.md#output-block) that provides the data entered by the user when using the [Show Popup Form](/app-editor/page-flow/toolbox-blocks/show-popup-form.md) block. The output is of type [*object*](/app-editor/page-flow/references/value-types.md) and is compatible with [Value Parameters](/app-editor/page-flow/block-anatomy.md#value-parameters) of type [*object*](/app-editor/page-flow/references/value-types.md) or of type [*any*](/app-editor/page-flow/references/value-types.md).

<div align="left"><figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FwwZRxheTdgioTcDon97z%2Fimage.png?alt=media&amp;token=7cfe379b-6574-472e-af0f-1a8709b4c754" alt="" width="295"><figcaption><p>Popup Form Data block</p></figcaption></figure></div>

{% hint style="warning" %}
The Popup Form Data block only works when used inside the *Save Success Tasks* and/or the *Form Close Success Tasks* [flow parameters](/app-editor/page-flow/block-anatomy.md#flow-parameters) of the [Show Popup Form](/app-editor/page-flow/toolbox-blocks/show-popup-form.md) block.
{% endhint %}

***

## Usage Example

The image below shows an example of the Popup Form Data block used inside the *Form Close Success Tasks* [flow parameter](/app-editor/page-flow/block-anatomy.md#flow-parameters) of the [Show Popup Form](/app-editor/page-flow/toolbox-blocks/show-popup-form.md) block.

The [Set Content block](/app-editor/page-flow/toolbox-blocks/set-content.md) is used to set the content of an element on the page to the `Name` property of the object representing the data entered by the user.

<figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FxYn0emzaTqC1JkbdhRpP%2Fimage.png?alt=media&amp;token=1b08bbaf-6a9c-482a-bf89-32560b79b354" alt=""><figcaption><p>Example of Popup Form Data block</p></figcaption></figure>


---

# 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/toolbox-blocks/popup-form-data.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.