This part of the Help Center follows data after a workflow receives it. Define the business entity you want to keep, map workflow output onto it, and then use that history in dashboards or read-only embeds.
Choose your next task
- Define a data model — the fields and primary key your workflows and dashboards share.
- Persist workflow data — map upstream fields onto a data model and save the result.
- Build a dashboard — widgets that read those records and recompute as new ones land.
- Embed a dashboard — put a live dashboard in another web page.
- Run a report — ask one question of those records and download the answer.
The order these happen in
- A data model describes the shape. Nothing is stored yet.
- A workflow's Map to Data Model step fills it, one record per run.
- Dashboards read those records. A widget with no records shows nothing, so build the dashboard after data has landed.
If you are still learning the builder, start with Build your first workflow — its optional last step creates a data model and maps into it.
What the warehouse keeps
Nothing is ever overwritten. A second write for the same primary key becomes the next entry in that entity's history, so every record carries a complete timeline you can scrub back through.
Every record also knows which workflow version and step produced it, which makes "where did this number come from?" a question with an answer.