Hermetry has no built-in scheduled or e-mailed reports. You get data out in four ways: download it from a dashboard card, read it with the history API, forward it from a flow as it arrives, or export the whole organisation. This page helps you pick one.
Which way to use
| Need | Use |
|---|---|
| A one-off spreadsheet of what a chart or table shows | Download data (CSV) on a dashboard card |
| A regular extract into your own system (ERP, data warehouse, BI) | The history API, called by your scheduler |
| Every reading in your own store, in real time | A forwarding block in the root flow |
| A copy of your organisation’s records (members, settings, devices) | The organisation export |
Download from a dashboard card
Most data cards can offer a download:
- Open the dashboard and switch to editing.
- Open the card’s settings. Under Card buttons, tick Download data (CSV).
- Save the card and the board.
The card header then has a CSV button and, beside it, an Excel (.xlsx) button. Both download what the card holds at that moment, in the board’s current time window.
| Detail | Value |
|---|---|
| Cards that can download | Chart cards (line, bar, area, pie, scatter, histogram, heatmap), table cards, the activity feed, map cards, attribute lists and model views |
| File name | The card’s title (or the card type) and the date, for example Tank-levels-2026-11-09.csv |
| Rows | What the card shows, in the columns its query returns. A table that pages on the server is walked page by page up to 10,000 rows; beyond that the download says “Exported the first 10000 rows only.” |
| Permissions | Only what the viewer may see |
To export a period, set the board’s time window first (for example This month), then download. A chart over a long window holds hourly or daily figures, not every reading; see Aggregates and rollups. For every reading of a period up to the raw window, use a table card with a raw source over at most 24 hours, or the API.
See Tables and lists and Widgets.
The device’s Telemetry tab has no download button.
Read with the history API
GET /api/telemetry/series returns any key of any device you may read, over any window your retention keeps, at raw, minute, hour or day resolution, with an aggregate of your choice. Call it from a script on a schedule to build your own reports: for example, every morning read yesterday’s hourly increase of each energy meter.
- Authenticate with an API key that has the telemetry read permission. Give the key the Read-only preset and restrict its networks.
- At most 50 keys and 10,000 points per key per request; split longer periods into several calls.
See The history API and Authentication.
Forward from a flow
To keep every reading in a system of your own (a data lake, a historian, a message broker), add a forwarding step to the root flow, after Save telemetry:
| Block | Sends to | Notes |
|---|---|---|
| HTTP request | Your HTTPS API, through an HTTP endpoint connection | Retries transient failures with the same idempotency key; private addresses are refused |
| MQTT out | Your MQTT broker | QoS 0, 1 or 2 |
| Webhook | A webhook endpoint of your organisation subscribed to “Automation message” | Signed, retried, with a delivery list |
Set the block’s late setting to send when your store must also receive the backlog after an outage. Readings arrive one record at a time; use the Batch block to send groups. See Action blocks and Flow cookbook.
Forwarding is in addition to storing: keep Save telemetry in the root flow.
The organisation export
An Owner can export the organisation’s data as one JSON file. It holds records such as members, settings, webhooks, API key metadata, the newest audit log entries and, from the IoT modules, the devices and their attributes (up to 10,000 rows each). Device secrets, credentials and addresses are never included, and values under secret-looking attribute keys are masked.
The organisation export does not contain telemetry readings. Use the history API for those. See Export your data and close your organisation.
Other exports
| Data | Where |
|---|---|
| Audit log | CSV or NDJSON. See Audit log. |
| A flow | Export in the flow’s row menu (a JSON file of the flow, without secrets). See Versions, testing and rollback. |
| A dashboard | A board file. See Board templates and board files. |
No scheduled reports
Hermetry does not send reports by e-mail on a schedule. If you need one, either:
- run a small script on your side that calls the history API and mails the result, or
- build a flow with a Schedule trigger and an HTTP request block that asks your own reporting service to produce and send the report.
Before you rely on an export
- Raw readings are kept at most 90 days; hour and day figures for your full class. See How long data is kept.
- Times in the API are milliseconds since the epoch, UTC.