Mibo Testing icon

Mibo Testing

Capture every executed workflow node and send a canonical trace to Mibo Testing for semantic and procedural testing

Mibo Testing

AI-generated

Summary

Capture executed workflow nodes and send their redacted data as a trace to the hosted Mibo Testing service for storage and evaluation. Add an Agent ID if your API key is not scoped to one agent; optionally configure request correlation, metadata, and sensitive data protection.

Inputs

  • Agent ID — Optional UUID identifying the Mibo Testing agent. Leave empty when the API key is scoped to a single agent.
  • Request ID Override — Optional correlation ID sent as x-request-id. If omitted, the node searches incoming data for an x-request-ID header, then uses the n8n execution ID.
  • Include Metadata — When enabled, adds environment and version fields (defaulting to production and 1.0.0) and optional additional JSON fields to the trace metadata.
  • Automatic Sensitive Data Protection — Enabled by default. Replaces values under common sensitive field names, such as password, API key, token, and cookie fields, with [REDACTED] before sending.
  • Custom Sensitive Data Protection — When enabled, protects values found at the configured field paths. Use dot-separated paths and * for one object or array level; matching paths are searched throughout captured data.
  • Options — Include Input Data in Output defaults to false; when enabled, returns each input item with the trace summary. Timeout (Seconds) defaults to 30 and sets the wait for the Mibo service response.

Output shape

One output item containing _miboTrace by default, or one output per input item with _miboTrace merged into the original fields when Include Input Data in Output is enabled.

The trace summary reports send status, trace ID, request ID and source, timestamp, span and tool-call counts, payload size, captured node statuses, redaction counts, recommendations, and the Mibo app URL. The node captures workflow nodes with available execution data and sends their parameters and outputs after redaction. It needs the workflow graph from configured n8n API credentials or an upstream item containing nodes and connections, and errors if no executed node data is available. API or send errors normally fail the node; with Continue On Fail enabled, the output contains sent: false and error details in _miboTrace.

Links

Discussion