← Features · Core Engine

Core Engine

Outcome Verification & Contracts

SUCCESS is n8n. VERIFIED is FlowSRE.

FlowSRE does not log into your n8n. The last HTTP Request node POSTs the run to us. Then we open the destination ourselves and compare it to the contract.

  1. 01

    n8n calls FlowSRE

    Copy the ingest URL and x-flowsre-secret from Setup. Last node in the workflow: HTTP Request, POST. FlowSRE never needs your n8n API key for this path. Your n8n can stay private.

  2. 02

    A contract is the expected result

    After n8n status is SUCCESS, one contract must hold. Default: a Google Sheet row exists (lookup email ← lead.email, status = qualified). Optional second check: FlowSRE GETs HubSpot / AmoCRM / Bitrix by ID. Missing record = FALSE SUCCESS even if n8n was green.

  3. 03

    Engine verdicts

    VERIFIED — destination matches. FALSE SUCCESS — n8n succeeded, outcome did not. TECHNICAL_FAILURE — n8n itself failed. PENDING — still checking. Each check writes an immutable verification attempt with expected vs actual.

  4. 04

    Incidents stay on the contract

    FALSE SUCCESS opens an incident tied to that execution and contract. You acknowledge or resolve it. Optional self-healing POSTs the evidence back to an n8n webhook, up to three automatic retries.

In the product

Contracts →New contract →Setup →Live demo →
Try Live Demo →Start 7-Day Free Trial

The other three

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 →
Observability

Audit Logs & Client Reporting

Every verdict is stored. Reports turn VERIFIED vs FALSE SUCCESS into a month’s SLA pack you can export for a client.

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 →