Evaluate AI Agent Response Relevance with OpenAI & Cosine Similarity

Evaluates AI agent response relevance to user questions by generating a proxy question via OpenAI and scoring with cosine similarity, inspired by RAGAS.

n8n
Evaluate AI Agent Response Relevance with OpenAI & Cosine Similarity

This n8n workflow calculates the 'Relevance' metric for AI agent responses in Q&A scenarios, adapting the open-source RAGAS framework. It analyzes the agent's answer by prompting another LLM (OpenAI) to generate a representative question from it, then compares this to the original user question using cosine similarity on embeddings. High scores indicate on-topic, accurate responses; low scores flag irrelevance, hallucinations, or off-script content.

The process starts with inputting the user question and agent response. An OpenAI Chat Model generates a question that the response best answers. Embeddings are computed for both questions (original and generated), and cosine similarity yields a 0-1 score. This requires n8n 1.94+, OpenAI credentials, and works seamlessly with LangChain nodes for advanced AI chaining.

Benefits include automated quality checks for chatbots, RAG systems, and AI agents, saving manual review time and enabling scalable evaluation pipelines. Ideal use cases: Travel AI assistants (e.g., logistics queries), customer support bots, or any Q&A agent needing relevance scoring. Integrate with Google Sheets for batch testing sample data provided in the template.

$16.99
Last updated October 3, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Travel workflows

More from Jose Maurino

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.