Workflow Analyzer
v7 • Most PopularThe Swiss Army knife for n8n debugging. Compare workflow versions, detect webhook collisions, validate router→handler contracts, and catch common bugs before deployment.
Open AnalyzerFeatures
Health Check Analysis
Detects expression syntax errors, missing configs, orphaned nodes
Version Comparison
Word-level diff with LCS algorithm, export as Markdown
Webhook Collision Detection
Find when multiple workflows share the same endpoint
NEW: Compatibility Check
Catches body.body nesting bugs, validates router→handler contracts
More Tools
Demo Dashboard
NEWInteractive preview of Sanctuary operations dashboard with sample data.
- • Real-time fake data
- • Orders, members, credits
- • Auto-refreshes every 30s
Bible Generator
Auto-generate documentation from n8n workflows, SQL schemas, and config files.
- • Multi-file upload support
- • Structured Markdown output
- • Environment variable extraction
Cron Builder
Visual cron expression builder with human-readable descriptions.
- • Point-and-click interface
- • Preview next run times
- • Copy to clipboard
Env Generator
Extract environment variables from workflow JSON files.
- • Scan workflow expressions
- • Generate .env templates
- • Identify missing vars
Task Extractor
Pull TODOs, FIXMEs, and NOTEs from your codebase.
- • Priority detection
- • File location tracking
- • Export to Markdown
Flow Visualizer
Interactive Mermaid diagrams of workflow execution paths.
Coming SoonCredential Validator
Check if referenced credentials exist and are valid.
Coming SoonWhy 100% Client-Side?
Your Data Stays Yours
Workflows contain sensitive business logic. We don't want your data - it never leaves your browser.
Works Offline
After the first load, everything is cached. Use these tools on planes, in bunkers, wherever.
No Account Required
No signup, no tracking, no cookies. Just open and use. Forever free.
Common Use Cases
🐛 "Why is my webhook returning 404?"
Use the Compatibility Check to verify your handler workflow is active and the webhook path matches what the router is calling.
🔄 "What changed between these versions?"
Use Compare to see exactly which nodes and parameters changed, with word-level highlighting. Export as Markdown for your changelog.
📦 "My handler receives data at body.body"
The Compatibility Check specifically detects this nesting issue before you deploy. It happens when your HTTP Request body contains a field named "body".
📝 "I need to document 40 workflows"
Use the Bible Generator to auto-generate structured documentation. Upload your exports and copy the Markdown.
Ready to debug smarter?
Start with the Workflow Analyzer - it's the tool we use every day before deploying changes to production.
Open Workflow Analyzer