# Quick Start Guide

Get the Mibo Testing node sending traces in about 30 seconds.

## 30-second setup

1. **Install the node** — in n8n, go to **Settings → Community Nodes**, search for `@mibo-ai/n8n-nodes-mibo-testing`, click **Install**.
2. **Add credentials** — create a new credential of type **Mibo Testing API**. Paste your Mibo API key and your n8n API key (Settings → API → Create an API Key, `workflow:read` scope is enough).

   ![Credentials setup](./images/quickstart-credentials.png)

3. **Drop the node at the end of your workflow** — connect it after the last node you want traced.

   ![Workflow with Mibo Testing node](./images/quickstart-workflow.png)

4. **Run the workflow** — the node returns one focused `_miboTrace` summary. Open the Mibo Testing dashboard to see the trace. Turn on **Include Input Data in Output** only when downstream nodes also need the original items.

   ![Node configuration](./images/quickstart-node-config.png)

That's it. No filters, no per-node config, no host-level setup.

## What leaves n8n

The node captures available workflow observations, applies Sensitive Data Protection to cloned parameters, outputs, tool arguments, and user metadata, then sends the canonical trace to **hosted Mibo Testing**. This applies to self-hosted n8n as well. Original workflow items are omitted from the node output by default; enabling **Include Input Data in Output** returns them unchanged.

Automatic Sensitive Data Protection is enabled by default. Custom Sensitive Data Protection is optional and uses deep-search paths such as `email`, `customer.email`, or `customers.*.email`; every matching occurrence is protected before transmission. Encryption at rest does not replace capture-time protection.

## After the first trace

- **Passive evaluation:** configure applicable assertions in Mibo and run the workflow; Mibo evaluates the captured trace and records pass/fail results.
- **Active authoring and validation:** use Mibo smoke tests or trace-grounded test creation to exercise or derive tests from the workflow.

The node captures observations; Mibo owns assertions, replay-like smoke-test execution, test authoring, result history, and reporting. Exact per-node inputs, retries, and timing are unavailable through the supported community-node APIs and are not inferred.

## Troubleshooting

### Payload too large

> `Failed to send trace to Mibo Testing: The trace data is too large to send.`

The node has a **10 MB hard limit per trace**. n8n does not let community nodes gzip outgoing HTTP requests, so the JSON payload travels uncompressed and the limit applies to the raw size. At 8 MB, the output includes a `payload_size` recommendation.

Most common cause: one or more nodes return large outputs — files, base64 images, long LLM responses, or full document bodies — and those outputs get serialized into `n8n.node.output`.

Fixes:

- Strip or summarize heavy fields before the Mibo Testing node (a Set or Code node trimming `data`, `image`, `body`, etc. is usually enough).
- Split the workflow so heavy nodes run in a sub-workflow that is not traced.
- Check `_miboTrace.trace.payloadSize` in the node output. Near the limit, `_miboTrace.recommendations` also contains a `payload_size` recommendation.

### Wrong node names in the trace

The trace uses the **n8n display name** of each node — the same string shown in the editor. If a Mibo `node_call` assertion does not match, it is almost always because the node was renamed in the editor and the assertion still references the old name.

Fixes:

- Open the workflow in n8n and confirm the exact display name of each node (case and spaces matter).
- Update the assertion in Mibo to match the current display name, or rename the node in n8n to match the assertion.
- Auto-utility nodes (`Sticky Note`, `No Op`, `Wait`, `Manual Trigger`, `Respond to Webhook`, the Mibo Testing node itself) are excluded by design and never appear in the trace.

### API key issues

> `The API key does not exist or has been revoked.`
> `Missing x-api-key header.`
> `Could not determine the target agent.`

The node uses two different API keys and they are easy to mix up:

- **API Key** (required) — your **Mibo Testing** API key, from the Mibo dashboard under Settings → API Keys.
- **n8n API Key** (optional) — your **n8n** instance key, used to read the workflow structure.

Fixes:

- If you see "API key does not exist or has been revoked", you pasted the n8n key into the Mibo field (or the Mibo key was rotated). Re-paste the Mibo API key from the dashboard.
- If you see "Missing x-api-key header", the credential field is empty — re-open the credential and save it again.
- If you see "Could not determine the target agent", either set **Agent ID** on the node, or scope the Mibo API key to a single agent in the dashboard.
- If you see "The API key is restricted to specific agents", the **Agent ID** on the node is not one of the agents the key is allowed to use — update one of them so they match.