So I’d been using Notta — a meeting transcription SaaS — on a yearly subscription. Genuinely useful. But the renewal date was creeping up, and shelling out for another year felt wasteful…

“Why not have an AI sit in on the meeting and write the notes? Just throw it on my home server?”

That’s the thinking I started with. Bottom line up front: it has never worked cleanly even once. Here’s an honest breakdown of where it broke, case by case.

What I tried: a “meeting notes bot”

The picture I wanted:

1. Throw a meeting link at the bot
2. Bot joins the meeting on its own
3. After the meeting ends, notes show up in chat

Supported platforms: Google Meet, Microsoft Teams, Cisco Webex. (Zoom — code’s there, but I don’t use it personally so it’s untested.)

Failure case 1: can’t get into the meeting room

The first wall. Each platform has its own way of letting you in, and each one breaks differently.

Google Meet — outside-org users blocked

If a company uses Google Workspace, an external bot is just blocked. “Users outside the organization can’t join.” End of story.

The workaround would be to have the bot log in with my own Google account. Once you log in, a cookie (a small piece of info the browser uses to remember “I know who you are”) gets saved, and the bot uses that to enter from then on.

But hooking my company Google account up to a bot felt sketchy. Security-wise iffy, plus 2-step verification (that thing where you also have to enter a code from your phone) trips it up every time. So I just gave up on Google Meet. Even though most of my work meetings are on Meet.

Teams — CAPTCHA shows up

“Type the characters you see.” That CAPTCHA (the thing websites use to check “are you actually human?” with distorted text). It pops up 100% of the time the bot tries to join.

The fix: feed the CAPTCHA image to Gemini Vision (an AI that can read text out of images) and have it type the answer. If the first attempt fails, refresh and try again. Up to 3 tries, then give up.

I have this coded in, but Gemini occasionally reads the wrong letters. Not smooth.

Webex — everything’s inside a frame-within-a-frame

Webex runs the entire meeting UI inside an iframe (a structure where one full webpage is embedded inside another — think picture-in-picture). When the bot tries to find a “mute mic” button on the outer page, it’s not there. You have to dig into the inner frame.

Debugging this took 5 separate “snap a screenshot at this step” hooks in the code. (“Did we grab the inner frame?” → “Inner frame loaded too slow, retry” → “Still no inner frame? One more time…”). If the frame fails to load, fall back to plan B; if plan B also fails, plan C. I keep adding workaround code per case.

Common: 5-minute host approval timeout

Even after all of that, you land in the lobby. The host has to click “Admit” before you’re in.

The bot waits up to 5 minutes and then bails. If the host starts the meeting 5 minutes late? The bot’s already gone. Have to send it again.

What it looks like in practice: “Sent the bot, the meeting ended, and I got a chat saying it never made it in.”

Failure case 2: recording saved as a 0KB file

This is the one that happened most often.

The bot got into the meeting. The bot’s status said “Recording.” But the file I got back after the meeting? A zero-second empty file.

Cause: how the audio is captured. The bot drops a tiny “hook” into the audio stream (“hook” in the dev sense — code that latches onto data flowing past, like a fishing line) inside the meeting page to record. But meeting sites change their internal structure constantly, so the hook lands in the wrong spot and pulls in nothing. The bot reports “recording started!” while the actual file is 0 seconds long.

After eating this a few times I added a backup move (if plan A fails, automatically try plan B). It still hands me empty files now and then.

What it looks like in practice: “Hour-long meeting wraps up, chat pings me — file is 0KB. Thought it was recording. It was 0 from the start.”

Failure case 3: no place to type in attendee names

This problem sat unfixed for a long time.

The whole point of meeting notes is who said what. The bot does try to read speaker names off the screen automatically, but if someone has their camera off or the layout changes in a way the bot can’t see, the name doesn’t get caught.

So a human has to fill in names afterward. The old version had no step for that at all. Bot ends meeting → instantly generates notes → done. If a name was wrong, no recovery.

I recently added a flow where, after the meeting, the bot pauses and waits for me to chat back the attendee list (“attendees are Mr. Kim and Ms. Lee”), and only then generates the notes.

But I haven’t actually tested this fix. Case 2 above (the 0KB recording) keeps blowing up on Webex, and if there’s no recording there’s no notes to attach names to — so the new feature can’t be verified.

What it looks like in practice: “Fixed one thing, but something else is broken downstream so I can’t even test the new feature.”

Failure case 4: the one set of notes I did get back was mediocre

After clearing all the above, I’ve actually received meeting notes exactly once — from Webex. (Meet: gave up. Teams: CAPTCHA solved but the recording broke after.) That single set of notes had two problems.

I had Gemini Flash (Google’s free AI) generate the notes.

1. The writing quality is meh

Run the same transcript through Gemini Pro and the notes come out much more natural, with the key points actually surfaced. Flash is free, which is great, but the notes feel awkward and the gist gets blurred.

2. Markdown shows up raw in Telegram

Gemini outputs notes in Markdown (a convention where “two asterisks = bold”, “hash = heading”, etc. The format Notion or GitHub silently renders for you), but Telegram doesn’t render it. So I get this on screen:

## Decisions
- **Option A approved**
- ~~Option B~~ on hold

Hard to read. I asked for clean notes; what I get looks like raw scribbles with asterisks and hash marks.

What it looks like in practice: “Notes generated, but the writing’s awkward and Markdown symbols sit there raw. Not readable.”

So where am I now

Honestly, I have never had a meeting → automatic notes flow run end-to-end cleanly. One of the four failure modes above hits every single time.

What I’m currently working around / fixing:

• Joining meetings: I gave up on full automation entirely. Manual approval per meeting + secondary account.
• 0KB recordings: still patching the audio-capture fallback. Still drops files occasionally.
• Attendee-name step: built. Just need Webex recording to stabilize before I can verify it.
• Notes quality: trying Gemini Pro and weighing cost vs. quality. Planning to add Markdown → HTML conversion before sending to Telegram.

Wrapping up

Why write this if nothing’s actually finished? Two reasons.

1. To give anyone trying to build the same thing a heads-up: “this is harder than it looks, plan for the time.”
2. So that later, when it actually works, I can write a “back then it was all broken, now it looks like this” follow-up.

For now, I’m leaning on Notta to get through actual work, and pushing on the meeting bot in the background. Building it from scratch made me appreciate why Notta charges what it does — you have to clear every one of these cases before you reach that level.

I’ll write a follow-up once it’s actually usable. When all four cases pass reliably and I can finish a meeting and have the notes show up without touching anything.

Automation isn’t a one-shot achievement — it’s slow improvement, case by case, hitting walls and routing around them. I can’t code, but I keep asking AI “why doesn’t this work?” and inching forward step by step.

Next post will be on something a bit cleaner.

The post Even a Code-Illiterate Built It! Home Server Journey (9) — Trying to Automate Meeting Notes, and Failing in Every Single Way appeared first on Prsm Studio.

“I just want to set it up once and have it run itself.”

That’s why I installed n8n. After setting up a few workflows, my server now works on its own. All I do is check Telegram notifications.

What is n8n? One-Line Summary: Free Zapier

n8n (pronounced “n-eight-n”) is a visual automation tool. If you’ve used Zapier or Make (formerly Integromat), it’s exactly that. Drag blocks onto a canvas, connect them with lines, and your automation is done. Code? Not a single line needed.

The one difference: it runs on your own server. That means it’s free, there are no execution limits, and your data never leaves your machine.

If you already have a home server, there’s no reason not to use n8n. Especially if you’ve ever hit Zapier’s free tier limit of 100 executions per month.

Installing n8n: One Docker Compose File

Remember how we set up Docker in Episode 1? We just add n8n on top of that.

services:
  n8n:
    image: n8nio/n8n:latest
    ports:
      - "5678:5678"
    volumes:
      - ./data:/home/node/.n8n
    environment:
      - N8N_BASIC_AUTH_ACTIVE=true
      - N8N_BASIC_AUTH_USER=admin
      - N8N_BASIC_AUTH_PASSWORD=yourpassword
    restart: unless-stopped

Tell Claude “install n8n” and it creates this file and runs docker compose up -d for you. Navigate to http://yourServerIP:5678 and you’ll see this:

At first glance it might look intimidating. But give it five minutes. You drag nodes (blocks) from the left panel onto the canvas and connect them with lines. It’s like building with LEGO.

Real Workflow #1 — Auto-Sync Dev Logs to Notion

I’m building an app called Prsm. (A non-coder building an app? Yep, I just tell AI what to do. That’s a story for another post.) Every day I write development progress in a file on GitHub. I wanted those logs copied to Notion automatically.

Doing it manually:

1. Open GitHub
2. Find today’s log file
3. Copy the content
4. Open Notion
5. Paste into the Day Log page
6. Add a date tag

Five minutes a day. Doesn’t sound like much, but that’s two and a half hours a month. And honestly, I forget to do it most days.

After automating with n8n:

Every night at 11 PM → Read file from GitHub → Auto-add to Notion Day Log

Three nodes. Set it up once, and it runs every night by itself. What I have to do: nothing. When I open Notion in the morning, last night’s log is neatly organized and waiting for me.

Real Workflow #2 — Auto-Monitor Blog Google Indexing

No matter how good your blog post is, if Google hasn’t indexed it, nobody can find it through search. This is especially brutal for new blogs — it’s common for posts to go unindexed for days after publishing.

Checking manually? You’d have to log into Google Search Console and inspect each URL one by one. Ten posts means ten checks.

n8n handles it:

Every 12 hours → Get list of published post URLs → Check Google indexing status → Unindexed post found? → Send Telegram alert

“Hey boss, episodes 3 and 5 still aren’t indexed on Google!” — I get alerts like this on Telegram. Then I just click “Request Indexing” in Search Console. Done.

Real Workflow #3 — Instant Alert When Server Goes Down

When you’re running multiple services on a home server, one of them can quietly die without you noticing. Once, Immich crashed after an update and I didn’t realize for over a day. That was a full day of photos not being backed up.

So I built this workflow:

Periodic check → Ping Immich → Ping OpenClaw → Ping WordPress → Any service down? → Send Telegram alert

Now when a service goes down, I get notified within minutes. After setting up this workflow, Immich actually crashed again. This time I caught it in 10 minutes and fixed it immediately. Because n8n is watching 24/7.

Real Workflow #4 — Morning Briefing Data Prep

Remember the morning briefing from Episode 5? My AI assistant sends me weather, news, gold prices, and my schedule via Telegram every morning at 7 AM.

To create that briefing, the AI needs data. Calling weather APIs, fetching exchange rates, checking the calendar — n8n handles all this data collection automatically at 6:50 AM every morning. At 7 AM, the AI picks up the data, summarizes it, and shoots it to Telegram.

My morning routine: Wake up, open Telegram, check today’s weather and news. That’s it.

Before and After Automation

Saving time is great, but the real benefit is peace of mind. “Is the server okay?”, “Did that post get indexed?”, “Did I sync the logs?” — I don’t worry about any of this anymore. n8n is watching over everything.

n8n Self-Hosting Cost Breakdown

Let’s crunch the numbers.

n8n is lightweight and barely uses any server resources. Compared to Immich or Ollama, it’s practically invisible. Since the server is already running around the clock, the additional electricity cost is effectively zero.

Tips for Beginners

It’s all great, but let me be honest about a few things to watch out for.

• Name your workflows clearly. If you leave them as “My Workflow 1” and “New Workflow,” you won’t know what’s what once you have more than ten. Use specific names like “Prsm to Notion Sync” or “Server Health Check.”
• Always add error notification nodes. When an API is temporarily down or a service changes, your workflow will fail silently. Connect a Telegram notification node at the end to catch errors — you’ll sleep better at night.
• Block external access. n8n stores sensitive information like Notion tokens and GitHub tokens. Make sure to block external access with a firewall. I locked everything down with iptables back in Episode 1.

What’s Next

Now that the server runs itself with automation, it’s time to build features that are directly useful for real work.

In the next episode:

• Auto-transcribe phone calls — hang up and the text is ready
• AI-generated meeting notes — Google Meet and Zoom meetings summarized by AI
• Whisper — OpenAI’s speech recognition AI, running free on your own server
• How a single phone call becomes a work record in a manufacturing environment

A non-coder who built an AI assistant, now building an AI transcriber. Stay tuned.

This post was written by AI (Claude Code) and reviewed by a code-illiterate human.

The post Even a Code-Illiterate Built It! Home Server Journey (7) — Making the Server Work on Its Own with n8n appeared first on Prsm Studio.