← Features · Observability

Observability

Audit Logs & Client Reporting

Evidence first. Then the PDF.

Dashboard is the live stream. Execution detail holds redacted input/output JSON and the verification audit trail. Reports aggregate that month for clients.

  1. 01

    Live executions

    Dashboard lists the last 100 runs: n8n status next to FlowSRE status. FALSE SUCCESS rows link to the incident. Workflow pages show the same history per automation.

  2. 02

    Audit trail on the execution

    Open a run: status history, attempts (duration, reason, contract), and JSON in a side drawer. Secrets are redacted. That is the log you show when someone asks “why did you flag this?”

  3. 03

    Incidents

    Open incidents are outcome failures, not n8n crashes. Expected vs actual stays on the incident. Recovery attempts (self-healing) are in the same drawer.

  4. 04

    Reports for the month

    Reports computes verified %, false-success %, executions checked, and incidents caught. Export Audit PDF or CSV. Value saved is an assumption you set (currency × incidents) — labeled as an estimate, not guaranteed revenue.

In the product

Dashboard →Incidents →Reports →
Try Live Demo →Start 7-Day Free Trial

The other three

Core Engine

Outcome Verification & Contracts

n8n can return SUCCESS while the sheet row or CRM record never appears. A contract is the independent check FlowSRE runs after that SUCCESS.

How it works →
For Agencies

Multi-Tenant Agency Control

Each client is a separate workspace: own ingest URL, executions, and incidents. Pro adds client workspaces, white-label, and a custom domain.

How it works →
Integrations

Real-Time Webhook Alerting

n8n POSTs every run to FlowSRE. When the outcome is missing, we email FALSE SUCCESS and can POST a recovery webhook back into n8n.

How it works →