Sync nightly TeamRetro health check scores with Postgres and Slack alerts
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 13 nodes and runs on a schedule (every day at 02:00). Along the way it connects Postgres, Slack and Teamretro (community).
How it runs
Trigger: On a schedule (every day at 02:00).
- Ensure Table Exists (Postgres): run a query
- Get Teams (Team Retro): get many (team)
- Latest Health Check (Team Retro): get many (health check)
- Has a Closed Check? (If): checks a condition and branches into true / false
- Get Dimensions (Team Retro): get all dimensions (health check)
- Collect Outcomes (Merge): merges the data from its input branches
- Normalise Rows (Code): runs custom JavaScript code
- Run Summary (Code): runs custom JavaScript code
- Valid Row? (If): checks a condition and branches into true / false
- Any Errors? (If): checks a condition and branches into true / false
…plus 2 more steps. See the full node list below.
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 Get Teams, Latest Health Check, Get Dimensions).
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Postgres
n8n-nodes-base.postgres - Team Retro
n8n-nodes-teamretro.teamRetro - If
n8n-nodes-base.if - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow runs nightly to fetch each team’s latest closed TeamRetro health checks, normalizes one row per health dimension, and upserts the scores into a Postgres table, sending a Slack alert only when errors occur. How it works 1. Runs…