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.
A client’s AI email response workflow sent a message last August that opened with the name and order history of a completely different customer. The workflow had pulled data from the wrong CRM row and the AI had formatted it politely. The email went out before anything flagged it as wrong. That is the problem Zapier’s new AI Guardrails is trying to address, and it is a real problem. Zapier launched AI Guardrails in March 2026, and the feature runs PII detection, prompt injection screening, and toxicity flagging inside Zaps and Agents. It intercepts AI outputs before they reach CRMs…
I was mid-client project when Make’s CTO dropped the Maia announcement, and I stopped what I was doing to test it. Maia is a conversational AI layer inside the Scenario Builder where you describe a workflow in plain language and it generates the full visual scenario. The demo looks compelling. The thing buried in the release notes does not. AI-powered workflows in Make now consume three to five times more credits than standard scenarios. Make’s announcement mentioned this as a pricing consideration, but the framing was gentle enough that most coverage glossed over it. At high volume, that multiplier does…
I was debugging a Claude integration inside an n8n workflow when the MCP Server Trigger node appeared in an update. I had been building the same thing manually: HTTP Request to the Anthropic API, a Code node parsing the tool call response, another HTTP Request firing the downstream action. The native node made half of that unnecessary. I closed the tab and rebuilt the flow from scratch. MCP stands for Model Context Protocol. Anthropic released it as an open standard for how AI models communicate with external tools and data sources. Instead of hardcoding API calls yourself, you define tools…
I found out about Zapier deprecating Functions from someone in a Discord server, not from an email or a changelog I actually opened. They posted a screenshot and said "wait, is this actually gone?" I checked. The May 2026 product update confirmed it: Functions was being deprecated, and the migration guidance was thin. Functions was the feature that let you run JavaScript inside a Zap when standard action blocks stopped being enough. If you needed to parse a nested JSON response three levels deep, or do a string transformation no native action covered, Functions was how you did it. The…
I was mid-deployment on a client’s EC2 instance when CVE-2026-21858 dropped into my feed. They were already calling it Ni8mare, and that name made immediate sense. I had three production n8n servers running and two had public-facing webhook endpoints. The vulnerability enabled unauthenticated remote code execution on any exposed n8n instance. No credentials, no prior access, no social engineering required. A single crafted HTTP request was sufficient to execute arbitrary code on the host. What makes this particularly serious is what n8n instances typically hold. My servers carry credentials for client AWS accounts, Salesforce orgs, and OpenAI API keys. A…
Install Puppeteer in n8n with the n8n-nodes-puppeteer community node, then test browser automation by capturing a webpage screenshot.
Learn how to configure Retry on Fail in the n8n HTTP Request node and connect failed workflows to an Error Trigger workflow that sends actionable Gmail alerts.
n8n and Power Automate are 2 workflow automation platforms that serve different types of teams. n8n is an open-source workflow automation platform built for flexibility and developer control. Power Automate is Microsoft’s cloud-based automation tool, deeply integrated with the Microsoft 365 ecosystem, including Teams, SharePoint, Dynamics 365, and Excel. The right choice depends on your team’s technical profile, existing software stack, and budget. For the previous guide in this series, read LangGraph vs n8n: 2 Frameworks, 5 Core Differences, and Which One Fits Your AI Workflow in 2025. What Is n8n? n8n is a source-available, node-based visual automation platform. It…
For the previous guide in this series, read Dify vs n8n – 7 Key Differences Between an AI App Builder and a Workflow Automation Platform. LangGraph and n8n are both open-source tools for building automated workflows, but they serve fundamentally different purposes. LangGraph is used for building sophisticated AI agents where the execution path depends on the model’s reasoning, tool outputs, and stateful memory across multiple interaction steps. n8n is primarily used for automating business workflows such as syncing CRM data, sending notifications, processing form submissions, and integrating SaaS tools without requiring extensive coding. What Is LangGraph? LangGraph is an…
The moment I knew something had shifted permanently was not the Mercedes-Benz announcement or the Series B or any of the coverage that followed. It was a T