Overview#

An end-to-end pipeline that takes meeting notes from Granola and publishes them as dated markdown entries to a static website — with minimal manual effort.

Integration chain: Granola → Telegram → OpenClaw → GitHub → Azure

How It Works#

Technical Implementation#

OpenClaw#

• Monitors a specific Telegram channel
• Triggers on the instruction phrase: "go ahead and create an entry"
• Generates markdown files with date stamps
• Pushes directly to the connected GitHub repository

GitHub + Azure#

• Repository is linked to an Azure Static Website deployment
• Every push triggers an automatic redeploy
• No manual publishing step required

Version 1 Scope#

This first iteration keeps things simple and focused on getting the pipeline working end-to-end:

A cautionary tale, a second chance, and a 13-year-old iMac that found its purpose.

I didn’t do much research. A friend said it was good, built by a single developer, and worth trying. So I downloaded OpenClaw, clicked through a security warning that I probably should have taken more seriously, and installed it directly on my main Mac.

My first question was simple: “What can you do?”

It told me it could manage email, calendars, and system settings. Impressive. So I pushed a little further — “Can you update Docker?”

My OpenClaw Journey: From Friction to Flow#

When I started using OpenClaw seriously, I wanted one thing: an assistant that could actually do work with me, not just talk about it.

Real Problems, Real Fixes#

One of my most practical wins was fixing Wi‑Fi on an older 2013 Intel Mac running Linux. I hit a nasty Broadcom + DKMS dependency conflict, tracked it down to a repo/version mismatch, and got Wi‑Fi working again by pinning the right kernel (6.8.0-111-generic) and locking the driver/toolchain to prevent future breakage.