> For the complete documentation index, see [llms.txt](https://docs.videsk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videsk.io/es-dashboard/formularios/crear-un-formulario.md).

# Crear un formulario

## 1. Accede al dashboard con tu cuenta de administrador

Para crear un formulario, primero debes **iniciar sesión** en [**Dashboard Videsk**](https://app.videsk.io) con tu cuenta de administrador.

## 2. Accede a "Formularios" y crea uno nuevo

A continuación dirígete al menú principal **Formularios** y **selecciona el botón celeste (+).** Se abrirá una ventana emergente donde debes **asignar un nombre** (es obligatorio para todos los formularios) y una **descripción** (esta es opcional).

![](https://707854291-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ma4PSLcae00pEGrc2J6%2F-MeackT3qj2z7OEUkn4G%2F-MeflvdP2qBh5sVpvMlV%2F03%20-%20Creaci%C3%B3n%20de%20formularios%20-%20crea%20un%20nuevo%20formulario.png?alt=media\&token=f6431426-ca69-4ee4-b3b8-814ead42af81)

![](https://707854291-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ma4PSLcae00pEGrc2J6%2F-MeackT3qj2z7OEUkn4G%2F-Mefb89VGh4lWy8vPOGk%2F04%20-%20crear%20nuevo%20formulario_edited_v2.png?alt=media\&token=7d4c67dc-d413-4334-919c-ae8640b6e25c)

## 3. Edita tu formulario recién creado

Por defecto, los formularios recién creados traen dos campos predefinidos como Nombre e e-mail. Pero puedes eliminarlos y crear tus propios campos.

![](https://707854291-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ma4PSLcae00pEGrc2J6%2F-MeackT3qj2z7OEUkn4G%2F-MefeSNNP2m4VvJ6pFxp%2F05%20-%20Formulario%20reci%C3%A9n%20creado%20-%20campos%20por%20defecto%20-%20form%20builder.png?alt=media\&token=4838440c-901b-4bb0-851d-26739453cbae)

Para añadir nuevos campos, sólo debes tomar los elementos y arrastrarlos al área de trabajo, tal como muestra la imagen a continuación.

![](https://707854291-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ma4PSLcae00pEGrc2J6%2F-MeackT3qj2z7OEUkn4G%2F-Mefebsp4utMz-70arcf%2F06%20-%20espacio%20de%20trabajo%20drag%20and%20drop.png?alt=media\&token=8053e749-5055-4a62-96cd-84ad4e4e34f6)

## 4. Guardar cambios realizados en el formulario

Para guardar los cambios debes presionar el botón celeste de la parte superior izquierda del formulario **Guardar cambios.**

![](https://707854291-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ma4PSLcae00pEGrc2J6%2F-MeackT3qj2z7OEUkn4G%2F-MefkjEetwCA5DmgiYK5%2F07%20-%20no%20olvides%20guardar%20los%20cambios.png?alt=media\&token=5b576c55-2192-459d-8a7d-5758444bf74c)

Conoce los [**tipos de campos disponibles para crear formularios en Videsk →**](https://docs.videsk.io/es-dashboard/formularios/tipos-de-campos.md)

{% hint style="warning" %}
**Es requisito que la cuenta tenga vinculado un proveedor de captcha**, esto evitará el envío masivo de información por parte de bots de terceros.
{% endhint %}


---

# 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.videsk.io/es-dashboard/formularios/crear-un-formulario.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.
