> 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/linking-forms-to-events.md).

# Linking forms to events

Once you've built a form, you can link it to one or more events. Linking a form to an event is what turns a standalone lead capture form into an event-specific application with product selection and booth checkout.

## How It Works

Forms in Vendor Space can serve two purposes:

| Mode             | How Vendors Access It          | What Happens                                                            |
| ---------------- | ------------------------------ | ----------------------------------------------------------------------- |
| **Standalone**   | Direct link or embed code      | Form captures lead data only -- no event context, no product selection  |
| **Event-linked** | Through a published event page | Form captures lead data, then presents product selection for that event |

The form itself is the same in both cases. The difference is how the vendor reaches it. When a vendor accesses a form through a public event page, Vendor Space automatically adds the event context and shows available products after the form is submitted.

## How to Link a Form to an Event

1. Open the form you want to link by navigating to **Forms** in the sidebar and selecting it.
2. Click the **Link to Event** button.
3. A list of your events will appear. Select one or more events to link the form to.
4. Click **Save** to confirm.

The form is now associated with those events. When vendors visit a published event page, they will see the form and can submit their information. After submitting, they are presented with the event's available products (booths, add-ons) to continue with their application.

## Linking One Form to Multiple Events

A single form can be linked to as many events as you like. This is especially useful when you run recurring events and want vendors to use the same application each time.

For example, you might create a "Vendor Application" form and link it to your Spring Market, Summer Market, and Holiday Market events -- all using the same set of questions. Each event page will show the same form but with that event's own product options.

> **Tip:** If different events require different information from vendors, consider creating separate forms tailored to each event rather than using one generic form for everything.

## Unlinking a Form from an Event

1. Open the form.
2. In the linked events list, click the unlink or remove icon next to the event you want to disconnect.
3. The form will no longer appear on that event's public page.

Unlinking a form does not delete any submissions that have already been received. All existing submission data is preserved.

## When Do Vendors See the Form?

Vendors see linked forms on an event page only when the event is **published**. If your event is still in draft, the form will not be visible to the public, even if it is linked.

The form's standalone direct link and embed code always work regardless of event status.

> **Tip:** Before publishing your event, preview the public event page to make sure your linked forms look the way you expect and that all the right questions are included.


---

# 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/linking-forms-to-events.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.