> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/build/integrate-ai/test-and-improve-ai-workflows/run-quick-evaluations.md).

# Run quick evaluations

{% hint style="info" %}
**Available on registered community and paid plans**

Light evaluations are available to registered community users and on all paid plans.
{% endhint %}

## What are light evaluations? <a href="#what-are-light-evaluations" id="what-are-light-evaluations"></a>

When building your workflow, you often want to test it with a handful of examples to get a sense of how it performs and make improvements. At this stage of workflow development, looking over workflow outputs for each example is often enough. The benefits of setting up more [formal scoring or metrics](/build/integrate-ai/test-and-improve-ai-workflows/use-metrics-to-measure-quality.md) don't yet justify the effort.

Light evaluation allows you to run the examples in a test dataset through your workflow one-by-one, writing the outputs back to your dataset. You can then examine those outputs next to each other, and visually compare them to the expected outputs (if you have them).

## How it works <a href="#how-it-works" id="how-it-works"></a>

{% hint style="info" %}
**Credentials for Google Sheets**

Evaluations use data tables or Google Sheets to store the test dataset. To use Google Sheets as a dataset source, configure a [Google Sheets credential](/integrations/builtin/credentials/google.md).
{% endhint %}

Light evaluations take place in the 'Editor' tab of your workflow, although you’ll find instructions on how to set it up in the 'Evaluations' tab.

Steps:

1. Create a dataset
2. Wire the dataset up to the workflow
3. Write workflow outputs back to dataset
4. Run evaluation

The following explanation will use a sample workflow that assigns a category and priority to incoming support tickets.

![Example AI workflow](/files/d11MWCaBzwH9N4MlVxnM)

### 1. Create a dataset <a href="#id-1-create-a-dataset" id="id-1-create-a-dataset"></a>

Create a data table or Google Sheet with a handful of examples for your workflow. Your dataset should contain columns for:

* The workflow input
* (Optional) The expected or correct workflow output
* The actual output

Leave the actual output column or columns blank, since you'll be filling them during the evaluation.

<figure><img src="/files/r7sSFm5EXJrsGsAuUT66" alt=""><figcaption><p>A <a href="https://docs.google.com/spreadsheets/d/1uuPS5cHtSNZ6HNLOi75A2m8nVWZrdBZ_Ivf58osDAS8/edit?gid=294497137#gid=294497137">sample dataset</a> for the support ticket classification workflow.</p></figcaption></figure>

### 2. Wire the dataset up to your workflow <a href="#id-2-wire-the-dataset-up-to-your-workflow" id="id-2-wire-the-dataset-up-to-your-workflow"></a>

#### Insert an evaluation trigger to pull in your dataset <a href="#insert-an-evaluation-trigger-to-pull-in-your-dataset" id="insert-an-evaluation-trigger-to-pull-in-your-dataset"></a>

Each time the [evaluation trigger](/integrations/builtin/core-nodes/n8n-nodes-base.evaluationtrigger.md) runs, it will output a single item representing one row of your dataset.

Clicking the 'Evaluate all' button to the left of the evaluation trigger will run your workflow multiple times in sequence, once for each row in your dataset. This is a special behavior of the evaluation trigger.

While wiring the trigger up, you often only want to run it once. You can do this by either:

* Setting the trigger's 'Max rows to process' to 1
* Clicking on the 'Execute node' button on the trigger (rather than the 'Evaluate all' button)

#### Wire the trigger up to your workflow <a href="#wire-the-trigger-up-to-your-workflow" id="wire-the-trigger-up-to-your-workflow"></a>

You can now connect the evaluation trigger to the rest of your workflow and reference the data that it outputs. At a minimum, you need to use the dataset’s input column(s) later in the workflow.

If you have multiple triggers in your workflow you will need to [merge their branches together](/build/integrate-ai/test-and-improve-ai-workflows/fix-common-issues.md#combining-multiple-triggers).

<figure><img src="/files/9pKgcoa7E61WezXanylV" alt=""><figcaption><p>The support ticket classification workflow with the evaluation trigger added in and wired up.</p></figcaption></figure>

### 3. Write workflow outputs back to dataset <a href="#id-3-write-workflow-outputs-back-to-dataset" id="id-3-write-workflow-outputs-back-to-dataset"></a>

To populate the output column(s) of your dataset when the evaluation runs:

* Insert the 'Set outputs' action of the [evaluation node](/integrations/builtin/core-nodes/n8n-nodes-base.evaluation.md)
* Wire it up to your workflow at a point after it has produced the outputs you're evaluating
* In the node's parameters, map the workflow outputs into the correct dataset column

<figure><img src="/files/15ZkERVzZNGsVrlSQCUI" alt=""><figcaption><p>The support ticket classification workflow with the 'set outputs' node added in and wired up.</p></figcaption></figure>

### 4. Run evaluation <a href="#id-4-run-evaluation" id="id-4-run-evaluation"></a>

Click on the **Execute workflow** button to the left of the evaluation trigger. The workflow will execute multiple times, once for each row of the dataset:

![Execute workflow button](/files/4Uj2FTXmSb30Cix07jtG)

Review the outputs of each execution in the data table or Google Sheet, and examine the execution details using the workflow's 'executions' tab if you need to.

Once your dataset grows past a handful of examples, consider [metric-based evaluation](/build/integrate-ai/test-and-improve-ai-workflows/use-metrics-to-measure-quality.md) to get a numerical view of performance. See also [tips and common issues](/build/integrate-ai/test-and-improve-ai-workflows/fix-common-issues.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.n8n.io/build/integrate-ai/test-and-improve-ai-workflows/run-quick-evaluations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.