ZapierBeginner6 min readUpdated Jun 9, 2026

Zapier: Slack Standup Channel → Weekly Digest

Aggregate a week of Slack standup posts into a per-person summary and a team-level rollup, delivered every Friday.

zapierslackopenaiteam

Download this template

Grab a structured copy of "Zapier: Slack Standup Channel → Weekly Digest" as JSON (for programmatic import) or Markdown (for docs and README files). Both are licensed CC-BY-4.0 with attribution.

Overview

Async standups accumulate hundreds of messages a week. Nobody reads them all. This Zap pulls the week's standup posts by author, generates a per-person weekly summary (what they shipped, what they're blocked on, what's next), and produces a team-level rollup pinned in the channel every Friday.

How it works

  1. Schedule trigger: Fridays at 3pm local time.
  2. Slack: get messages from #standup for the last 7 days.
  3. Group by user; send each user's messages to GPT-4o-mini for a per-person summary.
  4. Concatenate + one more call for the team rollup.
  5. Post both back to Slack; pin the team rollup.

Benefits

  • Managers get one weekly artifact instead of scrolling.
  • Blocked items become visible earlier.
  • New teammates skim history in 5 minutes.

Use cases

  • Remote engineering teams.
  • Cross-functional squads with weekly rituals.
  • Founders needing lightweight visibility across 3-5 teams.

Step-by-step guide

Step 1: Set up the channel

One #standup channel. Enforce a simple template: Shipped / Doing / Blocked.

Step 2: Pull the week's messages

Zapier's Slack action for channel messages, filter to standups (top-level, not replies).

Step 3: Per-person summary prompt

GPT-4o-mini: 'Summarise this person's week in 3 bullets: shipped, doing, blocked. Preserve their voice.'

Step 4: Team rollup

'Given these per-person summaries, write a 5-bullet team rollup emphasising shared blockers.'

Step 5: Post + pin

Post per-person summaries as a thread, team rollup as top-level, pin it.

Example

Team rollup: '• Shipped: MCP eval harness (Sam), Stripe migration phase 2 (Priya). • Blocked: three engineers waiting on infra permissions — infra team, please check DMs.'

FAQs

Related resources

Workflows, articles, and tools that pair with this build.