# Flows

A flow is a composed set of correlated API requests registered from an operation made by the user. A flow can represent any type of operation like adding and deleting a user to a group chat or simply going through a checkout process.

![](/files/FrfJl6XSmeEma8iUnhI5)

You can register flows through the [Test Composer Chrome Extension](https://github.com/loadmill/loadmill-docs/blob/master/test-editor/flows/broken-reference/README.md) or adding the Loadmill User Behavior Module on your server.

When uploading your flow/test scenario to Loadmill, you’ll see the flow added to your test suite on the left side of the platform. By default, the name is the date and time you uploaded your test but make sure to rename it to, most commonly, the name of the operation you composed to a test.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LHDbUNdi3wPd9vSolzU%2Fuploads%2F2t1LeTvaYQ4Za9CHc1XM%2Frunning-1.mp4?alt=media&token=6a52489f-11ae-473e-a0c6-afbb3fd34434>" %}


---

# 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.loadmill.com/test-editor/flows.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.