← Features · Integrations

Integrations

Real-Time Webhook Alerting

n8n talks to us. We talk back only on failure.

Ingest is the production path. Email alerts and self-healing are optional and never block verification if delivery fails.

  1. 01

    Ingest webhook

    URL shape: /api/n8n/connections/{id}/executions. Header x-flowsre-secret. Body includes workflow id, execution id, n8n status, and payload. Community node n8n-nodes-flowsre is optional — same check, API key instead of a long URL.

  2. 02

    Email on FALSE SUCCESS

    Settings → incident alerts. One email per new incident (workflow, reason, expected/actual, link). Delivery is queued and retried. A failed email does not change the verdict.

  3. 03

    Self-healing POST

    On a contract you paste an HTTPS webhook. FALSE SUCCESS sends incident id, expected/actual, and the original payload, signed. Auto retry up to three times; manual retry is recorded.

  4. 04

    What we do not do

    We do not poll n8n on your laptop. We do not treat Make as a first-class ingest (n8n HTTP Request still works if Make can POST). CRM tokens are used only for independent GET after SUCCESS — not trusted from the n8n response.

In the product

Setup (copy URL) →Settings →Recipes →
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 →
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 →