> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/device-management/your-data-flow.md).

# Data Flows

This page describes the basic functionality and principles of data flows

**Data Flows** define how the device data is processed and stored in akenza.

There are three basic components that all together form the **Data Flow:**

* Device Connectors
* Device Types
* Output Connectors

### Device Connectors

Device connectors hold the information on how a device communicates with akenza. They define the secret, which is used to authenticate the received data of a device.

If an **Integration** is available, a device connector has already been created during the setup of an integration. The connectivity provider platform also has been configured to correctly send the data to akenza.

{% content-ref url="/pages/-MQI9E7aPT1CHWVEN5qe" %}
[Device Connectors](/device-management/your-data-flow/device-connector.md)
{% endcontent-ref %}

### Device Types

Device types define how the received uplink is structured, parsed, and finally stored in the akenza database. A variety of predefined **Device Types** are available.\
A **Custom Device Type** can be created, if not the right device type is available for the desired device.

{% content-ref url="/pages/-MQI9SygRqYDEMCJEXAm" %}
[Device Types](/device-management/your-data-flow/device-type.md)
{% endcontent-ref %}

### Output Connectors

Output connectors define the behavior after the device type has parsed the uplink payload. There are a variety of predefined actions that can be chosen from.\
Webhooks can be used to communicate with 3rd party **REST APIs**.

{% content-ref url="/pages/-MQICL3-1RzGgsAcos2h" %}
[Output Connectors](/device-management/your-data-flow/connectors.md)
{% endcontent-ref %}

![Data Flow](https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2Fgit-blob-68305c2628e793008e17396b9b950be54e42b6e9%2Fimage.png?alt=media)


---

# 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.akenza.io/device-management/your-data-flow.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.