Self-hosted · n8n ≥ 2.19.0
Built-in OTLP tracing
Enable n8n's OTel tracer and export OTLP/HTTP JSON to Mibo. The configured service.name routes traces to the matching agent.
Test n8n AI workflows before release, then keep evaluating every real run.
Mibo connects n8n's workflow execution to a reliability test suite. Drive selected scenarios actively, or send traces from n8n Cloud and self-hosted workflows for passive production evaluation.
Three supported ways to connect n8n
Cloud or self-hosted
Mibo Testing Node
Add the community node when you want per-workflow control. It captures the execution graph and sends a canonical Mibo trace.
View verified n8n listing →Any n8n version
HTTP Request node
Send a JSON trace from the built-in node at the end of a workflow, without installing a package or changing host configuration.
A concrete workflow test
Imagine an n8n support workflow handling a cancellation request. An active test can send the scenario before a workflow change and check that the router selects the billing path, the cancellation tool receives the right account, and the response explains the next step.
After release, the same expectations can evaluate real traces passively. A production interaction that claims a cancellation completed without a successful tool result becomes evidence for investigation rather than a silent failure.
Compatibility boundary
n8n controls how the workflow runs. Mibo controls the test definitions and evaluation. Active testing needs a configured agent connection; passive testing only needs an authenticated trace path and active test cases.
Learn about production testing →Keep exploring
n8n setup documentation
Use the maintained setup guide for environment variables, nodes, headers, and trace routing.
Open n8n docs →AI agent evaluation
See how semantic and procedural checks evaluate the workflow's behavior.
Explore evaluation →See Mibo in action
Run a live passive reliability check with a synthetic support request.
Run a live check →