Bibliothek / Berichte, Analysen & Dashboards
Berichte, Analysen & Dashboards
TeamRetro-Standups in Google Sheets protokollieren und wöchentliche Slack-Berichte posten
Schreibt jedes abgeschlossene TeamRetro-Standup-Update als Zeile in Google Sheets (Upsert) und postet jeden Montag Teilnahme, neue Blocker und den am längsten bestehenden Blocker in Slack.
Was sie bewirkt
## TeamRetro: Log standups to Google Sheets and post a weekly participation report For scrum masters who want standup history they can search and trend. Every update from a closed TeamRetro standup is upserted into Google Sheets as its own row. Each Monday a second flow reads the log, posts who posted, new blockers and the longest-running blocker to Slack, and appends the week's numbers to a trends tab. ### How it works 1. Daily: the TeamRetro Trigger fires on Standup Completed. A delivery TeamRetro retries is skipped, so nothing happens twice. Each update becomes a plain-text row, upserted on Update ID so a row is never written twice. 2. Mondays at 9 AM: the schedule reads the log and keeps the days days before today. 3. A Code node counts standups held, who posted on how many, and new and long-running blockers, per team. 4. Slack gets the report, and the week's numbers are appended to the trends tab. ### Setup - [ ] Create a sheet "Log" with columns: Date, Team, Standup, Person, Question, Blocker, Update, Carried over, Update ID - [ ] Create a sheet "Weekly" with columns: Week ending, Team, Standups, People posting, Updates, New blockers, Longest blocker (standups) - [ ] Copy the Production URL from "When Standup Closes" into TeamRetro under Settings → Integrations → Webhooks, tick Standup Completed, and paste the signing secret back into the trigger - [ ] Connect Google Sheets and Slack, pick the document and sheets, and set slackChannel Both flows have pinned samples. Running the pinned sample a second time stops at "Skip Repeat Deliveries": that is the duplicate guard. ### Customization Set includeCarriedOver to false to log only new items.
Die Schritte
- When Standup Closes
- Skip Repeat Deliveries
- Settings
- One Row per Update
- Upsert into the Log
- Every Monday at 9 AM
- Report Settings
- Read the Log
- Build the Weekly Report
- Post the Report
- Append to the Weekly Sheet
Ähnliche Automatisierungen
Aufgaben & ProjektmanagementTeamRetro-Standup-Blocker mit OpenAI und Slack in Jira-Issues umwandeln18 SchritteKI-Agenten & AssistentenRetro-Konsole für Gmail, X und Nachrichten betreiben12 SchritteAufgaben & ProjektmanagementProjektteam in Notion erstellen23 SchritteBerichte, Analysen & DashboardsTeam-Tickets aus GraphQL nach Google Sheets exportieren11 Schritte