> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/convert/forms/forms-tutorial-videos/forms-creating-won-opportunities-in-an-event.md).

# Forms - Creating Won Opportunities in an Event

Participating in in-person events is an excellent opportunity to generate new leads and strengthen relationships with potential customers. However, ensuring that the data collected during the event is properly used in the sales funnel requires organization and automation. With that in mind, this article will show you how to automate the lead capture and qualification process using SprintHub’s native form during an event.

Here, we will teach how to configure specific actions in the form to identify when a sale is made on-site, using a custom field that, when checked, triggers an automation in the CRM. 

This approach ensures that the most qualified contacts receive the ideal treatment, optimizing the work of the sales team and increasing the chances of conversion.

Check out the tutorial:

{% embed url="<https://youtu.be/CysBJfKn_l8>" %}

<br>


---

# 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://docs.sprinthub.com/en/topics/convert/forms/forms-tutorial-videos/forms-creating-won-opportunities-in-an-event.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.