Get started: HTTP GET
This tutorial builds your first dashboard. You will add one data section, one data piece, and one HTTP data source that fetches live JSON from the network. Then you will pull out a single field on a Label.
1. Create a data section
A data section is one swipeable screen on your dashboard. Each section has a name and holds a grid of data pieces.
On the empty home screen, tap Add data section manually or Ask AI assistant to add data section. Or open the menu → Data → Add section.
Choose the section type (Fixed grid for this guide), then type a section name and tap OK. The new section opens right away with Edit layout on. Its settings are under the tune button at the top.
See Main screen: dashboard and sections for how sections and swiping work.
2. Add a data piece
On an empty section, tap Add data piece manually or Ask AI assistant to add data piece. Or turn on Edit layout, tap Add at the top, then Add data piece. In the library, pick Design your own data piece.
3. Create an HTTP data source
Open the menu → Data sources → Add data source, or start from Add data piece → Data source → Add data source.
On the "New data source" screen you set:
- Name — a label for this source
- Data source type — HTTP, HTTP stream, Video, MQTT, WebSocket, or Timer
- Type-specific settings (for HTTP: an Actions / Transformers pipe with at least one request, plus how often it fetches)
- Every type except HTTP and Video can add optional data transformers that run at the source level. HTTP sources use the Actions / Transformers pipe instead.
Create an HTTP source as an example:
-
Set Name to
HTTP DS. -
Open the first HTTP request in the Actions / Transformers pipe. Leave method as GET.
-
Set URL to the DummyJSON single-product address:
https://dummyjson.com/products/1That address returns mock product JSON — handy for testing without your own server.
-
Tap the save tick in the top-right.
See Data sources (incoming) for the full list of HTTP options.
4. Finish the data piece
You're still in the data piece editor (or turn on Edit layout, tap the data piece, then tap its menu button → Edit if you left it).
Set HTTP DS as the data piece root data source. Tap Add component in the top-right and choose Label. The Label uses that source. Inherited stays on, so it shows the same data as the data piece — the full JSON from the server.
Tap the save tick in the top-right.
5. View the JSON on the dashboard
Back on the home screen, the Label shows the full JSON from the server.
6. Extract the product title
Showing the whole JSON is rarely what you want. To pull out one field:
- Turn on Edit layout, tap the data piece, then tap its menu button.
- Choose Edit to open the data piece editor, then select the Label.
Inherited is on by default, so the rest of Data transformers pipe is hidden. Turn Inherited off so this Label can run its own transformers.
To reshape data before it's shown, use a data transformer on the component. Transformer types include JSONPath, Lua, and Simple expression. Here you'll add a simple expression:
- Under Data transformers pipe, tap Add....
- Choose Simple expression from the list.
- Enter
value?.title.
To remove a transformer later, swipe its row right to left in the editor.
The ?. keeps things safe if .title is missing; value.title also works, but fails if the field isn't there. See Expressions for more.
Save. The Label now shows the product title instead of raw JSON.
What you built
| Part | Role |
|---|---|
| Data section | One dashboard screen |
| HTTP data source | Fetches from DummyJSON and stores the response as value |
| Data piece | One cell in the dashboard grid. Root HTTP source; a Label inherits it. Inherited off on the Label; a Simple expression transformer shows just the title |
Next steps
- Get started: HTTP POST on tap — add tap actions, POST to DummyJSON, and show the response
- Get started: MQTT — subscribe, publish on tap, and read live telemetry
- Get started: WebSocket send and receive — shared connection and echo server
- Get started: Timer source and live clock — timer-driven Timer source and Lua
- Typical setup flow — recommended order for larger dashboards
- Data transformers — source-level vs component transformer chains
- Tap actions — refresh, user input, HTTP request, MQTT send, WebSocket send, outbound destinations
- Menu and navigation — where to find every editor