> For the complete documentation index, see [llms.txt](https://docs.helmut.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.cloud/high5/spaces-in-high5/events.md).
# Events
An event is a starting point for one or multiple streams. All streams that are to be found underneath one event will execute in the order of their listing (starting at the top), once the event has been triggered (e.g. by an [event webhook](/high5/spaces-in-high5/webhooks.md)).
The switches next to the streams enable or disable the single stream for this event. In a modularly built stream execution, you could switch off certain parts of your workflows by simply disabling the stream which provides the function(s) you want to stop executing. This also helps in debugging complex workflows.
* To add a stream to an event, use the "*+ Add Stream*" button in the lower left corner of the list
* To edit a stream, use the pencil icon and enter StreamDesignerStudio
* To duplicate a stream, use the paper-sheets icon
* To delete the stream, use the trash-bin icon
---
# 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.helmut.cloud/high5/spaces-in-high5/events.md?ask=&goal=
```
`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.