🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home n8n Workflow
January 22, 2026

WhatsApp to Google Sheets, recruitment tracked clean

Lisa Granqvist Partner Workflow Automation Expert

Your recruitment WhatsApp gets messy fast. One person asks pricing, another sends a blurry passport photo, someone else wants “status update” with zero context, and now you’re scrolling for 10 minutes just to answer a simple question.

This is what recruitment coordinators complain about in private. agency owners feel it when staff miss messages. And ops managers see the same pattern in the numbers. This WhatsApp recruitment intake automation turns those chats into structured records, so you can respond faster and keep every request traceable.

You’ll set up a WhatsApp menu that routes people to the right path, logs everything to Google Sheets (including media), and escalates to a human when it should. Clean in, clean out.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: WhatsApp to Google Sheets, recruitment tracked clean

Why This Matters: WhatsApp Recruitment Requests Get Lost

Recruitment chats look “fine” until you try to scale them. A client sends a new request, then follows up with documents, then asks for tracking updates a week later. Meanwhile your team is answering pricing questions for the tenth time today, and complaints land in the same inbox as everything else. The result is predictable: missed messages, slow replies, inconsistent information, and no reliable log of what was promised. Honestly, it’s not just time you lose. It’s trust, and that’s harder to win back.

The friction compounds. Here’s where it breaks down in real operations:

  • Manual copy-pasting from WhatsApp into a spreadsheet takes forever, especially when people send voice notes or photos.
  • Status tracking turns into detective work because the request details, documents, and “latest update” live in different chat threads.
  • Common questions (pricing, required documents, transfer links) interrupt the team all day, which slows down the high-value conversations.
  • Complaints and “I need a human” requests are easy to miss, so the worst conversations get the slowest responses.

What You’ll Build: A WhatsApp Menu That Logs and Routes Everything

This workflow turns your official WhatsApp number into a structured intake and support channel for recruitment. A customer messages you, and they immediately get an interactive menu with eight clear options (pricing, new request submission, tracking, documents, complaints, human agent, and more). Based on what they choose, the workflow either answers with the right info, collects details step-by-step, or looks up an existing application in Google Sheets. It also keeps session state (so the conversation doesn’t “forget” what happened two messages ago), supports media uploads like PDFs and images, and logs the whole interaction for accountability. If the customer asks for a person or the workflow detects uncertainty, it pauses automation for that user and notifies staff internally.

The workflow starts with a WhatsApp webhook from your WhatsApp API provider. Google Sheets and Data Tables handle storage and lookup, while an AI Agent (OpenAI Chat Model + memory) can help with classification or “I don’t understand” moments. Finally, Telegram notifications alert your team when a human should step in, so nothing urgent sits in the queue.

What You’re Building

Expected Results

Say your WhatsApp number gets 20 inbound messages a day. If even half of those require you to copy details into Google Sheets and ask two follow-up questions, that’s maybe 6 minutes per conversation, or about 1 hour daily. Add “status update” lookups and hunting for attachments, and it’s easy to lose another hour. With this workflow, most people self-select from the 8-option menu, requests log automatically, and lookups are instant. You typically spend your time only on exceptions and real human conversations.

Before You Start

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • WhatsApp Business API for receiving and sending WhatsApp messages.
  • Google Sheets to store requests, logs, and status tracking.
  • OpenAI API key (get it from your OpenAI dashboard) for AI routing and uncertainty handling.

Skill level: Intermediate. You’ll connect accounts, edit sheet IDs, and test a few message paths end-to-end.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A WhatsApp message triggers the workflow. Your WhatsApp API provider calls an n8n webhook when a customer sends a message, taps a menu item, or uploads a file.

Session state is loaded (or created) for that contact. Using Data Tables and memory, the workflow figures out if this is a brand-new conversation, a follow-up inside an active flow, or someone returning after a pause.

Routing happens based on the menu choice. Switch/If logic sends the user into the right branch: pricing by nationality, new request intake, application tracking via Google Sheets lookup, complaints, or “human agent.” If the message is unclear, an AI Agent can classify it and choose the best route.

Results are logged and staff are alerted when needed. Every interaction is written to Google Sheets with timestamps and context, and escalation pings a staff member in Telegram while pausing the bot for that user.

You can easily modify the 8 menu options to match your services, and route escalations to different departments based on category. See the full implementation guide below for customization options.

Troubleshooting Tips

  • WhatsApp Business API credentials can expire or require approved webhooks. If messages stop triggering, check your WhatsApp provider dashboard logs and webhook status first.
  • If you’re using Wait nodes or external file handling, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • OpenAI prompts in AI nodes start generic. Add your brand voice and examples early, or you will spend your week rewriting “robot replies.”

Quick Answers

What’s the setup time for this WhatsApp recruitment intake automation?

About 1–2 hours if your WhatsApp API and Google Sheet are ready.

Is coding required for this recruitment intake automation?

No. You’ll mainly connect accounts and edit the menu text, sheet IDs, and a few routing rules.

Is n8n free to use for this WhatsApp recruitment intake workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API usage (often a few cents a day for light routing) and any WhatsApp API provider fees.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I modify this WhatsApp recruitment intake workflow for different use cases?

Yes, and you probably should. You can swap Google Sheets for Airtable, HubSpot, or a database by replacing the Sheets “append row” and “lookup” steps with your preferred storage nodes. Most teams also customize the 8-option WhatsApp interactive list to match their services, adjust the nationality pricing mapping, and change where escalation goes (Telegram to email, Slack, or a helpdesk). If you handle multiple countries, add a country selector early so the rest of the flow stays clean.

Why is my WhatsApp Business API connection failing in this workflow?

Usually it’s expired tokens or a webhook misconfiguration on your WhatsApp API provider. Recheck the callback URL, verify the right events are enabled, and confirm your number is still approved for sending. If failures happen only on busy days, you may be hitting provider rate limits or message template restrictions. Also make sure your n8n instance is publicly reachable over HTTPS.

What volume can this WhatsApp recruitment intake workflow process?

A lot. On n8n Cloud, the limit is tied to your plan’s monthly executions, and self-hosting depends on your server. In practice, teams comfortably handle dozens to hundreds of WhatsApp conversations per day because most messages are lightweight routing plus a sheet write.

Is this WhatsApp recruitment intake automation better than using Zapier or Make?

Often, yes. This workflow needs branching logic, session memory, cooldown controls, and a clean escalation path, and those get awkward (and expensive) in tools that charge per step and per path. n8n is also easier to self-host, which matters when message volume grows and you don’t want every reply to feel “metered.” Another difference is control: you can add a global bot shutdown switch and per-user overrides without hacks. Zapier or Make can still be fine for a simple “WhatsApp message → add row to sheet” flow, but this is closer to a real intake system. If you want a quick recommendation based on your volume and tools, Talk to an automation expert.

Once this is running, your WhatsApp becomes a proper intake channel instead of a chaotic inbox. The workflow handles the repetitive sorting and logging so your team can focus on closing placements.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Launch login modal Launch register modal