> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/project-manager/advanced/flows.md).

# Flows

Flows act as the neural schema for system integration, and carry out the whole integration logic end to end. The Flow is responsible for making API calls to the targeted system, formatting and validating data, logging transactions, and so on.

The Flows landing page contains the following information in tabular form: 

| Title          | Name of the Flow                                    |
| -------------- | --------------------------------------------------- |
| Description    | Brief description of the Flow                       |
| Created By     | The user who created the Flow                       |
| Status         | Displays if the Flow is in Active or Inactive state |
| Open Simulator | To simulate the Flow. Used for testing purposes     |

For detailed information on [Flows and Handlers, click here.](/developers/flows.md)


---

# 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.dckapintegrator.com/project-manager/advanced/flows.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.