> For the complete documentation index, see [llms.txt](https://docs.beeta.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beeta.one/platform/beeta.builder.md).
# beeta.builder
Our beeta.builder is a powerful graphical user interface that allows you to easily create and configure IoT data flows. It provides an intuitive environment for designing simple linear or complex data flows with multiple inputs and outputs.
The building blocks are divided into three categories: Input, Processing and Output. These blocks can be dragged and dropped onto a canvas and linked together to create a data flow. The intuitive drag-and-drop functionality allows you to visually design your data flows without the need for extensive programming knowledge.
Each block can be configured directly on the block itself, making setting up the desired functionality simple and straightforward. Define your input sources, apply different processing functions and set output targets - all in one place. You can easily create and configure your own custom data flows to adapt and digitise IoT implementations to meet specific business requirements.
The beeta.builder reduces the complexity of managing IoT data flows and allows users to focus on gaining meaningful insights and taking action.
---
# 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.beeta.one/platform/beeta.builder.md?ask=&goal=
```
`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.