🧪 New Free Tool: Get a Quality Score for Your n8n Workflows!

Built with n8n
1

Ever looked at one of your n8n workflows and thought:

“Hmm… this works, but should it?”

Introducing our new Workflow Scoring Tool – a free service by n8nhackers.com that gives you a quality report for all the workflows you have in your n8n.

:bar_chart: What does it analyze?

Each workflow is scored across key categories that impact maintainability, performance, and scalability:

Category Description
:brain: Memory Leaks Indicates if the workflow has potential memory leaks from the use of Code, Function, or FunctionItem nodes. A higher score means better memory leak control.
:gear: Performance Measures how well the workflow performs. Looks for bottlenecks like sequential HTTP calls or unnecessary waits. Higher is better.
:eye: Readability Indicates how readable the workflow is — use of sticky notes, clear node names, and layout. A higher score means easier to understand.
:closed_lock_with_key: Security Evaluates secure use of webhooks and credential handling. Higher scores mean safer workflows.
:stop_sign: Error Handling Checks for proper use of Error Trigger or continueOnFail. A higher value means more robust error control.
:jigsaw: Complexity Indicates how complex the flow is. More nodes and tangled logic reduce your score. Simpler = better.
:chart_with_upwards_trend: Scalability Analyzes if the workflow is designed to scale, especially through subflows. Higher scores mean it can grow safely.
:arrows_counterclockwise: Modularity Rewards use of subflows and reusable logic. Modular = maintainable.
:package: Idempotency Evaluates if the same execution can run multiple times without side effects. Critical for reliability.
:rocket: Throughput & Latency Measures how fast and how much the workflow can process. Batch vs item-by-item? Parallelism? High = good.
:white_check_mark: Total Score A combined view of all the above. Gives you a snapshot of your workflow’s overall quality.

:wrench: Why does this matter?

  • Catch design issues before they become incidents
  • Make workflows easier to debug and collaborate on
  • Scale confidently with clean, testable automations
  • Stop losing time in spaghetti logic and painful error hunts

:rocket: How to use it?

You can get automated scorings for all your workflows if you:

  1. Add your n8n to the Installations section.
  2. You can get an enhanced scoring report by enabling OpenAI integration in the Integrations section.

After the first sync, you get a full scoring table, a list of warnings, and recommendations for improvement (only when OpenAI enabled).

Find below an enhanced scoring report by AI:

Scoring Report

1. Scorings Table

Category Score (out of 10)
memory_leaks 10
performance 10
readability 10
security 10
error_handling 0
complexity 10
scalability 0
modularity 5
idempotency 10
throughput_latency 10
Total 75

2. Recommendations to Improve Scorings

memory_leaks (10)
• Periodically profile memory usage in production to catch regressions early.
• Implement health‐check dashboards or alerts for abnormal heap growth.

performance (10)
• Introduce caching for frequently accessed data or API responses.
• Run load tests to validate throughput under peak conditions.
• Optimize any long‐running functions or reduce node execution time.

readability (10)
• Enforce naming conventions and add descriptive comments on complex steps.
• Maintain a workflow README or documentation for onboarding new contributors.

security (10)
• Rotate and vault sensitive credentials (use n8n’s built-in credential store).
• Scan for unused or over-privileged credentials and clean them up regularly.

error_handling (0)
• Add an Error Trigger node to catch and route runtime failures.
• Configure onError behavior on critical nodes (continueRegularOutput or continueErrorOutput).
• Define a global errorWorkflow in workflow settings to centralize retries/notifications.

complexity (10)
• Keep steps atomic and well-bounded—avoid overloading a single function with multiple responsibilities.
• Document any advanced logic or nested conditionals to aid future maintenance.

scalability (0)
• Replace or batch Wait nodes where possible—consider external rate-limiters or queuing.
• Refactor large workflows into smaller, independently deployable subflows for horizontal scaling.
• Leverage n8n’s execution queue settings (concurrent executions, fair scheduling).

modularity (5)
• Extract repeated or logically distinct segments into Subflows for reuse.
• Encapsulate domain-specific operations (e.g., data validation, API orchestration) into reusable modules.

idempotency (10)
• Ensure external API calls are safe to retry by using idempotency keys or checks.
• Log request identifiers and results to avoid duplicate processing on replays.

throughput_latency (10)
• Monitor node-to-node latency and set up alerts on SLA breaches.
• Tune concurrency settings (e.g., increase “Max Concurrent Runs” where safe) to reduce end-to-end latency.

The spaghetti monster should only live in your mind… not in your workflows. :spaghetti::skull:

Workflow Scoring Tool is a tool built by the team at n8nhackers.com —
“It works” isn’t where the story ends — it’s where it begins.

:hammer_and_wrench: Feature suggestions and feedback welcome! :wink: