Predict employee attrition risk with Google Sheets, OpenAI, Gmail, and Telegram
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 28 nodes and runs on a schedule (cron 0 8 * * 1) (plus 1 other trigger). Along the way it connects Slack, Google Sheets, OpenAI and Gmail and 1 more.
How it runs
Trigger: On a schedule (cron 0 8 * * 1) (plus 1 other trigger).
- Get Performance Review Data (Google Sheets): uses Google Sheets
- Get 1:1 Meeting Notes (Google Sheets): uses Google Sheets
- Get Attendance Data (Google Sheets): uses Google Sheets
- Get Engagement Survey Data (Google Sheets): uses Google Sheets
- Get Employee Master Data (Google Sheets): uses Google Sheets
- Slack: uses Slack
- Merge: merges the data from its input branches
- Merge Employee Data Sources (Code): runs custom JavaScript code
- Compute Rule-Based Risk Signals (Code): runs custom JavaScript code
- Loop Through Employees (Loop Over Items (Split in Batches)): loops over the items in batches
…plus 16 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (11)
- Error Trigger
n8n-nodes-base.errorTrigger - Slack
n8n-nodes-base.slack - Code
n8n-nodes-base.code - Google Sheets
n8n-nodes-base.googleSheets - Merge
n8n-nodes-base.merge - OpenAI
@n8n/n8n-nodes-langchain.openAi - Gmail
n8n-nodes-base.gmail - Telegram
n8n-nodes-base.telegram - If
n8n-nodes-base.if - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Quick overview This workflow runs weekly to pull HR datasets from Google Sheets, calculate rule-based attrition risk signals, and enrich them with an OpenAI (GPT-4o-mini) risk assessment. It logs results back to Google Sheets, sends high-risk alerts via…