Interactive recruitment customer service with WhatsApp, Google Sheets CRM & notifications
π Recruitment Office WhatsApp Automation
Automate WhatsApp communication for recruitment agencies with an interactive, structured customer experience. This workflow handles pricing inquiries, request submissions, tracking, complaints, and human escalation while maintaining full session tracking and media support.
Good to know
- Uses WhatsApp Interactive List Messages for user selection and navigation.
- Includes session-state logic and memory across messages.
- Includes a 5-minute cooldown to avoid spam and repeated triggers.
- Supports logging for all interaction types including media files.
- Includes both a global bot shutdown switch and per-user override.
How it works
- A customer sends a message to the official WhatsApp number.
- The workflow replies with an interactive menu containing 8 service options:
- π° Pricing by nationality (8 supported countries)
- π New recruitment request submission
- π Tracking existing applications via Google Sheets lookup
- π Worker transfer link distribution
- π Translation service information
- π Required documents and instructions
- β οΈ Complaint submission and routing
- π€ Request a human agent
- The workflow retrieves or stores data based on the selection using Google Sheets and Data Tables.
- If the customer requests human help or the logic detects uncertainty, the workflow:
- Pauses automation for that user
- Notifies a designated staff member
- All interactions are logged including files, text, timestamps, and selections.
Features
- π Structured WhatsApp service menu
- π CRM-style recruitment request logging
- β¨ Pricing logic with nationality mapping
- π Lookup-based status tracking
- π Support for media uploads (PDF, images, audio, documents)
- π§ Session tracking with persistent user state
- π€ Human escalation workflow with internal notifications
- π Anti-spam and cooldown control
- π Bot master switch (global + per-user)
Technology stack
| Component | Usage | |----------|-------| | n8n | Automation engine | | WhatsApp Business API | Messaging and interactive UX | | Google Sheets | CRM and logs | | Data Tables | State management | | JavaScript | Custom logic and routing |
Requirements
- WhatsApp Business API account with active credentials
- n8n Cloud or self-hosted instance
- Google Sheets for CRM storage
- Data Tables enabled for persistent session tracking
How to use
- The workflow uses a Webhook trigger compatible with common WhatsApp API providers.
- Modify menu content, pricing, optional steps, and escalation flows as needed.
- Link your Google Sheets and replace test sheet IDs with production values.
- Configure human escalation to notify team members or departments.
Customising this workflow
- Replace Google Sheets with Airtable, HubSpot, or SQL storage.
- Add expiration and reminder messages for missing documents.
- Add AI-powered response logic for common questions.
- Enable multi-country support (Saudi/UAE/Jordan/Qatar/Kuwait/etc.)
- Connect to dashboards for reporting and staff performance analytics.
n8n Interactive Recruitment and Customer Service Workflow
This n8n workflow provides a robust framework for managing interactive recruitment and customer service scenarios, likely integrated with WhatsApp (implied by the directory name, though not explicit in the JSON) and Google Sheets for CRM. It uses a webhook to initiate interactions, processes data, and sends emails, incorporating conditional logic and delays for a structured conversation flow.
What it does
This workflow is designed to handle interactive conversations, likely from a messaging platform, and manage them through a series of steps:
- Receives Incoming Interactions: It starts by listening for incoming data via a Webhook, which acts as the entry point for new interactions (e.g., a new message from a customer or applicant).
- Processes Incoming Data: A "Code" node is used to process the incoming webhook data. This could involve parsing messages, extracting key information, or preparing data for subsequent steps.
- Routes Based on Interaction Type: A "Switch" node then evaluates the processed data to determine the type of interaction. This allows the workflow to branch into different paths based on the content or context of the incoming message.
- Conditional Logic for Specific Scenarios: An "If" node introduces further conditional logic, enabling the workflow to handle specific scenarios or responses based on predefined criteria.
- Manages Customer/Applicant Data: It interacts with Google Sheets, likely to read or write customer/applicant information, acting as a simple CRM or record-keeping system.
- Sends Email Notifications: The workflow is capable of sending emails via Gmail, which can be used for notifications, follow-ups, or sending information to users.
- Introduces Delays: A "Wait" node allows for pauses in the workflow execution, which is crucial for simulating human-like response times in interactive conversations or for scheduling follow-up actions.
- Responds to the Initiating Webhook: Finally, a "Respond to Webhook" node sends a response back to the system that triggered the initial webhook, completing the interaction cycle.
- Stores Static Data: A "Data table" node is included, which can be used to store static configuration data or lookup tables within the workflow itself.
- Provides Internal Documentation: Sticky Notes are used throughout the workflow for internal documentation, explaining the purpose or logic of different sections.
Prerequisites/Requirements
To effectively use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Google Account: For Google Sheets and Gmail integration. You will need to set up Google OAuth2 credentials in n8n.
- Webhook Source: An external service or application configured to send data to the n8n Webhook URL. This could be a messaging platform (like WhatsApp via a connector), a form submission, or another API.
- Basic JavaScript Knowledge: For customizing the "Code" node if specific data parsing or manipulation is required.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Set up your Google Sheets credentials (OAuth2) to allow n8n to access your spreadsheets.
- Configure your Gmail credentials (OAuth2) to enable sending emails.
- Configure Webhook:
- Activate the "Webhook" trigger node. n8n will provide a unique URL.
- Configure your external application (e.g., WhatsApp connector, CRM) to send POST requests to this URL when an interaction occurs.
- Customize Nodes:
- Code Node: Adjust the JavaScript code to correctly parse and transform the data received from your webhook, as well as to prepare data for subsequent nodes.
- Switch Node: Define the conditions for routing based on your specific recruitment or customer service scenarios.
- If Node: Set up the conditional logic for specific actions or responses.
- Google Sheets Node: Specify the spreadsheet ID, sheet name, and the operations (e.g., append row, get all rows) you want to perform.
- Gmail Node: Customize the recipient, subject, and body of the emails to be sent.
- Wait Node: Adjust the delay duration as needed for your interaction flow.
- Data table Node: Populate this node with any static data or lookup information required by your workflow.
- Activate the Workflow: Once configured, activate the workflow in n8n. It will now be ready to process incoming interactions.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitorβs webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger β Manually start the workflow or schedule it to run periodically. Input Setup β Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) β Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring β Clean and convert GPT output into JSON format. Data Storage (Google Sheets) β Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the βSet Input Fieldsβ node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors β Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection β Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report β Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization β Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs β Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting Itβs a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chatβturn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. π What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing π§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation π Required Credentials OpenAI API Setup Go to platform.openai.com β API keys (sidebar) Click "Create new secret key" β Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β Dashboard β API Keys Generate a new API key β Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βοΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβchat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" π― Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration β οΈ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive β Download PDF β OCR text β AI normalize to JSON β Upsert Buyer (Account) β Create Opportunity β Map Products β Create OLI via Composite API β Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content β the parsed JSON (ensure itβs an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id β build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total β per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger β Download File From Google Download File From Google β Extract from File β Update File to One Drive Extract from File β Message a model Message a model β Create or update an account Create or update an account β Create an opportunity Create an opportunity β Build SOQL Build SOQL β Query PricebookEntries Query PricebookEntries β Code in JavaScript Code in JavaScript β Create Opportunity Line Items --- Quick setup checklist π Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. π IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) π§ AI Prompt: Use the strict system prompt; jsonOutput = true. π§Ύ Field mappings: Buyer tax id/name β Account upsert fields Invoice code/date/amount β Opportunity fields Product name must equal your Product2.ProductCode in SF. β Test: Drop a sample PDF β verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep βReturn only a JSON arrayβ as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields donβt support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your orgβs domain or use the Salesforce nodeβs Bulk Upsert for simplicity.