> For the complete documentation index, see [llms.txt](https://help.blings.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blings.io/apps/blings-studio/connectors/submit-form.md).

# Submit Form

Use the Submit Form connector when a viewer action should submit values entered in one or more Input Field connectors. Submission can save values in Blings Form Data or trigger custom handling for an external workflow.

<figure><img src="/files/xD0N1YzYvk436tZOYKCZ" alt="Shared Studio connector detail panel where interaction connector source, fallback, editing access, and internal description controls are configured" width="375"><figcaption></figcaption></figure>

## Options

| Option                   | What it controls                                                           | Notes                                                                     |
| ------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| **Submit layer**         | The button or interactive layer that submits the form.                     | Confirm the layer is visible, clickable, and clearly tied to the form.    |
| **Captured fields**      | The Input Field values included in the submission.                         | Confirm each field has a stable name.                                     |
| **Submission handling**  | Whether values are stored in Blings Form Data or handled with custom code. | Match this to the project's data collection and compliance workflow.      |
| **Validation behavior**  | What should happen when required values are empty or invalid.              | Avoid submitting incomplete values when the workflow depends on them.     |
| **Success state**        | What the viewer sees after submission.                                     | Use a clear next state, message, frame jump, or branch when needed.       |
| **Failure behavior**     | What happens if submission cannot complete.                                | Keep the viewer experience controlled even when an external action fails. |
| **Internal description** | A note explaining where submitted data goes.                               | Useful for operations and QA review.                                      |

## Configure Submit Form

{% stepper %}
{% step %}

### Confirm Input Fields

Make sure every value that should be submitted has an Input Field connector with a clear field name.
{% endstep %}

{% step %}

### Select the Submit Layer

Choose the button, hotspot, or interactive layer that should submit the form.
{% endstep %}

{% step %}

### Choose Submission Handling

Select whether the submission should be saved in Blings Form Data or handled with custom code.
{% endstep %}

{% step %}

### Define Empty and Failure Behavior

Decide what happens when required fields are blank, invalid, or when submission cannot complete.
{% endstep %}

{% step %}

### Preview the Full Flow

Test typing, submitting, success behavior, empty fields, and failure behavior before publishing.
{% endstep %}
{% endstepper %}

## Success Checks

Before publishing a Submit Form connector, confirm:

* The submit layer is clickable in the player.
* Each submitted field has a stable name.
* Empty or invalid values are handled intentionally.
* Form Data or custom handling has been tested.
* The viewer sees an appropriate state after submission.
* Submission does not interfere with other player interactions, links, or analytics.

{% content-ref url="/pages/lt20SZVUbkT6ghpdYk2y" %}
[Input Field](/apps/blings-studio/connectors/input-field.md)
{% endcontent-ref %}

{% content-ref url="/pages/tcTMJOKSy05H4hRxVQ8F" %}
[Data, Catalog, and Forms](/apps/blings-platform/data-catalog-and-forms.md)
{% endcontent-ref %}


---

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

```
GET https://help.blings.io/apps/blings-studio/connectors/submit-form.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.