# Collection

A collection is a way of segregating workflows into sets in order to keep them more organized for every individual. This is totally up to the user and can be treated as having different set of workflows where each set forms a collection with some specific set of tasks. Watch out for custom collections for different domains which will soon launch on YellowAnt.

**If you create a new event triggered workflow and do not select/create a collection, by default it gets added to a collection called workflow.**\
**If you add the workflow to a certain collection, it still makes no difference to the way it is executed (unlike command workflows). In event workflows, it is purely a better way to organize your workflows.**

Example 1:

![](/files/-LCCCGWiZI0IhPJSahoE)

In this case, the event workflow will add to the collection "workflow" since we did not select/create any collection.

Example 2:

![](/files/-LCCCIVu4wVNemmcre1S)

In this case, the event workflow will add to the collection "demo-collection".


---

# Agent Instructions: 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:

```
GET https://docs.yellowant.com/workflows/event-workflows/building-event-workflows/collection.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.