Blog 23 — Automation Diaries, Episode 2

After the Make disaster of Episode 1, we did what all intelligent people do after trauma: we decided the problem was structure. Not tools. Not complexity. Structure. So we rebuilt everything.

The Notion databases became temples: Membership, Artists, Media, Exhibitions. Every field carefully designed — consent fields, status tags, relations, upload properties, filtered views with logic that would impress NASA. We debated field names like diplomats negotiating borders. “Artist Name or Full Name?” “Submission Source or Entry Type?” “Should Status be Select or Multi-Select?” This went on for weeks. Weeks. But it was beautiful. Opening the database felt like walking into a perfectly organised museum storage room where nothing had dust and everything had a label. We were proud. That was the first mistake.

Then came the integration: Make ↔ Notion. The promise was simple — form submission → automation → database entry → done. Except… not done.

The first problem was mapping. Scrolling fields disappeared when mapping was enabled, so we manually entered database IDs like medieval monks copying manuscripts. One character wrong? Nothing works. Correct ID? Still nothing works. Then images arrived broken: URLs instead of files, files instead of URLs, sometimes both, sometimes neither. At one point we had an automation that successfully transferred absolutely nothing with perfect consistency, which is almost impressive.

We adjusted. Simplified. Removed relations. Added fallback logic. Changed modules. Sacrificed elegance for survival. Finally — finally — one test submission passed. We celebrated like astronauts. Then the second submission failed.

This is the emotional turning point nobody tells you about: the database was perfect, the system was not. Perfection without movement is useless. I stared at the dashboards. Everything looked ready. Nothing was happening. It felt like building a train station with no trains.

MINION appeared, arms crossed, deeply unimpressed.
“Now listen carefully,” he said.
“You do not have an automation problem. You have a tool mismatch.”

I did not want to hear that, because we had invested time. Humans hate abandoning time investments. But he was right. The more we forced Notion into being a live processing system, the more friction appeared. Notion wanted to be organised. We wanted it to be operational. Those are not the same thing.

The breaking moment came quietly: another failed sync, another missing file, another module adjustment. And I heard myself say, “This shouldn’t be this hard.” That sentence changes everything, because when something shouldn’t be hard but is, you stop blaming yourself. You start questioning the architecture.

We had built a cathedral. What we needed was a warehouse. And that realisation hurt. A lot.

⭐ Best Quote
“We built a perfect system. It just didn’t move.”

📜 Goat Bible Verse
When the structure is flawless but the flow is blocked, the wise Goat does not polish the walls. She opens another door.

Next episode: The dangerous sentence that changed everything.
“Fine. We’ll use Google Sheets.”