HumationHuman + Automation
Back to Catalog

WhatsApp fact-checking bot with Perplexity AI and Twilio

Harsh ManiyaHarsh Maniya
725 views
2/3/2026
WebhookJotFormAutomationSalesforceCRM
Official Page

✅💬Build Your Own WhatsApp Fact-Checking Bot with AI

Tired of misinformation spreading on WhatsApp? 🤨 This workflow transforms your n8n instance into a powerful, automated fact-checking bot! Send any news, claim, or question to a designated WhatsApp number, and this bot will use AI to research it, provide a verdict, and send back a summary with direct source links.

Fight fake news with the power of automation and AI! 🚀

How it works ⚙️

This workflow uses a simple but powerful three-step process:

  1. 📬 WhatsApp Gateway (Webhook node): This is the front door. The workflow starts when the Webhook node receives an incoming message from a user via a Twilio WhatsApp number.
  2. 🕵️ The Digital Detective (Perplexity node): The user's message is sent to the Perplexity node. Here, a powerful AI model, instructed by a custom system prompt, analyzes the claim, scours the web for reliable information, and generates a verdict (e.g., ✅ Likely True, ❌ Likely False).
  3. 📲 WhatsApp Reply (Twilio node): The final, formatted response, complete with the verdict, a simple summary, and source citations, is sent back to the original user via the Twilio node.

Setup Guide 🛠️

Follow these steps carefully to get your fact-checking bot up and running.

Prerequisites

1. Configure Credentials

You'll need to add API keys for both Perplexity and Twilio to your n8n instance.

  • Perplexity AI:
    1. Go to your Perplexity AI API Settings.
    2. Generate and copy your API Key.
    3. In n8n, go to Credentials & New, search for "Perplexity," and add your key.
  • Twilio:
    1. Go to your Twilio Console Dashboard.
    2. Find and copy your Account SID and Auth Token.
    3. In n8n, go to Credentials & New, search for "Twilio," and add your credentials.

2. Set Up the Webhook and Tunnel

To allow Twilio's cloud service to communicate with your n8n instance, you need a public URL. The n8n tunnel is perfect for this.

  1. Start the n8n Tunnel: If you are running n8n locally, you'll need to expose it to the web. Open your terminal and run: 
    n8n start --tunnel
  2. Copy Your Webhook URL:
    • Once the tunnel is active, open your n8n workflow.
    • In the Receive Whatsapp Messages (Webhook) node, you will see two URLs: Test and Production.
    • Copy the Test/Production URL. This is the public URL that Twilio will use.

3. Configure Your Twilio WhatsApp Sandbox

  1. Go to the Twilio Console and navigate to Messaging & Try it out & Send a WhatsApp message.
  2. Select the Sandbox Settings tab.
  3. In the section "WHEN A MESSAGE COMES IN," paste your n8n Production Webhook URL.
  4. Make sure the method is set to HTTP POST.
  5. Click Save.

How to Use Your Bot 🚀

  1. Activate the Sandbox: To start, you (and any other users) must send a WhatsApp message with the join code (e.g., join given-word) to your Twilio Sandbox number. Twilio provides this phrase on the same Sandbox page.
  2. Fact-Check Away! Once joined, simply send any claim or question to the Twilio number. For example: Did Elon Musk discover a new planet?
  3. Within moments, the workflow will trigger, and you'll receive a formatted reply with the verdict and sources right in your chat!

Further Reading & Resources 🔗

WhatsApp Fact-Checking Bot with Perplexity AI and Twilio

This n8n workflow creates a WhatsApp fact-checking bot that leverages Perplexity AI to answer user queries and responds via Twilio. It provides a simple yet powerful way to get quick, AI-powered information directly within WhatsApp.

What it does

This workflow automates the following steps:

  1. Receives WhatsApp Messages: It acts as an endpoint to receive incoming WhatsApp messages sent to your Twilio number.
  2. Processes User Queries with Perplexity AI: It takes the incoming message text and sends it to Perplexity AI to generate a factual response.
  3. Sends AI-Generated Response via WhatsApp: It takes the response from Perplexity AI and sends it back to the user as a WhatsApp message using Twilio.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Account: An active n8n instance (cloud or self-hosted).
  • Twilio Account: A Twilio account with a WhatsApp-enabled phone number. You will need your Twilio Account SID and Auth Token.
  • Perplexity AI API Key: An API key for Perplexity AI to access its language model capabilities.

Setup/Usage

  1. Import the Workflow:

    • Download the provided JSON file for this workflow.
    • In your n8n instance, click on "Workflows" in the left sidebar.
    • Click "New" and then "Import from JSON".
    • Paste the JSON content or upload the file.

  2. Configure Credentials:

    • Twilio Node: Click on the "Twilio" node. You will need to create or select a Twilio credential. Provide your Twilio Account SID and Auth Token.
    • Perplexity Node: Click on the "Perplexity" node. You will need to create or select a Perplexity AI credential. Provide your Perplexity AI API Key.

  3. Configure the Webhook:

    • Click on the "Webhook" node.
    • Set the "HTTP Method" to POST.
    • Copy the "Webhook URL" generated by n8n.
    • In your Twilio account, navigate to your WhatsApp-enabled phone number's configuration.
    • Under the "Messaging" section, find "A MESSAGE COMES IN" and set its webhook URL to the one you copied from the n8n "Webhook" node. Ensure the method is set to HTTP POST.

  4. Activate the Workflow:

    • Once all credentials and the webhook are configured, click the "Activate" toggle in the top right corner of the n8n workflow editor to enable the workflow.

Now, when someone sends a message to your Twilio WhatsApp number, the workflow will trigger, process the message with Perplexity AI, and send the AI's response back to the user.

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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247