The first thing I noticed was the login attempt timestamp. I was reviewing execution logs on a client’s self-hosted n8n instance, a t3.medium on EC2 runnin
Author: Olaitan Oladipo
Olaitan Oladipo
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.
The workflow existed before the test did. It was not something I designed to make a point. It was a real client automation I had been maintaining for about
The workflow had been running clean for six weeks. Forty-three nodes, three HTTP Request calls to external APIs, an OpenAI function-calling block in the mi
The workflow has been running for eight months and I genuinely resent it. Not because it does not work. It works better than most things I have built. I re
Learn how to migrate Make.com scenarios into n8n templates by exporting Make blueprint JSON, converting it with AI, validating the output, and importing the edited JSON into n8n.
Learn how to connect n8n to OpenAI by creating an OpenAI API key, adding it to an OpenAI node credential, saving it securely, and testing the node.
I was in the middle of a Code node trying to flatten a deeply nested SAP API response when the Joule Studio announcement dropped in my feed. The response h
The first sign something was wrong was a workflow that should not have been running. I had a Webhook node sitting at the top of a client’s n8n instance, a
The migration was supposed to take a week. It took three, and the middle one I would prefer to forget entirely. The client had seventeen active scenarios i
The morning SAP announced the acquisition I was three hours into debugging a webhook that was returning 200 but not actually firing. Classic. The workflow