Inside Zo.E
The Technical Docs
Buyer education articles explaining how the Zo.E system works — n8n, Gemini, webhooks, data structure, and the full £30/month stack.
- D01
Why Zo.E runs on n8n
When you import these JSON files, the first thing you'll notice is that every workflow is a visual graph — nodes connected by lines, branching left and right, looping back on themselves. That's n8n. And once you…
2 min read - D02
The AI Brain of Zo.E: How Gemini Actually Works Inside WF2
Most people assume the interesting part of an AI automation is the workflow plumbing. It isn't. In Zo.E, the plumbing took a weekend. The prompts took weeks.
2 min read - D03
How Webhooks Work — and Why Zo.E Runs on Them
Every time I tap Approve on my phone and a post goes live thirty seconds later, that's a webhook doing its job.
2 min read - D04
The Real Secret to a Workflow That Doesn't Break
The tools are the easy part. n8n, NocoDB, Gemini, Upload Post — you can replace any of them. What's harder to replace, and what causes the most breakage when it goes wrong, is the data structure underneath.
2 min read - D05
The £30/Month Stack That Runs Two Brands
There's a trap a lot of people fall into when they decide to take content seriously. They see what big companies spend on marketing technology and reverse-engineer the logic: ambitious goal, expensive tools. So they…
2 min read - D06
From Approved to Published: How Zo.E Handles Distribution
Most people who automate content generation still post manually. They'll have AI write the copy, maybe even format it — then open LinkedIn, paste it in, and hit publish themselves. That's not automation. That's…
2 min read - D07
The Input Problem: How Zo.E Finds Something to Say
You can build a beautiful machine and starve it in week three.
3 min read