n8n Testing Node

The Mibo Testing Node is an open-source n8n community node (npm) that captures execution data from your workflows and sends it to Mibo for analysis.

When your workflow runs, the node collects the inputs and outputs of each node you configure, builds a trace in the optimized format (node names as keys, with output, type, and status), and sends it to Mibo’s trace API. If the payload exceeds 5 MB, it’s automatically gzip-compressed.

The node acts as a passthrough: data flows through it unchanged. Your workflow continues to work exactly as before.

When do you need this node?

The Mibo Testing Node lets you push trace data from your n8n workflows directly to Mibo. This is useful in two scenarios:

• You’re not sharing your n8n API key: without an API key, Mibo can’t pull execution data directly. The node pushes it instead.
• You want to send traces on demand: even if Mibo already collects data through active testing, you can use this node to send traces from any workflow execution whenever you need to (for example, from production runs or manual tests).

Installation

1. Open your n8n instance

   Go to the n8n instance where your AI workflow runs.

2. Go to Community Nodes

   Navigate to Settings → Community Nodes.

3. Install the node

   Search for Mibo Testing and click Install.

4. Verify the installation

   The “Mibo Testing” node should now appear in your node palette. You can search for it when editing any workflow.

Adding the node to your workflow

Open the workflow you want to test with Mibo. Add the Mibo Testing node after the nodes whose data you want to capture, typically at the end of your workflow, after your AI agent or response nodes.

The node doesn’t modify any data passing through it. Your workflow’s output remains exactly the same.

Tip

Place the Mibo Testing node at the very end of your workflow, right before the response is sent back. This ensures it captures data from all previous nodes.

Setting up credentials

1. Open the node settings

   Double-click the Mibo Testing node in your workflow to open its configuration panel.

2. Add your API credentials

   Click on Credentials and create a new Mibo Testing credential. You’ll need:

   • API Key: your Mibo project API key. Find this in your Mibo dashboard under Settings > API Keys.
   • n8n API Key (optional): enables automatic workflow node detection and resolves input parameters (like configured URLs on HTTP Request nodes) so they can be asserted with expected_arguments, no separate “Get Workflow” node needed. To create one: in n8n, go to Settings > API and create a key with the workflow:read scope.
   • n8n Base URL (optional): defaults to http://localhost:5678, which works for most setups since the node runs inside n8n. Change only for n8n Cloud or custom deployments.

Node settings

Target Nodes

Choose which nodes in your workflow should be captured. The node collects the inputs and outputs of each selected node and builds the trace.

You have two options:

• Auto-detect (recommended): enable Auto-detect Workflow Nodes. If you configured n8n API credentials, it discovers nodes automatically. Otherwise, connect an n8n “Get Workflow” node before the Mibo Testing node as a fallback.

  You can filter which nodes are captured:

  Filter	What it captures
  All Nodes	Every node (excluding internal/utility types)
  AI Nodes Only	Only AI-related nodes (agents, LLM calls)
  HTTP/Webhook Only	Only HTTP Request and Webhook nodes
  Exclude Utility Nodes	Everything except Set, If, Merge, and Switch
  Custom	You specify exact node names, separated by commas

• Manual selection: leave auto-detect off and type the names of the nodes you want to capture, separated by commas.

Tip

For most workflows, AI Nodes Only is the best starting point. It captures the nodes that matter most for evaluating your agent’s behavior without including unnecessary data.

Platform ID

Links this node to your n8n platform in Mibo. Enter the platform ID from your Mibo dashboard. This tells Mibo which platform the trace data belongs to.

Metadata (optional)

Add extra labels or context to your traces:

• Environment: tag traces with “production,” “staging,” etc.
• Version: track which version of your workflow generated the trace.
• Custom fields: any additional information you want attached.

Verifying it works

1. Save your workflow with the Mibo Testing node configured.
2. Run the workflow once, either manually or by sending a test message to the webhook.
3. Check Mibo: go to your Mibo dashboard. You should see a new trace appear for the platform.

If the trace doesn’t appear:

• Check the API key: make sure it matches the one in your Mibo project settings.
• Check the Platform ID: verify it points to the correct platform in Mibo.
• Check the workflow execution: make sure the workflow ran successfully and the Mibo Testing node was reached (it won’t capture data if the workflow fails before reaching the node).

Note

The node only sends data when the workflow actually runs. If you’re building or editing the workflow without executing it, no data is sent to Mibo.

Once the node is configured and sending traces, Mibo automatically evaluates every incoming trace against your active test cases. See Passive Testing for the full setup guide.

n8n Trace Format See the exact data structure the node sends to Mibo.

Source Code The node is open source. View the code, report issues, or contribute.