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

# Data Sources

- [No-Code Integrations](https://docs.qubitro.com/data-sources/no-code-integrations.md): Forward data from connectivity providers without custom code, automatically create devices in Qubitro.
- [Onomondo](https://docs.qubitro.com/data-sources/no-code-integrations/onomondo.md): The Qubitro and Onomondo integration allows you to sync all devices and their data from Onomondo Cloud.
- [Notehub](https://docs.qubitro.com/data-sources/no-code-integrations/notehub.md): The Qubitro and Blues Notehub integration allows you to sync all devices and their data from Notehub.
- [The Things Stack](https://docs.qubitro.com/data-sources/no-code-integrations/the-things-stack.md): The Qubitro and The Things Stack (TTS) integration allows you to sync all devices and their data from The Things Stack.
- [Soracom](https://docs.qubitro.com/data-sources/no-code-integrations/soracom.md): The Qubitro and Soracom integration allows you to sync all devices and their data from Soracom.
- [Loriot](https://docs.qubitro.com/data-sources/no-code-integrations/loriot.md): The Qubitro and Loriot integration allows you to sync all devices and their data from Loriot.
- [1NCE](https://docs.qubitro.com/data-sources/no-code-integrations/1nce.md): Qubitro offers a no-code integration with the 1NCE Cloud Integrator.
- [Golioth](https://docs.qubitro.com/data-sources/no-code-integrations/golioth.md): The Qubitro and Golioth integration allows you to sync all devices and their data from Golioth.
- [AWS IoT Core LoRaWAN](https://docs.qubitro.com/data-sources/no-code-integrations/aws-iot-core-lorawan.md): The Qubitro and AWS IoT Core for LoRaWAN integration allows automatic synchronization of devices and their data from AWS IoT Core to Qubitro.
- [Actility ThingPark](https://docs.qubitro.com/data-sources/no-code-integrations/actility-thingpark.md): The Qubitro and Actility (ThingPark) integration enables you to automatically sync LoRaWAN devices and their data from ThingPark to Qubitro.
- [Chirpstack](https://docs.qubitro.com/data-sources/no-code-integrations/chirpstack.md): The Qubitro and Chirpstack integration allows you to sync all devices and their data from Chirpstack.
- [Particle](https://docs.qubitro.com/data-sources/no-code-integrations/particle.md): The Qubitro and Particle Cloud integration allows you to sync Particle devices and their data to Qubitro seamlessly.
- [Senet](https://docs.qubitro.com/data-sources/no-code-integrations/senet.md)
- [Coiote](https://docs.qubitro.com/data-sources/no-code-integrations/coiote.md)
- [MQTT](https://docs.qubitro.com/data-sources/mqtt.md): Publish device data to Qubitro using the lightweight MQTT protocol for real-time ingestion.
- [HTTP](https://docs.qubitro.com/data-sources/http.md): Send JSON payloads from your devices or applications to Qubitro via a simple HTTP endpoint.


---

# 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.qubitro.com/data-sources.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.