Subscribe to Updates
Get the latest creative news from FooBar about art, design and business.
Author: 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 procurement email came through on a Friday afternoon and I almost missed what it actually said. A fintech client, mid-sized, regulated, the kind of com
For the previous guide in this series, read How to Use n8n to Process a PDF File: Build an AI Invoice Approval Workflow. n8n and Google Opal are both workflow automation tools, but they serve different users. Google Opal is a free, no-code AI mini-app builder from Google Labs. n8n is an open-source workflow automation platform built for developers and technical teams. The core difference is simplicity versus control. What Is Google Opal? Google Opal is a no-code AI app builder from Google Labs that converts plain-language descriptions into shareable AI-powered mini-apps. It is available as a free public beta…
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
I Tested n8n, Zapier, and Make.com on the Same 47-Step Workflow. Only One Finished Without Breaking.
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
