There is a specific GitHub issue I want to describe because it is the clearest illustration I have of why the open-source automation movement keeps winning arguments it has no business winning.
I was debugging an n8n workflow where OAuth2 tokens were not refreshing correctly in production. The workflow ran fine in manual test mode, failed silently on the scheduled trigger, and the execution log showed a 401 that the workflow was not catching because the credential refresh had not fired before the HTTP Request node attempted the call. I spent about forty minutes convinced I had misconfigured the credential before I searched the GitHub issues. The thread I found was six weeks old. Three other people had hit exactly the same thing, described it in exactly the terms I would have used, and in the comments one of the core contributors had explained the specific condition that caused it, linked to a pull request that fixed it, and posted a one-line workaround that resolved it until the fix shipped. Twenty minutes after finding the issue I had a working workflow. The fix was to add a specific header to force the token refresh before the request. That is it.
The equivalent experience with Zapier, which I ran production automations on for two years before migrating off it, does not exist. There is no public issue tracker. There is no way to know if anyone else has hit the same problem. There is a support ticket system that responds with template messages and closes itself after fourteen days. I have no way to look at Zapier’s code, no way to read the internal conversation about whether my bug is a bug or expected behaviour, and no way to find a workaround posted by someone who already solved it. The product is a black box that either works or does not, and when it does not, the resolution timeline is measured in weeks and the outcome is frequently a support agent suggesting I rebuild the Zap.
The reason open-source automation should not work at scale against VC-backed competitors is straightforward and the advantages on the other side are real. Zapier has a team of engineers whose full time job is building and maintaining integrations. Make.com has a design team that has produced a visual workflow builder that is genuinely better looking and more intuitive than n8n’s interface, particularly for users who are newer to the concept. Both companies have dedicated enterprise sales, compliance documentation, SOC2 certifications done properly, and SLAs that a procurement team can actually sign off on. n8n and the broader open-source automation ecosystem are, by comparison, running lean. The documentation has gaps. The UI has rough edges. There are features that have been requested for two years and are still on the roadmap.
And yet. The n8n community Discord has people who actually built the integrations answering questions about how they work. The GitHub issues are public, searchable, and honest about what is broken and when it will be fixed. When I hit the OAuth2 bug, the information I needed was already there, written by someone who understood the codebase, in a form I could actually use. That is infrastructure. The Zapier equivalent is a support portal and a knowledge base article that was written in 2021 and has not been updated since.
The documentation failure mode in open-source tools is different from the documentation failure mode in proprietary ones, and I find the open-source version significantly less frustrating to deal with. When n8n’s docs are wrong or incomplete, which happens, the gap between the documentation and the reality is usually visible in the GitHub issues or the Discord, because the same people who found the discrepancy filed it or discussed it. The docs for configuring the Code node’s external dependencies, specifically the way you have to add npm packages to the n8n instance before they are available in the node, are genuinely unclear about which environment variable to set and what format it expects. I found the correct configuration in a Discord message from eight months ago, not in the official documentation. That is annoying. But it is findable. The equivalent failure in a proprietary tool is a support ticket that eventually resolves itself through your own experimentation with no record anyone else can learn from.
The open-source model keeps winning because the knowledge it generates is collective and persistent. Every bug that gets found and documented publicly becomes a resource for the next person who hits it. Every workaround posted in a GitHub comment is findable by anyone running the same version. The VC-backed model generates knowledge that stays inside the company’s support system and disappears from public view.
What the VC-backed automation platforms have correctly identified is that most enterprise buyers do not value this. They value the appearance of support, the comfort of an SLA, and the ability to point at a vendor when something goes wrong. For that market, the open-source model is genuinely weaker and will remain so.
For people who are actually building things, who need to understand why something is broken rather than just that it is broken, the transparent failure mode of an open-source tool is worth considerably more than the polished opacity of a proprietary one.
The community that forms around a genuinely useful open-source tool becomes the product’s most valuable feature. Zapier’s moat is not its product. It is the fact that switching costs are high and most users have never seriously evaluated whether what they are paying for is actually the best available option for what they need.
Olaitan Oladipo holds a BSc in Sociology from Olabisi Onabanjo University. He is a self-taught automation builder who has spent years inside n8n doing the work that most tutorials skip: debugging OAuth errors at 2am, migrating client automations from Make.com mid-project, fighting reverse proxy misconfigurations on AWS EC2, and figuring out through trial and error what actually holds up in production versus what only looks clean in a demo.
He is not a developer by training and not a SaaS founder. He is the person in the Discord server who actually answers the question instead of linking to the docs.
His writing on n8n Automation Tutorial covers self-hosting, AI agent workflows, tool comparisons, and the security vulnerabilities the automation industry would rather not discuss. He has built AI-assisted invoice approval flows using OpenAI function calling, connected Claude via HTTP Request nodes, and holds considered opinions about Zapier, Make.com, LangChain, and CrewAI that their marketing teams would not appreciate.
He writes for people who are technical enough to follow a tutorial but experienced enough to want the honest version.