config-evals

Create and manage configuration-based workflow evaluations against test datasets.

203k|60.5k|Updated Jun 22, 2019
One-click install
npx skills add https://github.com/n8n-io/n8n --skill config-evals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-evals
Source: https://github.com/n8n-io/n8n/tree/main/packages/%40n8n/instance-ai/skills/config-evals
Command: npx skills add https://github.com/n8n-io/n8n --skill config-evals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Setting up workflow evaluations in n8n normally requires manually wiring on-canvas evaluation nodes, which is error-prone and disconnected from the workflow logic you actually want to score. This Skill attaches evaluations through the off-canvas evaluation-config API, pairing a workflow with a dataset and judge metrics without touching the canvas.

Core Features & Use Cases

  • Config-based eval lifecycle: List, get, create, update, and delete evaluations attached to a workflow via the eval-config tool.
  • LLM-judged metrics: Configure correctness and helpfulness presets with judge credentials, models, and expression-based references to dataset columns and workflow outputs.
  • Dataset integration: Link evaluations to n8n Data Tables holding test inputs and ground-truth answers, with explicit guidance on picking the correct start and end nodes.
  • Use Case: Score an AI agent workflow's responses against a labeled dataset of support questions to measure correctness before deploying changes.

Quick Start

Set up a correctness evaluation on my support agent workflow using the existing support eval dataset.

Frequently Asked Questions about config-evals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an evaluation on an n8n workflow?

Use the `eval-config` tool with `action="create"`, supplying the workflow id, a start node after the trigger, an end node, a Data Table id, and one or more judged metrics. The config lives off-canvas and does not modify the workflow itself.

What is the difference between correctness and helpfulness metrics?

Correctness compares the produced answer to a ground-truth value from the dataset and requires an `expectedAnswer` expression. Helpfulness judges the answer against the user's query and requires a `userQuery` expression, with no ground truth needed.

Why must the start node have an incoming connection?

An eval run replaces the workflow's trigger with a dataset-driven one, so the start node must already receive input from a trigger. Naming the trigger itself as the start node causes the eval run to fail to compile.

Why is my expression stored as literal text instead of being evaluated?

Expression fields like `actualAnswer`, `expectedAnswer`, and `userQuery` must begin with `=` so n8n evaluates the `{{ ... }}` template. Without the leading `=`, the string is stored verbatim and the judge scores the raw template text.

Can I use on-canvas evaluation nodes with this Skill?

No. This Skill only handles configuration-based evaluations through the evaluation-config API. If the user asks for EvaluationTrigger or Evaluation nodes, build a config eval instead and explain that is how evaluations are set up.