> For the complete documentation index, see [llms.txt](https://learn.getsparrow.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.getsparrow.co/features/events/building-an-event.md).

# Building an Event

Sparrow allows you to build events in a variety of ways, both manually and imported from a variety of sources.  Here's how.

{% hint style="info" %}
Need a step-by-step walkthrough? See our [quickstart guide.](/quick-start/building-an-event.md)
{% endhint %}

## Manually

{% embed url="<https://www.youtube.com/watch?v=agNxLqqsMp0>" %}

1. Navigate to the "Events" section.
2. In the upper right corner click the "+ Add New" button.
3. Fill out the form with your event information.
4. As you fill out information more fields will appear. Continue to fill in any information you currently have.
5. You will be able to add Headliner/Support, ticket prices/links, stage, capacity, presale info, budget, event links, genre, and assets.
6. Check out the video below to see how it's done!


---

# 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://learn.getsparrow.co/features/events/building-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.