n8n Linter - Flowlint

By Piotr Sikora

  • n8n

  • 28 November 2025

Hey n8n community!

It reviews your pull requests, applies configurable lint rules, and provides detailed annotations to catch automation bugs before deployment.

I added it to my repository today, and it immediately revealed that some of my workflows need fixing.

It’s a great tool - you can lint your workflows just like JS or Python code. All you need to do is add the plugin to your repository in GitHub.

Below are screenshots of my workflow before and after applying the fixes, as well as a screenshot from flowlint.dev.

Have you worked with it before?

Thanks Martin Holý for sharing this tool with community!

PS. Martin Holý will it be possible to run it locally without pushing it to repository?

Before using n8n linter - Flowlint.dev

My workflow before using n8n linter - Flowlint.dev was shown below:

n8n workflow before Flowlint

Flow includes basic error handling, but it's not enough. After installation of Flowlint.dev, it immediately revealed that some of my workflows need fixing. (Installation instructions: https://flowlint.dev/doc/)

Flowlint.dev report

Below is the basic report from Flowlint.dev:

n8n workflow after Flowlint

I started fixing my workflow based on the report. Steps which I took:

  • I named my nodes to be more descriptive
  • I added basic error handling in Google Sheet nodes
  • I needed to add retry in HTTP Request nodes

After using n8n linter - Flowlint.dev

After fixing my workflow, it was shown below: n8n workflow after Flowlint

Workflow is now much better and more secure. It handles errors and retries, and it's more maintainable because of node names.

Summary

Flowlint.dev is a great tool for linting n8n workflows. It helps you to catch errors and security issues before deployment. It's a great tool for maintaining a high quality of your workflows.

The only issue for now is that it can't be run locally without pushing it to repository. It would be great to do it locally to catch issues before pushing to repository as it reduces the number of commits and makes the process faster.

Additionally in case of security it would be great to have a local linter to remove 3rd party dependencies in Github tools.

Check it on your own: https://flowlint.dev/

It reveals a lot of issues which are not visible in n8n editor.

Categories

Recent Posts

About Me

Piotr Sikora - Process Automation | AI | n8n | Python | JavaScript

Piotr Sikora

Process Automation Specialist

I implement automation that saves time and money, streamlines operations, and increases the predictability of results. Specializing in process automation, AI implementation, and workflow optimization using n8n, Python, and JavaScript.

n8n Workflows

n8n workflow automation templates

Explore my workflow templates on n8n. Ready-to-use automations for blog management, data collection, and AI-powered content processing.

3Workflow Templates

• Auto-Categorize Blog Posts with AI

• Collect LinkedIn Profiles

• Export WordPress Posts for SEO