> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs.md).
# Data hub
Organize data traffic with data flows
The applications have access to (master) data from external data sources (**import data**). In addition, entered data can also be written to external data sources (**export data**) again by using a (default) data hub.
A data hub is a **multi-platform application** installed on a server (web or local).
Multiple data hubs can be linked to the same no-code platform.
The data hub can thus have the function of an **edge device**.
A data hub has a **range of services** that establish connections with external data sources (reading and writing data).
The configuration of the services takes place on the no-code platform in the Data studio. Data flows from a toolbox are used, which are visually built (drag & drop) from a **toolbox of triggers, import and export functions and conditions**.
If the data hub acts as an edge device, the current configuration of the data hub in question will be automatically updated upon adjustments in the Data studio (polling).
The Data studio has a **default data hub** with functions depending on the agreed license.
Each data hub has a unique Guid ID that must be entered when adding the hub in the Data Studio.
---
# 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://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs.md?ask=&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.
