The Dashboard tab is a Grafana-style space where you build grids of chart widgets. Each widget is rendered from the output of its own hidden Heym workflow, so any data you can produce in a workflow — database queries, API calls, RAG lookups, LLM output — can become a chart. You can keep several dashboards and share each one with people or teams.
Dashboards
Everyone starts with one dashboard, created the first time they open the tab. Use the dashboard selector at the top of the tab to switch between dashboards, and + next to it to create a new one. The selector lists your own dashboards first, then the ones shared with you, labelled with the name of the person who shared them.
The tab reopens the dashboard you used last, and the address bar carries the open dashboard (?tab=dashboard&dashboard=<id>), so a link opens that exact dashboard for anyone who has access to it.
The settings button (owners only) renames the dashboard, manages sharing, and deletes it. Deleting a dashboard removes its widgets and their workflows. You always keep at least one dashboard of your own, so the last one cannot be deleted.
Widgets
A widget is a single chart on the grid. Supported chart types:
- Bar (vertical or horizontal)
- Line
- Area (filled trend, supports multiple series)
- Pie
- Table (scrollable)
- Numeric (a single KPI value with an optional unit)
- Gauge (a single value against a min–max range, e.g. a percentage)
- Scatter (X/Y points for correlation plots)
- Proportion (one bar split into shares with a percentage legend, e.g. a language breakdown)
- Bar gauge (one horizontal gauge per row with a red→green gradient and a value, e.g. free disk space)
- Text (a markdown message, e.g. a status note like "Last execution at 19:47"; supports interactive checkboxes when the markdown is static, and explicit numbered lists for custom or descending numbering)
Each widget loads its data asynchronously when you open the tab, so the page stays responsive while charts populate.
Adding a widget
- Click Add widget, give it a title, and pick a chart type. Below the picker, the dialog draws an example of that chart type with sample data and names the rows it expects, so you can compare types before you build anything.
- The widget opens in the workflow editor with a starter graph: a Set node that produces the rows, connected to a Chart Output node. Replace the Set node with any data source.
- Build the workflow so the node feeding Chart Output produces an array of rows, then configure the Chart Output node's field mapping (label field, value field, etc.).
- Save, return to the Dashboard tab, and the widget renders.
Double-click a widget (or use its edit button) to reopen its workflow at any time. Use Clone widget in the widget header to duplicate both the widget and its complete workflow. The copy is placed below the original and labeled with (Copy) so you can edit it independently.
Generating a widget with AI
Click AI, describe the metric you want (for example, "workflow success rate over the last 30 days as a bar chart"), and pick an LLM credential and model. Heym generates a complete widget workflow ending in a Chart Output node and adds it to the grid. See Chart Output for example prompts per chart type.
Use a widget's Fine-tune with AI button to revise an existing widget with a new instruction. Each AI fine-tune snapshots the previous workflow into the widget's Edit History, so you can review or roll back changes from the workflow editor.
Editing the layout
Toggle Edit to enter edit mode, where you can drag widgets and resize them on a 12-column grid. Layout changes are saved automatically. Widget titles are editable inline from the widget header.
Caching and refresh
Each widget caches its last computed data on the server for a configurable time-to-live (TTL). While the cache is fresh, reopening the dashboard serves the stored result instead of re-running the workflow. The cache is replaced in place every time the data is recomputed (one cache per widget), and it is automatically invalidated when you edit the widget's workflow.
Use a widget's Refresh button (or Refresh in the toolbar) to bypass the cache and recompute immediately.
Sharing
Owners share a dashboard from its settings, with individual users (by email) or with any team they belong to. Each share is Read or Write; when someone has both a personal and a team share, the stronger one applies.
| Action | Owner | Write | Read |
|---|---|---|---|
| View widgets, refresh them, use auto-refresh | ✓ | ✓ | ✓ |
| Add, clone, delete, rename and resize widgets; AI generate and fine-tune; tick checklist items | ✓ | ✓ | |
| Open a widget's workflow in the editor | ✓ | ✓ | |
| Rename or delete the dashboard, manage sharing | ✓ |
Widgets always run as the dashboard owner. Whoever is looking, a widget uses the owner's credentials and global variables, and its runs appear in the owner's execution history and traces. Teammates therefore see the same data without access to the accounts behind it, and every viewer shares the one cached result per widget. Widgets that a write collaborator adds or clones belong to the owner as well.
Because of this, Write carries the same trust as sharing a workflow for editing: a collaborator with write access can change what runs with your credentials. Give it only to people you would let edit your workflows. A test run that a collaborator starts from the workflow editor uses their own credentials, as with any shared workflow; only the dashboard itself runs as the owner. Read grants no access to the widget workflows, and read-only viewers receive the chart itself but not the per-node execution details behind it.
Removing a share, or lowering it from write to read, takes effect immediately.
Related
- Chart Output node
- Analytics tab — built-in execution metrics (distinct from user-built dashboards)