Skip to product information

n8n TeamRetro to Google Sheets: Slack Weekly Reports

n8n TeamRetro to Google Sheets: Slack Weekly Reports

 (200+Reviews)
Regular price £15.99
Regular price £15.99 Sale price
SAVE Sold out
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
n8n TeamRetro to Google Sheets: Slack Weekly Reports

n8n TeamRetro to Google Sheets: Slack Weekly Reports

Regular price £15.99
Regular price £15.99 Sale price
SAVE Sold out

Turn TeamRetro standup notes into weekly Slack reports (and track trends in Google Sheets)

This n8n workflow captures completed TeamRetro standup updates, stores them in Google Sheets, and every Monday automatically summarizes the past week’s participation and blockers per team—posting the formatted report to Slack and appending weekly metrics to a separate sheet.

What this workflow does

  • Ingests standup data via TeamRetro webhook: Triggers on the “Standup Completed” event using the TeamRetro webhook trigger.
  • Prevents duplicate writes: Deduplicates incoming webhook deliveries using the TeamRetro delivery ID.
  • Transforms updates into sheet-ready rows: Converts each participant’s topic updates into one plain-text row per update (with an option to exclude carried-over items) and flags blocker-topic entries.
  • Upserts into Google Sheets: Writes to the Google Sheets “Log” sheet and matches on Update ID to avoid duplicate records.
  • Schedules weekly reporting: Runs every Monday at 9 AM, reads the logged standups from Google Sheets, and builds per-team summaries for the last N days.
  • Generates and distributes the report: Includes standups held, posting frequency, new blockers, and the longest-running blocker; then posts the report to a Slack channel.
  • Tracks weekly metrics over time: Appends the week’s metrics to the Google Sheets “Weekly” sheet.

Use cases

  • Daily team leads who want a single weekly Slack summary of TeamRetro standups and blockers.
  • SaaS operators tracking engineering participation and blocker trends across teams.
  • Automation engineers maintaining a reliable audit log of standup updates in Google Sheets.

Technical details

  • Triggers: TeamRetro webhook trigger (Standup Completed), plus a schedule trigger for Monday 9 AM.
  • Integrations / nodes: TeamRetro, Google Sheets, Slack.
  • Core logic: Deduplication on TeamRetro delivery ID, optional exclusion of carried-over items, upsert matching on Update ID, and blocker detection.
  • Expected sheets: “Log” and “Weekly” tabs with columns for fields such as Date, Team, Standup, Person, and Question.
View full details