0d3cb498a3
Deploy local.promptfoo.app / Deploy to Cloudflare Pages (push) Waiting to run
Test and Publish Multi-arch Docker Image / test (push) Waiting to run
Test and Publish Multi-arch Docker Image / build-docker-and-push-digests (map[digest-suffix:linux-amd64 platform:linux/amd64 runner:ubuntu-latest]) (push) Blocked by required conditions
Test and Publish Multi-arch Docker Image / build-docker-and-push-digests (map[digest-suffix:linux-arm64 platform:linux/arm64 runner:ubuntu-24.04-arm]) (push) Blocked by required conditions
Test and Publish Multi-arch Docker Image / merge-docker-digests (push) Blocked by required conditions
Test and Publish Multi-arch Docker Image / Attest Multi-arch Image (push) Blocked by required conditions
CI / Shell Format Check (push) Waiting to run
CI / Check Ruby (3.4) (push) Waiting to run
CI / CI Config (push) Waiting to run
CI / Test on Node ${{ matrix.node }} and ${{ matrix.os }}${{ matrix.shard && format(' (shard {0}/3)', matrix.shard) || '' }} (push) Blocked by required conditions
CI / Build on Node ${{ matrix.node }} (push) Blocked by required conditions
CI / Style Check (push) Waiting to run
CI / Generate Assets (push) Waiting to run
CI / Check Python (3.14) (push) Waiting to run
CI / Check Python (3.9) (push) Waiting to run
CI / Build Docs (push) Waiting to run
CI / Code Scan Action (push) Waiting to run
CI / Site tests (push) Waiting to run
CI / webui tests (push) Waiting to run
CI / Run Integration Tests (push) Waiting to run
CI / Run Smoke Tests (push) Waiting to run
CI / Go Tests (push) Waiting to run
CI / Share Test (push) Waiting to run
CI / Redteam (Production API) (push) Waiting to run
CI / Redteam (Staging API) (push) Waiting to run
CI / GitHub Actions Lint (push) Waiting to run
CI / Check Ruby (3.0) (push) Waiting to run
release-please / release-please (push) Waiting to run
release-please / build (push) Blocked by required conditions
release-please / publish-npm (push) Blocked by required conditions
release-please / publish-npm-backfill (push) Waiting to run
release-please / docker (push) Blocked by required conditions
release-please / publish-code-scan-action (push) Blocked by required conditions
release-please / attest-code-scan-action (push) Blocked by required conditions
Validate Renovate Config / Validate Renovate Configuration (push) Waiting to run
n8n-agent (n8n AI Agent Evaluation)
You can run this example with:
npx promptfoo@latest init --example n8n-agent
This example demonstrates how to evaluate n8n AI agents and workflows using the n8n provider.
Prerequisites
- A self-hosted n8n instance with a webhook-triggered workflow
- An AI agent workflow that accepts messages and returns responses
Setup
- Create an n8n workflow with a Webhook trigger node
- Add your AI agent logic (e.g., AI Agent node, OpenAI node)
- Configure the workflow to return the agent's response
- Update
promptfooconfig.yamlwith your webhook URL:
providers:
- id: n8n:https://your-n8n-instance.com/webhook/your-agent-id
Environment Variables
export N8N_API_KEY=your-api-key # If your webhook requires authentication
Running the Example
# Run the evaluation
npx promptfoo eval
# View results
npx promptfoo view
Configuration Options
url: Webhook URL (alternative to specifying in provider path)method: HTTP method (default:POST);GETsends rendered body fields as query parametersheaders: Additional request headersbody: Custom request body template with Nunjucks support; prefer object form for JSON payloadstransformResponse: JavaScript expression to extract outputsessionHeader: Request header name for the session IDsessionParser: JavaScript expression to extract a session IDsessionField: Request body field for a supplied session ID
For multi-turn runs, pass sessionId in test variables or use a multi-turn strategy so sessions
remain scoped to one conversation. Keep webhook credentials in environment-backed headers rather
than embedding them in webhook URLs. The provider uses a fingerprinted display ID and skips
response caching so tokenized URLs and session-bearing requests do not enter response-cache
diagnostics or storage; URLs still remain in configuration and outbound requests.
Response Formats
The provider automatically handles common n8n response formats:
{ "output": "Response text" }
{ "response": "Agent response" }
{ "message": { "content": "Hello" } }
[{ "json": { "output": "Result" } }]
For custom formats, use transformResponse:
config:
transformResponse: 'json.data.agentMessage'
For more information, see the n8n Provider documentation.