Provider setup
Provider setup
Choose one starting path below. Upload a workflow JSON export for immediate static analysis, or connect a live n8n instance for continuing inventory and runtime evidence. You can add the other path later.
No connection is required for file analysis. A live connection is only needed when you want FlowSentinel to keep reading workflow inventory and new runtime evidence.
Upload a standard n8n workflow JSON export to inspect node and connection integrity, external-call resilience, webhook hardening, disconnected paths, branching pressure, and the runtime proof still missing before anyone calls the workflow safe or recovered.
The artifact is parsed but never imported, queued, or executed. FlowSentinel stores the sanitized report and findings, not the raw file. Static evidence cannot prove credentials, target-environment compatibility, successful execution, downstream outcome, or recovery.
Use a public HTTPS n8n API URL ending in /api/v1 and a read-capable API key. FlowSentinel verifies access before saving the encrypted credential and syncing workflow inventory.
This checks FlowSentinel's shared, isolated n8n execution engine. It is not evidence about your connected workflow.
FlowSentinel qualifies one pinned, credential-free n8n workflow automatically on production releases. The check requires the exact CLI contract and output, a platform-confirmed deny-all policy, zero permitted external egress, and completed Sandbox teardown.
This is shared platform infrastructure evidence. It cannot satisfy baseline, qualification, replay, connection, credential, workflow-behavior, or recovery proof for a customer workspace. Raw Sandbox session transfer is control-plane telemetry and is shown separately from permitted external egress.
Loading shared platform runtime evidence…
Platform diagnostics prove FlowSentinel's isolated n8n engine only. An export proves visible workflow structure only. This does not prove that credentials work, environment variables exist, external systems accept the current payload, or a recent execution completed successfully.
A live connection adds workflow inventory and scanner coverage. Recovery proof, freshness confidence, and change-over-time trends still require observed runtime or verification evidence after the connection is live.