Output
VizzDoo Output
Sends the incoming rows to a VizzDoo project as a dataset with the name you give it, ready to use in a worksheet or dashboard, and passes the same rows on to the next node.
When to use it
Use it at the end of a flow whose result people need to look at rather than download — a weekly enrolment summary, a live attendance board, numbers a principal or a client checks on a phone.
In a pipeline
File InputGroup ByVizzDoo Output
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| VizzDoo Project | text | Yes | — |
| VizzDoo Project Name | text | — | — |
| Dataset Name | text | Yes | e.g. Enrolment by school |
| Write Mode | select | — | replace |
Example
Turn a weekly summary into a live dashboard
- VizzDoo Project=School performance
- Dataset Name=Enrolment by school
- Write Mode=Replace the dataset each run
| School | Students |
|---|---|
| Riverside | 412 |
| Hilltop | 388 |
| School | Students |
|---|---|
| Riverside | 412 |
| Hilltop | 388 |
Open the project in VizzDoo and the dataset is there, already profiled. Dashboards built on it keep working as later runs refresh it.
Worth knowing
- The project list is read from VizzDoo when you open the node, and holds the projects you are allowed to add data to. Choose New project… to make one without leaving FlowDoo.
- The dataset name is the identity: running the flow again updates the same dataset, so a scheduled flow keeps the dashboard current on its own.
- Replace is right for a summary that is rebuilt each run; Add is for a log you are extending, such as a daily reading appended to a history.
- The rows keep flowing, so you can publish to VizzDoo and still write a file or a database table further down the same branch.
- A preview never publishes anything — it says what would be sent instead.
- A run that produces no rows leaves the dataset alone rather than emptying a dashboard on a quiet day.
- It works the same when the flow is scheduled or called through its published API, because the project is stored in the node.