Dashview Docs - Autoflow Node Reference

1. Node type matrix

Type	Configblok	Doel	Branching
`trigger`	`trigger`	Flowstart via schedule of event	default output
`datasource`	`data`	Datasource context zetten	default output
`filter`	`filter`	Filterregels op context toepassen	default output
`metric`	`metric`	Aggregatie op data berekenen	default output
`math`	`math`	Berekeningen op metricwaarden	default output
`condition`	`condition`	Vergelijking tussen references	if + else verplicht
`llmcondition`	`llm`	AI true/false routing	if + else verplicht
`llmresponse`	`llm`	AI tekstoutput naar context	default output
`elementnode`	`element`	Element uitvoeren als processing node	default output
`elementaction`	`element`	Element uitvoeren als action node	default output
`action`	`action`	Notificatie versturen	eindnode

2. Trigger, datasource en filter

Trigger node (`type: trigger`)

Veld	Type	Required	Beschrijving
`trigger.schedule`	string	No	Cron string of `Manual`.
`trigger.eventType`	string	No	Event trigger type (bijv. `parquet-refresh`, `alert`).
`trigger.minSeverity`	low/medium/high/critical	No	Alleen relevant voor `alert` events.

{
  "id": "trigger_daily",
  "type": "trigger",
  "title": "Dagelijkse check",
  "trigger": {
    "schedule": "0 8 * * *"
  }
}

Datasource node (`type: datasource`)

Veld	Type	Required	Beschrijving
`data.dataSourceId`	string	Yes	ID van bestaande datasource binnen tenant.

{
  "id": "ds_sales",
  "type": "datasource",
  "title": "Sales data",
  "data": {
    "dataSourceId": "testdata"
  }
}

Filter node (`type: filter`)

Ondersteunde rule-types: text, number, date, boolean. De runner vertaalt rules naar een SQL-achtige expressie en combineert rules met AND.

Rule veld	Type	Beschrijving
`field`	string	Kolomnaam (vereist).
`type`	text/number/date/boolean	Datatype van de vergelijking.
`enabled`	boolean	Uitgeschakelde rules worden genegeerd.
`values`	array	Tekst/keuze-set of numerieke lijst afhankelijk van type.
`min`, `max`	number	Range filtering voor type `number`.
`datePreset`	string	Preset (o.a. `past7`, `past30`, `thisWeek`, `lastWeek`, `ytd`).
`dateFrom`, `dateTo`	string	Datumrange (YYYY-MM-DD of date-time string).
`boolValue`	boolean	Boolean match voor type `boolean`.

{
  "id": "flt_paid_last_week",
  "type": "filter",
  "title": "Betaald vorige week",
  "filter": {
    "rules": [
      { "field": "status", "type": "text", "values": ["paid"], "enabled": true },
      { "field": "invoice_date", "type": "date", "datePreset": "past7_shift1w", "enabled": true }
    ]
  }
}

3. Metric, math en condition

Metric node (`type: metric`)

Veld	Type	Required	Beschrijving
`metric.key`	string	Yes	Unieke metric key in context.
`metric.label`	string	No	Leesbaar label; default van key.
`metric.aggregation`	sum/avg/count/min/max	Yes	Aggregatietype.
`metric.measureField`	string	Yes	Kolom waarop geaggregeerd wordt (bij count optioneel conceptueel).
`metric.dataSourceId`	string	No	Override van datasource context.
`metric.sourceNodeId`	string	No	Specifieke contextbron voor filters.

{
  "id": "metric_revenue_current",
  "type": "metric",
  "title": "Omzet huidig",
  "metric": {
    "key": "revenue_current",
    "label": "Omzet huidig",
    "aggregation": "sum",
    "measureField": "line_total"
  }
}

Math node (`type: math`)

Veld	Type	Required	Beschrijving
`math.variables`	array	Yes	Variabelen met `key` en optioneel `metricKey`/`nodeId`.
`math.expressions`	array	Yes	Expressies met `key` en `expression`.

{
  "id": "math_compare",
  "type": "math",
  "title": "Vergelijking",
  "math": {
    "variables": [
      { "key": "current", "label": "Current", "metricKey": "revenue_current" },
      { "key": "previous", "label": "Previous", "metricKey": "revenue_previous" }
    ],
    "expressions": [
      { "key": "delta", "label": "Delta", "expression": "current - previous" },
      { "key": "pct_change", "label": "% verschil", "expression": "((current - previous) / NULLIF(previous, 0)) * 100" }
    ]
  }
}

Condition node (`type: condition`)

Vergelijkt left en right references. Bronnen kunnen metric, math of number zijn.

Veld	Type	Required	Beschrijving
`condition.operator`	>, >=, <, <=, =, !=	Yes	Vergelijkoperator.
`condition.left`	object	Yes	Linker reference (`source`, `nodeId`, `key`, `value`).
`condition.right`	object	Yes	Rechter reference met zelfde model.

{
  "id": "cond_revenue_down",
  "type": "condition",
  "title": "Omzet lager dan vorige week",
  "condition": {
    "operator": "<",
    "left": { "source": "metric", "nodeId": "metric_revenue_current", "key": "revenue_current" },
    "right": { "source": "metric", "nodeId": "metric_revenue_previous", "key": "revenue_previous" }
  }
}

4. AI, Element en Action nodes

LLM condition / response (`llmcondition` & `llmresponse`)

Veld	Type	Required	Beschrijving
`llm.systemPrompt`	string	No	System context/instructie.
`llm.userTemplate`	string	Yes	Gebruikersprompt met template tokens.
`llm.responseKey`	string	No	Output key in context.
`llm.temperature`	number	No	Creativiteit (UI range 0..2).
`llm.maxTokens`	number	No	Output token cap.
`llm.includeHistory`	boolean	No	Voegt recente flow history toe als context.

{
  "id": "llm_outlier_gate",
  "type": "llmcondition",
  "title": "Outlier detectie",
  "llm": {
    "systemPrompt": "Je bent een data analist. Beslis alleen true of false.",
    "userTemplate": "Metric waarde={{metric:metric_revenue_current}}. Is dit een outlier?",
    "responseKey": "outlierDecision",
    "temperature": 0.1,
    "maxTokens": 120,
    "includeHistory": true
  }
}

Voor llmcondition zijn uitgaande if en else connecties verplicht.

Element node / Element action

Veld	Type	Required	Beschrijving
`element.elementId`	string	Yes	Element ID om uit te voeren.
`element.elementVersion`	string	No	Leeg = latest published.
`element.entrypoint`	string	No	Default `run`.
`element.timeoutSeconds`	number	No	Wordt begrensd op 1..300.
`element.responseKey`	string	No	Context key voor downstream gebruik.
`element.params`	object	No	JSON object; strings mogen template tokens bevatten.

{
  "id": "elem_predict",
  "type": "elementnode",
  "title": "Voorspelling",
  "element": {
    "elementId": "sales_forecast",
    "entrypoint": "run",
    "timeoutSeconds": 90,
    "responseKey": "forecastRows",
    "params": {
      "tenant": "{{dataSourceId}}",
      "windowDays": 14
    }
  }
}

Action node (`type: action`)

Veld	Type	Required	Beschrijving
`action.channel`	Notification	Yes	Wordt intern genormaliseerd naar Notification.
`action.target`	string	Yes	User ID of `all` voor alle users.
`action.severity`	info/warn/critical	No	Default `info`.
`description`	string	No	Berichttemplate met tokens.

{
  "id": "action_warn",
  "type": "action",
  "title": "Waarschuwing",
  "description": "Omzet daalt: huidige={{revenue_currentValue}}, vorige={{revenue_previousValue}}",
  "action": {
    "channel": "Notification",
    "target": "all",
    "severity": "warn"
  }
}

5. Template variabelen

Action-, LLM- en Element-templates kunnen contextwaarden gebruiken uit upstream nodes.

Algemene tokens

{{dataSourceId}}
{{filters}}
{{filterExpressions}}
{{history}} (voor LLM nodes met history-context)

Node-specifieke tokens

{{metric:<nodeId>}}, {{metric:<nodeId>.results}}
{{metricKeyValue}}, {{metricKeyRows}}, {{metricKeyLabel}}
{{math:<nodeId>}}, {{mathVars:<nodeId>}}
{{llmResponseKey}}, {{llmResponseKeyDecision}}, {{llmResponseKeyRoute}}
{{responseKey}} voor Element output keys.

Autoflow nodes: complete setting reference

1. Node type matrix

2. Trigger, datasource en filter

Trigger node (type: trigger)

Datasource node (type: datasource)

Filter node (type: filter)