Log TeamRetro standups to Google Sheets and send weekly Slack reports
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs on Team Retro events (standup.completed) (plus 1 other trigger). Along the way it connects Google Sheets, Slack and Teamretro (community).
How it runs
Trigger: On Team Retro events (standup.completed) (plus 1 other trigger).
- Skip Repeat Deliveries (Remove Duplicates): removes duplicate items
- Report Settings (Edit Fields (Set)): sets 2 fields: days, slackChannel
- Settings (Edit Fields (Set)): sets 2 fields: includeCarriedOver, blockerTopic
- Read the Log (Google Sheets): uses Google Sheets
- One Row per Update (Code): runs custom JavaScript code
- Build the Weekly Report (Code): runs custom JavaScript code
- Upsert into the Log (Google Sheets): append or update
- Post the Report (Slack): uses Slack
- Append to the Weekly Sheet (Google Sheets): append
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-teamretro is verified or supports 3.0 (used in When Standup Closes).
Nodes used (7)
- Team Retro Trigger
n8n-nodes-teamretro.teamRetroTrigger - Remove Duplicates
n8n-nodes-base.removeDuplicates - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Google Sheets
n8n-nodes-base.googleSheets - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow logs completed TeamRetro standup updates into Google Sheets and, every Monday, summarizes the past week’s participation and blockers per team, posting the report to Slack and appending weekly metrics to a separate Google Sheets…