Configuring the Mibo Testing Node

Once you’ve added the Mibo Testing node to your workflow, you need to configure it so it knows where to send the captured data.

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 project settings.
   • Server URL — leave this as the default unless you’re using a self-hosted Mibo instance.

Node settings

Target Nodes

Choose which nodes in your workflow should be captured. The Mibo Testing node will collect the inputs and outputs of each selected node and include them in the trace.

You have two options:

• Manual selection — type the names of the nodes you want to capture, separated by commas.
• Automatic detection — use the “Get Workflow” mode to let Mibo detect your workflow’s nodes automatically. You can then filter by type:
  • All nodes — captures everything.
  • AI nodes only — captures AI-related nodes (agents, LLM calls).
  • HTTP nodes only — captures API calls.
  • Exclude utility nodes — skips sticky notes, wait nodes, and other non-functional nodes.

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.

Request ID (optional)

A way to match incoming webhook requests with specific test executions. This is usually set up automatically using an expression that reads the request ID from the webhook headers. In most cases, you can leave the default value.

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.