Your entire n8n estate, observable from one API key.
Paste one read-only API key and Obsivara maps everything: every workflow, node, execution, and credential. Pull-based sync every five minutes, zero changes to your workflows — and when something breaks, you get the exact node that failed and why, not a wall of execution logs.
n8n, fully observable.
Node-level failure attribution
Every failed execution traced to the exact node that broke, with the error, timing, and everything downstream that never ran because of it.
Credential risk map
Every credential mapped to every workflow it touches. Know the blast radius before a key leaks, and get nudged when one goes too long without rotation.
Change audit with impact correlation
Every workflow edit versioned and diffed — who changed what, when — and error spikes correlated back to the exact change that caused them.
Failure prediction
Every workflow scored 0–100 on failure risk from error trends, latency drift, and dependency health — with 24-hour early warning on the ones about to break.
Three steps. No code changes.
Create a read-only n8n API key
In your n8n instance settings, generate an API key. Read-only is all Obsivara ever needs.
Paste it into Obsivara
First sync completes in about five minutes: full inventory of workflows, nodes, executions, and credentials — no agents to install, no workflow edits.
Watch the estate light up
Health scores, failure predictions, cost attribution, and the credential map populate automatically. Sync refreshes every five minutes.
Signals tracked out of the box.
- →Execution success / failure per workflow
- →Failing node, error class, and timing
- →Downstream nodes skipped by failures
- →Credential usage and rotation age
- →Workflow changes (diffs, author, time)
- →Failure-risk score per workflow (0–100)
Common questions.
Do I need to modify my workflows?
No. The integration is pull-based via the n8n API — zero workflow changes, no webhooks to add, no nodes to insert. Your workflows don't know Obsivara exists.
Does Obsivara work with self-hosted n8n?
Yes — self-hosted and n8n Cloud are both supported. For self-hosted instances behind a firewall, Obsivara connects over an outbound-only tunnel.
Can Obsivara change or pause my workflows?
No. The API key you provide is read-only, and Obsivara is architecturally observe-only. It can tell you a workflow is about to fail; acting on that stays your call.