n8n agent monitoring with platform-aware detectors

n8n agentic workflows fail differently from code-based agents: timeouts at HTTP nodes, complexity overflow when an LLM node returns to a sub-workflow, error propagation across nested workflows. Pisama ships six n8n-specific detectors calibrated against real n8n traces.

The integration is via n8n webhooks: configure a single webhook node to forward execution data to Pisama, and detectors run on every workflow execution. No code changes to your n8n flows.

Detectors specific to n8n

  • Timeout analysis
    F1 0.959: node-level timeout patterns and thresholds
  • Resource exhaustion
    F1 0.949: memory/queue-depth signatures
  • Complexity overflow
    F1 0.841: sub-workflow nesting + branching explosion
  • Cycle detection
    F1 0.812: workflows looping through the same node set
  • Error propagation
    F1 0.805: error nodes triggered downstream of root cause
  • Schema validation
    F1 0.765: output schema drift between executions

Install

# Configure a webhook node in n8n pointing to your Pisama ingest URL
// In your n8n workflow, add an HTTP Request or Webhook node:
// URL:    https://api.pisama.ai/v1/n8n/ingest
// Header: Authorization: Bearer <PISAMA_API_KEY>
// Body:   {{ $execution.json }}

FAQ

Do I need to modify every n8n workflow?
No. A single webhook trigger at the workflow start (or a global error workflow) forwards execution data. Detectors run server-side on the trace.
Does this work with n8n self-hosted?
Yes. Self-hosted, n8n Cloud, and embedded deployments all work the same way. The webhook is the integration surface.

See the full detector taxonomy at /taxonomy, benchmark numbers at /benchmarks, or compare against other observability stacks at /vs.