# Set Form Event Status Message

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

Available in: Page Flow

Toolbox Category: Form

Block Type: [Regular](/app-editor/page-flow/block-anatomy.md#regular-block)
{% endhint %}

The **`Set Form Event Status Message`** block is used to show a message to the user.&#x20;

<div align="left"><figure><img src="/files/Pis3TNLGPLb9p1M6jJsg" alt="" width="374"><figcaption><p>Set Form Event Status Message block</p></figcaption></figure></div>

The block's behavior varies based on the context in which it's used, as outlined below:

* Within the [Form Events block's](/app-editor/page-flow/toolbox-blocks/form-events.md) *Submit Tasks*, *Success Tasks* and *Error Tasks* [flow parameter](/app-editor/page-flow/block-anatomy.md#flow-parameters) context, this block will replace the form's customized success and error messages. In this scenario, it's advisable to employ the [Alert Text](/app-editor/page-flow/toolbox-blocks/alert-text.md) block to convey your message.
* Outside the [Form Events block's](/app-editor/page-flow/toolbox-blocks/form-events.md) *Submit Tasks*, *Success Tasks* and *Error Tasks* [flow parameters](/app-editor/page-flow/block-anatomy.md#flow-parameters) context, the message will appear in the form's general status section. Here, it's recommended to utilize the [Alert Text](/app-editor/page-flow/toolbox-blocks/alert-text.md) block in its *dismissible* setting to showcase your message.

The block consists of a [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts an [text](/app-editor/page-flow/references/value-types.md) value containing the message.

{% hint style="warning" %}
This block only works when used in *Form* type pages. See [Working With Forms](/app-editor/page-editor/working-with-forms.md) to learn about how forms work.
{% endhint %}

***

## Usage Example

The image below shows an example of the **`Set Form Event Status Message`** block.

<figure><img src="/files/AaS6szY8ZTopxyQTKTb3" alt=""><figcaption><p>Set Form Event Status block example 1</p></figcaption></figure>

In the above case, since the block is used outside of the [Form Events block's](/app-editor/page-flow/toolbox-blocks/form-events.md) *Submit Tasks*, *Success Tasks* and *Error Tasks* [flow parameter](/app-editor/page-flow/block-anatomy.md#flow-parameters) context, the message will appear in the form's general status section as shown in the image below.

<figure><img src="/files/OrXuWXjUg52zygZY8hgn" alt=""><figcaption><p>Result of example 1</p></figcaption></figure>

For the next example, we will use the **`Set Form Event Status Message`** block inside the [Form Events block's](/app-editor/page-flow/toolbox-blocks/form-events.md) *Success Tasks* [flow parameter](/app-editor/page-flow/block-anatomy.md#flow-parameters) as shown in the image below.

<figure><img src="/files/ZKEAZUj2onn52rjVfN91" alt=""><figcaption><p>Set Form Event Status block example 2</p></figcaption></figure>

This time the message provided replaces the customized success message and is displayed after the form was submitted successfully.&#x20;

<figure><img src="/files/wpWonFAVq8NTkWFsExsx" alt=""><figcaption><p>Result of example 2</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.zingy.ai/app-editor/page-flow/toolbox-blocks/set-form-event-status-message.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
