Provider setup
Provider setup
Choose one starting path below. Upload a scenario blueprint for immediate static analysis, or connect Make for continuing scenario inventory and monitoring. You can add the other path later.
No token is required for blueprint analysis. Connect Make only when you want current provider inventory, scanner evidence, and ongoing monitoring.
Upload a Make blueprint JSON export to inspect module and route integrity, external-call resilience, webhook hardening, branch fan-out, disconnected paths, and the runtime proof still missing before anyone calls the scenario 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.
Paste a token from your Make account to enable continuing read-only monitoring. FlowSentinel verifies the token and stores it encrypted, and the token can be removed from Make at any time.
This uses a token for one provider-native scan and discards it after the request. It gives stronger live inventory evidence than a file, but it still does not create continuing monitoring.
Paste your API key and choose region. We run a read-only scan and discard the key right after use—nothing is stored on FlowSentinel.
A blueprint proves visible scenario structure only. It does not prove that connections are authorized, live payloads still match route assumptions, external services accept writes, or a recent execution completed cleanly.
Live scans add provider inventory and current scenario details. Recovery, downstream business outcome, and ongoing health still require observed execution and follow-up evidence.