> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/forms/creating-a-form.md).

# Creating a form

Forms are the foundation of how you collect information from vendors. Whether you need vendor applications, booth preferences, or product details, creating a form takes just a few minutes.

## Getting Started

1. Click **Forms** in the left sidebar to open the Forms section.
2. Click the **Create Form** button in the top-right corner.
3. Enter a **name** for your form (for example, "Vendor Application - Summer Market 2026").
4. Optionally, add a **description** to help you and your team remember the form's purpose.

## Building Your Form

Once your form is created, you'll land in the drag-and-drop form builder.

### Adding Fields

1. Browse the list of available field types in the left panel.
2. Drag a field type onto your form, or click it to add it to the bottom.
3. Give the field a **label** (this is what vendors will see).
4. Optionally, add **placeholder text** or **help text** to guide vendors.

### Reordering Fields

* Drag any field up or down to change its position on the form.
* Fields appear to vendors in the exact order you arrange them.

### Setting Required Fields

* Toggle the **Required** switch on any field to make it mandatory.
* Required fields are marked with an asterisk (\*) so vendors know they must fill them in before submitting.

### Removing Fields

* Click the delete icon on any field to remove it from the form.
* Removing a field does not affect submissions that have already been received.

### Conditional Logic

You can show or hide fields based on a vendor's previous answers. This keeps forms short and relevant -- vendors only see the questions that apply to them.

To add a condition to a field:

1. Click on the field you want to make conditional.
2. In the field settings panel, look for the **Show this field when...** section.
3. Select the **field** whose answer should control visibility.
4. Choose an **operator** (equals, does not equal, contains, is empty, is not empty).
5. Enter the **value** to compare against. For select or radio fields, you can pick from the existing options.

Fields with a condition show a **Conditional** badge in the form builder so you can see which fields are dynamic at a glance.

**How it works for vendors:**

* When a vendor fills out the form, conditional fields appear or disappear instantly based on their answers.
* Hidden fields are skipped during validation -- vendors are never blocked by a required field they cannot see.
* Hidden field values are excluded from the submission data automatically.

**Example:** Add a select field asking "Do you need electricity?" with options Yes and No. Then add a number field for "How many outlets do you need?" with a condition: show when "Do you need electricity?" equals "Yes." Vendors who select No will never see the outlets question.

> **Tip:** Conditional logic works with text, select, radio, and checkbox fields as the trigger. Use it to branch your form into different paths based on vendor type, product category, or any other distinguishing answer.

## Saving Your Form

Your form saves automatically as you build it. You can close the builder at any time and come back to make changes later.

> **Tip:** Start with the essentials -- company name, contact email, and the information you truly need. Shorter forms tend to get more responses. You can always add more fields later.

## What's Next

After creating your form, you can:

* [Link it to one or more events](/docs/forms/linking-forms-to-events.md) so it appears on your public event pages.
* [Embed it on your own website](/docs/forms/embedding-on-your-website.md) for a seamless experience.
* [Review submissions](/docs/forms/reviewing-submissions.md) as they come in.


---

# 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, and the optional `goal` query parameter:

```
GET https://vendorspace.gitbook.io/docs/forms/creating-a-form.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.