nodes / builtin / trigger
Evaluation Trigger
Run the workflow once per row of a test dataset, from Test runs only
Hold the test rows of an evaluation. Test runs starts the workflow here, once per row, to measure how well it answers.
What it does
Section titled “What it does”The Evaluation Trigger never starts a normal run: pressing Run ignores it, and it doesn’t run on a schedule or any other trigger. Only Run evaluation in the canvas ⋯ menu › Test runs uses it. Each row becomes one run, and the row’s columns are this trigger’s output.
Rows come from:
- Data Store: a Dataset key that holds a list of rows, or a key prefix ending in
*(one row per key, in key order). Whose keys picks this workflow’s keys or all workflows’. - CSV: rows pasted in the step, with a header line.
Up to caps the rows per evaluation run (50 by default, at most 500).
- Google Sheets: a sheet read with the step’s Google connection (the spreadsheet’s link or ID, and the worksheet’s gid). The first row names the columns; each non-empty row below is a case.
To add a real run as a case, open it in Runs and use Add this run’s input to the test dataset (Data Store lists only, not a key prefix).
When to use it
Section titled “When to use it”- Before changing the model or the prompt of an AI workflow: run the same cases before and after, and compare.
- To keep a set of tricky inputs that once went wrong, and check they stay fixed.
See Test runs for the whole method.
Inputs and settings
Section titled “Inputs and settings”| Setting | Type | What it does |
|---|---|---|
| Rows from | Choice | Options: Data Store, CSV, Google Sheets. Default: Data Store |
| Dataset | Text | A Data Store key holding a list of rows, or a key prefix (one row per key, end it with *). |
| Whose keys | Choice | Options: This workflow, All workflows. Default: This workflow |
| CSV | Long text | Paste the rows, with a header line. |
| Connection | Credential | |
| Spreadsheet | One of several shapes | Paste its link or ID. |
| Worksheet ID | Text | The gid in the link; empty = the first sheet. |
| Up to | Number | Rows per evaluation run (at most 500). Default: 50 |
Put the expected answer in a column of the dataset (for example expected), so an Evaluation step can compare it with what the workflow produced.
question,expectedWhere is my order 1042?,shippingCan I get a refund?,billingOutputs
Section titled “Outputs”-
Output
Each output item has these fields:
| Field | Type | What it holds |
|---|---|---|
| _evalRow | Number |
{ "_evalRow": 0}The row’s columns, plus _evalRow (the row number, from 0).
Dependencies and credentials
Section titled “Dependencies and credentials”- Connection (connection, OAuth2): optional. See Create a connection.
Example workflow
Section titled “Example workflow”- Evaluation Trigger with the CSV above, next to the workflow’s normal Chat Trigger.
- Both triggers lead into the same Text Classifier.
- An Evaluation step, Set metrics, Category, expected
{{ $('Evaluation Trigger').expected }}.
Common issues
Section titled “Common issues”- “The dataset has no rows.”: the key is empty, or no key starts with the prefix.
- “Paste the CSV rows, with a header line.”: the CSV box is empty.
- “Save first: test runs use the saved workflow.”: Test runs always run the saved version. Save, then run the evaluation.
Related nodes
Section titled “Related nodes”- Evaluation: score each case.
- Data Store: keep the dataset.