Stow.AI Standup Automation: GitHub + Slack + Notion
AI AgentsApril 19, 20264 min read

AI Standup Automation: GitHub + Slack + Notion

Claude reads your GitHub activity from yesterday, drafts a standup update, logs it to Notion, and posts to your team Slack channel — with your approval before it posts.

Claude
Notion

A daily standup is three things: what you did yesterday, what you're doing today, and what's blocking you. Claude can answer the first one automatically from your GitHub activity. You fill in the second and third. The result posts to Slack with your approval and gets logged to Notion automatically.

The Workflow

GitHubClaude draftsNotion logsYou approve → Slack

Permission Configuration

GitHub

Read commits and PRs (yesterday's activity)Allowed
Read issues assigned to youAllowed
Everything elseOff

Notion

Create standup log entryAllowed
Read existing entries for contextAllowed
Delete pagesOff

Slack

Read #standup channel (for context)Allowed
Post to #standupApproval Required
Post to other channelsOff

The Standup Prompt

"Pull my GitHub activity from the last 24 hours — commits, PRs opened or reviewed, issues closed. Draft a standup update in this format: Yesterday: [what you did]. Today: [leave blank for me to fill in]. Blockers: [leave blank]. Log the draft to my Notion standup database, then ask for my edits before posting to #standup on Slack."

What Claude Reads From GitHub

Commits pushed

Summarized by repo and what changed

Pull requests opened

Title and which branch/repo

PRs reviewed

Which PRs you commented on or approved

Issues closed

What you resolved or marked done

Edge Cases Worth Knowing

No commits yesterday (weekend, PTO)

Claude will note no activity rather than hallucinating. You can add context manually before posting.

Activity across multiple repos

Claude groups by repo. Long lists get summarized — "3 commits to auth-service: session handling refactor".

Someone else already posted in #standup

Claude reads the channel before drafting so it knows the format your team uses.

Why the Slack Post Needs Approval

This is the one step where something goes to your team. The GitHub reads and Notion write are private — only you see the results. The Slack post is visible to everyone in #standup. Approval-required means you always read the draft before it becomes team-visible.

In practice, you'll approve it 95% of the time unchanged. The 5% is when Claude misread something ("3 commits to fix a typo" deserves a better description), and the approval gate is where you fix it.

Standup in 30 Seconds.

Yesterday's GitHub activity → drafted standup → logged to Notion → posted to Slack. One prompt.

S

Stow Security Team

April 19, 2026