AI-powered candidate nurturing with scheduled WhatsApp & Gmail follow-ups
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 18 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects MCP Client, OpenAI and Gmail.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Separating information (Code): runs custom JavaScript code
- Extract age (Date & Time): formats or calculates dates
- AI Recruitment Assistant (OpenAI): uses OpenAI, with 1 tool (MCP Recrutei)
- Getting the AI content (Edit Fields (Set)): sets 1 field: content
- Separating messages per days (Code): runs custom JavaScript code
- Message WhatsApp day (HTTP Request): calls an HTTP API (POST)
- Message Gmail day (Gmail): uses Gmail
- Merge: merges the data from its input branches
- Wait: waits 2 seconds
- Message WhatsApp day (HTTP Request): calls an HTTP API (POST)
…plus 5 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)
- Webhook
n8n-nodes-base.webhook - Date & Time
n8n-nodes-base.dateTime - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Wait
n8n-nodes-base.wait - No Operation, do nothing
n8n-nodes-base.noOp - MCP Client Tool
@n8n/n8n-nodes-langchain.mcpClientTool - OpenAI
@n8n/n8n-nodes-langchain.openAi - HTTP Request
n8n-nodes-base.httpRequest - Gmail
n8n-nodes-base.gmail - Merge
n8n-nodes-base.merge
From the author
What This Workflow Does This workflow automates the candidate nurturing process, solving the common problem of candidates losing interest or "ghosting" after an application. It keeps them engaged and informed by sending a personalized, multi-channel (WhatsApp…