TeamRetro: Weekly overdue actions digest. Uses n8n-nodes-teamretro, slack. Scheduled trigger; 5 nodes.
TeamRetro: On Webhook → Create Action. Uses n8n-nodes-teamretro. Webhook trigger; 4 nodes.
TeamRetro: AI agent retro assistant. Uses chatTrigger, agent, n8n-nodes-teamretro. Chat trigger; 5 nodes.
TeamRetro: Retro completed → Slack digest. Uses n8n-nodes-teamretro, slack. Event-driven trigger; 4 nodes.
TeamRetro: High-priority action → Slack alert. Uses n8n-nodes-teamretro, slack. Event-driven trigger; 4 nodes.
TeamRetro: Auto-create the sprint retrospective. Uses n8n-nodes-teamretro, slack. Scheduled trigger; 4 nodes.
TeamRetro: Health check completed → email summary. Uses n8n-nodes-teamretro, emailSend. Event-driven trigger; 4 nodes.
TeamRetro: Onboard a user onto a team (account key). Uses formTrigger, n8n-nodes-teamretro. Event-driven trigger; 4 nodes.
TeamRetro: Kudos → Slack shout-out. Uses n8n-nodes-teamretro, slack. Event-driven trigger; 3 nodes.
9 of 9 workflows in this view · Browse all →
FAQ
How many n8n N8N Nodes Teamretro workflows are in the catalog?
9 n8n workflows in AutomationFlows currently use the N8N Nodes Teamretro integration — triggers, actions, or both.
How do I connect N8N Nodes Teamretro in n8n?
After importing the workflow JSON, n8n will prompt for N8N Nodes Teamretro credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.
Can I combine these with other integrations?
Yes — most N8N Nodes Teamretro workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.