Smart human takeover & auto pause AI-powered Facebook Messenger chatbot
🤖 Facebook Messenger Chatbot - Smart Human Takeover, Auto Pause & Context-Aware
Adaptable to n8n 1.113+ and 2.x
by Nguyen Thieu Toan (Jay Nguyen)
📖 Overview
An intelligent Facebook Messenger chatbot that automatically detects human agent intervention and pauses AI responses accordingly. Features smart pause management, full context preservation, and seamless handoff between AI and human support.
Perfect for:
- 💼 Customer support with AI + human escalation
- 🎯 Sales conversations requiring manual intervention
- 🛠️ Technical support needing human expertise
- 🤝 Any chatbot requiring human oversight capability
Requirements: n8n v1.113.0+, Facebook App with Messenger, Google Gemini API key (or compatible LLM)
🔗 Complementary Workflow
Smart Facebook Messenger Chatbot – Message Batching & History
Enhances Messenger automation with intelligent batching, conversation tracking, and context-aware responses.
Messages are grouped, stored, and processed with full history for smoother interactions.
Why combine?
- 🧩 Smart Batch (v3): Efficient multi-message handling, reduced spam
- 📜 Conversation History: Maintains context across sessions
- 🤖 AI Responses: Natural, context-aware replies
- ⚡ Scalability: Sequential processing for reliable delivery
👉 Access workflow Smart Facebook Messenger Chatbot – Message Batching & History
⚡ Key Features
Core Capabilities
| Feature | Description |
|---------|-------------|
| 🔍 Human Takeover Detection | Automatically detects when admin/human sends messages from page via metadata checking |
| ⏸️ Smart Auto-Pause | Bot pauses for configurable duration (default 60s) when human joins conversation |
| 📝 Context Preservation | Saves both AI and human responses in conversation history for seamless continuity |
| 📋 Whitelist Management | Tracks paused users with timestamp-based auto-resume (no manual intervention needed) |
| 🔄 Seamless Handoff | Smooth transition between AI and human, then automatic resume after timeout |
| 🏢 Multi-Page Support | Single workflow handles multiple Facebook Pages via page_id differentiation |
| 📊 Full History Context | AI sees both previous AI and human responses when resuming |
Technical Highlights
- ✅ Metadata-based detection (
message.metadata == "bot_rep") - ✅ Timestamp-based pause management (auto-expires)
- ✅ Upsert operation for whitelist (updates if exists, inserts if new)
- ✅ Composite key indexing (
user_id+page_id) - ✅ Zero manual cleanup required
- ✅ Full conversation context preserved across handoffs
🏗️ How It Works
┌──────────────────────────────────────────────────────────┐
│ 1. Message Intake │
│ • The system receives incoming messages from different │
│ sources and identifies their type. │
└──────────────────────────────────────────────────────────┘
↓
┌──────────────────────────────────────────────────────────┐
│ 2. Human Interaction Recognition │
│ • Detects when a human is involved and records the event │
│ • Adjusts automated handling accordingly. │
└──────────────────────────────────────────────────────────┘
↓
┌──────────────────────────────────────────────────────────┐
│ 3. Pause & Resume Control │
│ • Temporarily pauses automation when needed │
│ • Resumes once conditions are met. │
└──────────────────────────────────────────────────────────┘
↓
┌──────────────────────────────────────────────────────────┐
│ 4. Automated Response │
│ • Processes messages with context │
│ • Generates and delivers appropriate replies. │
└──────────────────────────────────────────────────────────┘
🛠️ Setup Guide
Step 1: Facebook App Setup
Step 2: Data Storage Preparation
Step 3: Workflow Configuration
Step 4: Testing
👤 About the Author
Nguyen Thieu Toan (Nguyễn Thiệu Toàn / Jay Nguyen)
AI Automation Specialist | n8n Workflow Expert | Business Optimization Consultant
Services: AI Automation Solutions, n8n Workflow Development, Custom Chatbot Implementation, Team Training Programs
Contact:
- 🌐 nguyenthieutoan.com
- 🐦 X (Twitter)
- 📺 YouTube
- 📧 me@nguyenthieutoan.com
GenStaff Company: genstaff.net | contact@genstaff.net
📄 License
After purchase, use in commercial/personal projects. No redistribution or resale. Keep author attribution when sharing.
Last Updated: December 18, 2025 | Version: 1.0 | n8n Compatibility: v1.123.0+ and v2.0.0+ | Facebook API: v23.0/v24.0
Ready to enable intelligent human-AI collaboration in your Facebook Messenger? Import this workflow and transform your chatbot today! 🚀
Smart Human Takeover - Auto-Pause AI-Powered Facebook Messenger Chatbot
This n8n workflow provides a robust system for managing an AI-powered Facebook Messenger chatbot, enabling seamless human intervention when needed and automatically pausing the AI to prevent conflicts. It's designed to ensure a smooth customer experience by allowing human agents to step in without the AI interfering.
What it does
This workflow automates the following steps:
- Listens for Incoming Messages: Triggers when a new message is received via a webhook, likely from a Facebook Messenger integration (though the specific integration isn't detailed in the JSON, the context suggests it).
- Initial Message Processing: Prepares the incoming message data for further processing.
- Determines AI Pause Status: Checks a data table (likely a database or spreadsheet) to see if the AI for the current conversation is currently paused.
- Conditional AI Engagement:
- If AI is NOT paused:
- The incoming message is processed by an AI Agent (likely a LangChain agent) using a Google Gemini Chat Model.
- The AI Agent then performs an HTTP request, presumably to send its response back to the user via Facebook Messenger or another platform.
- If AI IS paused:
- The workflow waits for a configurable duration (e.g., 5 minutes). This is a crucial step to give the human agent time to respond without the AI immediately reactivating.
- After the wait, the workflow again checks the AI pause status. This re-check ensures that if the human agent resolved the issue quickly and unpaused the AI, the AI can resume.
- If the AI is still paused after the wait, the workflow simply responds to the initial webhook, effectively ending the AI's processing for that message without sending an AI-generated response.
- If AI is NOT paused:
- Human Takeover Mechanism: The "If" node and "Data table" imply a mechanism where a human agent can toggle the AI's active status (pause/unpause) within the data table, allowing them to take over the conversation.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Webhook Integration: An external service (e.g., Facebook Messenger, a custom chatbot platform) configured to send incoming messages to the n8n Webhook URL.
- Google Gemini API Key: Credentials for the Google Gemini Chat Model to enable AI responses.
- Data Table/Database: A data table (e.g., a Google Sheet, Airtable, or a database accessible via HTTP requests) to store and manage the AI pause status for conversations. The "Data table" node is used, implying a structured data source.
- HTTP Request Endpoint: An API endpoint to send responses back to the user (e.g., Facebook Messenger Send API).
Setup/Usage
- Import the Workflow: Download the JSON provided and import it into your n8n instance.
- Configure the Webhook Trigger:
- Locate the "Webhook" node.
- Set the "Webhook URL" to receive incoming messages from your chatbot platform (e.g., Facebook Messenger).
- Configure the Data Table:
- Locate the "Data table" node.
- Configure it to connect to your chosen data source (e.g., Google Sheets, a custom API) where you will store the AI pause status for each conversation/user. Ensure it can read and write a boolean or similar value indicating if the AI is paused.
- The "Edit Fields" (Set) node before the "Data table" is likely used to format the data being written to or read from this table.
- Configure the Google Gemini Chat Model:
- Locate the "Google Gemini Chat Model" node.
- Provide your Google Gemini API credentials.
- Configure the AI Agent:
- Locate the "AI Agent" node.
- Define the agent's instructions and capabilities based on your chatbot's purpose.
- Configure the HTTP Request Node:
- Locate the "HTTP Request" node (ID 19).
- Set the URL and payload to send the AI-generated response back to your chatbot platform.
- Activate the Workflow: Save and activate the workflow in n8n.
This setup allows the AI to handle routine queries, while providing a clear mechanism for human agents to take over, pause the AI, and then resume AI operations when their intervention is complete.
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.
By Ranjan DailataGenerate 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
By Daniel NkenchoAutomate 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.
By Le Nguyen