n8n TeamRetro Nightly Health Check Sync to Postgres + Slack Alerts

Nightly sync of TeamRetro health checks into Postgres—with Slack alerts only when something goes wrong

Keep your team health data up to date automatically. This n8n workflow runs every night, pulls each TeamRetro team’s latest closed health checks, normalizes the dimensions into a Postgres-friendly format, and sends a Slack notification only if failures are detected.

What this workflow does

• Schedules nightly: Runs daily at 02:00 (server time).
• Ensures storage is ready: Creates (if needed) the team_health_scores table in Postgres.
• Fetches teams and checks: Retrieves all teams from TeamRetro, then pulls up to three most recent health checks per team.
• Processes only closed checks: Skips teams without a closed health check and continues only checks with status closed.
• Flattens dimensions for analytics: Pulls all dimensions for each closed health check and flattens ratings into warehouse-ready rows (including the health model and rating scale).
• Filters invalid data: Drops unrated or failed dimension rows.
• Upserts scores safely: Upserts into Postgres using (health_check_id, dimension) as the conflict key.
• Run summary + error alerts: Aggregates outcomes into a single summary and posts error details to Slack only when failures occur.

Use cases

• Building a reliable historical dataset of TeamRetro health scores for dashboards and reporting.
• Keeping a SaaS operator’s analytics database fresh without manual exporting.
• Automated monitoring: detect and surface workflow processing issues via Slack.

Technical details

• TeamRetro credential: uses an account-scoped API key prefixed with tra_.
• Postgres: writes to team_health_scores and upserts using (health_check_id, dimension).
• Slack: posts failure notifications to a configured destination channel (e.g., #data-alerts).
• Nodes and logic used include: if, code, merge, slack, postgres, and sticky note.