Automated Note Publishing Workflow

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#

StepToolRole
1GranolaGenerates meeting summaries from transcripts
2TelegramReceives notes with a processing instruction
3OpenClawWatches the channel, creates dated markdown files
4GitHubStores the generated files in a repository
5Azure Static WebsiteAuto-deploys on every repository push

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:

  • Manual copy/paste from Granola into Telegram
  • No AI content enhancement — notes published as-is
  • No automated formatting or improvement
  • Validate the full chain before adding complexity

Future Iterations#

  • Eliminate the manual Granola → Telegram copy step
  • Add AI-powered content cleanup and formatting
  • Improve automated entry structure (headings, tags, metadata)
  • Streamline or replace the Telegram trigger with a direct integration