> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/the-portal-explained/things-manager/iot-devices/flows-tab.md).

# Flows tab

The Flows tab provides a visual and interactive overview of the complete data flow of your device. This view is designed to give you immediate insight into how data from your IoT device is processed and routed. You find this tab on the Device & Connectivity detail page. 

## What you see in the Flows tab

The schematic overview shows the following components of the flow: 

* **Device:** your IoT device sending data
* **Decoders:** Convert the raw payload from the device into readable data
* **Encoders:** Translate the data into a specific format for the Destination
* **Destinations:** The endpoints where the data is sent, such as a webhook, MQTT broker, or cloud platform

The components are visually connected, allowing you to see at a glance how the flow is structured and if/how each element is linked.

<figure><img src="https://1453626848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl6RrePMSAjRvOgcHjMBZ%2Fuploads%2F6omn8RDa18VArNrA6a9n%2FFlows%20DAgraph%20volledig.png?alt=media&amp;token=ff164dcb-167b-4403-95c8-8a87483d3b7a" alt=""><figcaption></figcaption></figure>

## Interactive editing

The Flows tab is not just a visual representation, it is also an editable interface. You can:&#x20;

* Enable or disable components using toggle switches
* Edit components by clicking on the link, which takes you directly to the configuration page &#x20;
* Remove a link, for example the Destination, by clicking the 'X' in the link

## Error detection and warnings

If something goes wrong in the flow the affected component will be highlighted in orange. The visual cue helps you quickly identify where the issue lies. Clicking in the highlighted component (i) provides more details about the problem and suggestions how to fix it. The links in the highlighted component brings you to the configuration page, so you can fix it right away.

Examples of possible issues are:&#x20;

* A required decoder is disabled or missing
* A destination is missing or misconfigured
* There's an incompatability between components

<figure><img src="https://1453626848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl6RrePMSAjRvOgcHjMBZ%2Fuploads%2FhyiKzNXRVHcQ7oMkMDyD%2FDAgraph%20decoder%20fout.png?alt=media&amp;token=bdfea4c3-0692-4991-978d-b21e49f23810" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1453626848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl6RrePMSAjRvOgcHjMBZ%2Fuploads%2FFozHsA3cww4ppD4bLDZq%2FDAgraph%20destination%20fout.png?alt=media&amp;token=c04239ab-0226-42b4-bcb0-f589f3d34a55" alt=""><figcaption></figcaption></figure>


---

# 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.kpnthings.com/kpn-things/the-portal-explained/things-manager/iot-devices/flows-tab.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.