> 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 are functional modules that resemble pseudocodes and form the building blocks of every integration.

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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dckapintegrator.com/project-manager/advanced/flows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.