Back to Catalog

Create a Witty Telegram Bot with AI-Powered Humor, Roasts & Stats using OpenRouter

Sergey SkorobogatovSergey Skorobogatov
238 views
2/3/2026
Official Page

GiggleGPTBot β€” Witty Telegram Bot with AI & Postgres

πŸ“ Overview

GiggleGPTBot is a witty Telegram bot built with n8n, OpenRouter, and Postgres. It delivers short jokes, motivational one-liners, and playful roasts, responds to mentions, and posts scheduled witty content. The workflow also tracks user activity and provides lightweight statistics and leaderboards.


✨ Features

  • πŸ€– AI-powered humor engine β€” replies with jokes, motivation, random witty lines, or sarcastic roasts.
  • πŸ’¬ Command support β€” /joke, /inspire, /random, /roast, /help, /stats, /top.
  • 🎯 Mention detection β€” replies when users tag @GiggleGPTBot.
  • ⏰ Scheduled posts β€” morning jokes, daily motivation, and random wisdom at configured times.
  • πŸ“Š User analytics β€” counts messages, commands, reactions, and generates leaderboards.
  • πŸ—„οΈ Postgres persistence β€” robust schema with tables for messages, responses, stats, and schedules.

πŸ› οΈ How It Works

  1. Triggers

    • Telegram Trigger β€” receives all messages and commands from a chat.
    • Schedule Trigger β€” runs hourly to check for planned posts.
  2. Processing

    • Switch routes commands (/joke, /inspire, /random, /roast, /help, /stats, /top).
    • Chat history fetches the latest context.
    • Mention Analysis determines if the bot was mentioned.
    • Generating an information response builds replies for /help, /stats, /top.
    • AI nodes (AI response to command, AI response to mention, AI post generation) craft witty content via OpenRouter.
  3. Persistence

    • Init Database ensures tables exist (user_messages, bot_responses, bot_commands, message_reactions, scheduled_posts, user_stats).
    • Logging nodes update stats and store every bot/user interaction.
  4. Delivery

    • Replies are sent back via Telegram Send nodes (Send AI response, Send info reply, Reply to Mention, Submit scheduled post).

βš™οΈ Setup Instructions

  1. Create a Telegram Bot with @BotFather and get your API token.

  2. Add credentials in n8n:

    • Telegram API (your bot token)
    • OpenRouter (API key from openrouter.ai)
    • Postgres (use your DB, Supabase works well).
  3. Run the Init Database node once to create all required tables.

  4. (Optional) Seed schedule with the Adding a schedule node β€” it inserts:

    • Morning joke at 06:00
    • Daily motivation at 09:00
    • Random wisdom at 17:00 (Adjust chat_id to your group/channel ID.)
  5. Activate workflow and connect Telegram Webhook or Polling.


πŸ“Š Database Schema

  • user_messages β€” stores user chat messages.
  • bot_responses β€” saves bot replies.
  • bot_commands β€” logs command usage.
  • message_reactions β€” tracks reactions.
  • scheduled_posts β€” holds scheduled jokes/wisdom/motivation.
  • user_stats β€” aggregates per-user message/command counts and activity.

πŸ”‘ Example Commands

  • /joke β†’ witty one-liner with light irony.
  • /inspire β†’ short motivational phrase.
  • /random β†’ unexpected witty remark.
  • /roast β†’ sarcastic roast (no offensive targeting).
  • /stats β†’ shows your personal stats.
  • /top β†’ displays leaderboard.
  • /help β†’ lists available commands.
  • @GiggleGPTBot + message β†’ bot replies in context.

πŸš€ Customization Ideas

  • Add new command categories (/quote, /fact, /news).
  • Expand analytics with reaction counts or streaks.
  • Localize prompts into multiple languages.
  • Adjust CRON schedules for posts.

βœ… Requirements

  • Telegram Bot token
  • OpenRouter API key
  • Postgres database

πŸ“¦ Import this workflow, configure credentials, run the DB initializer β€” and your witty AI-powered Telegram companion is ready!

n8n AI-Powered Telegram Bot with OpenRouter

This n8n workflow creates a witty and engaging Telegram bot that leverages AI to generate humorous roasts and provide user statistics. It uses the OpenRouter platform for AI language models, allowing for flexible and powerful conversational capabilities.

The bot listens for messages in Telegram, processes them through an AI agent, and can respond with a roast or provide user chat statistics, all while storing interaction data in a PostgreSQL database.

What it does

  1. Listens for Telegram Messages: The workflow is triggered by incoming messages to a configured Telegram bot.
  2. Filters Bot Commands: It checks if the incoming message is a specific command (e.g., /roast or /stats).
  3. Handles /roast Command:
    • If the command is /roast, it extracts the target of the roast from the message.
    • It then uses an AI Agent (LangChain with OpenRouter) to generate a humorous roast based on the provided target.
    • The generated roast is sent back to the user in Telegram.
  4. Handles /stats Command:
    • If the command is /stats, it queries a PostgreSQL database to retrieve interaction statistics for the user.
    • The statistics are formatted and sent back to the user in Telegram.
  5. Stores User Interactions: All incoming messages are logged into a PostgreSQL database, allowing for tracking and analysis of bot usage.
  6. Scheduled Database Cleanup (Optional but Recommended): A separate branch of the workflow is triggered on a schedule (e.g., daily) to perform database cleanup or maintenance tasks. (Note: The provided JSON only shows the trigger, the actual cleanup logic would need to be added).

Prerequisites/Requirements

  • n8n Instance: A running n8n instance (self-hosted or cloud).
  • Telegram Bot: A Telegram bot token obtained from BotFather.
  • OpenRouter Account & API Key: An OpenRouter API key for accessing AI language models.
  • PostgreSQL Database: Access to a PostgreSQL database for storing user interaction data.
  • n8n LangChain Nodes: Ensure the @n8n/n8n-nodes-langchain package is installed in your n8n instance.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Telegram Trigger & Telegram Node: Create or select an existing Telegram API credential using your bot token.
    • OpenRouter Chat Model: Create or select an OpenRouter API credential using your OpenRouter API Key.
    • Postgres Node: Create or select a PostgreSQL credential with the necessary connection details (host, port, database, user, password).
  3. Database Schema:
    • Ensure your PostgreSQL database has a table to store Telegram messages. A simple schema might look like:
      CREATE TABLE telegram_messages (
          id SERIAL PRIMARY KEY,
          chat_id VARCHAR(255),
          user_id VARCHAR(255),
          username VARCHAR(255),
          message_text TEXT,
          timestamp TIMESTAMP DEFAULT CURRENT_TIMESTAMP
      );
      
    • Adjust the Postgres node's query to match your table and column names if different.
  4. Activate the Workflow:
    • After configuring all nodes and credentials, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
  5. Interact with the Bot:
    • Open Telegram and send messages to your bot.
    • Try commands like /roast <name> (e.g., /roast n8n) or /stats to see it in action.
  6. Customize AI Agent:
    • Adjust the AI Agent node's prompt and tools to refine the bot's personality and capabilities.
    • Experiment with different OpenRouter models to find the best balance of humor and performance.
  7. Scheduled Cleanup (Optional):
    • Configure the Schedule Trigger node (ID 839) to your desired interval for database maintenance.
    • Add the necessary Postgres nodes and logic after the Schedule Trigger to perform tasks like deleting old messages or generating reports.

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 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://&lt;your-instance&gt;.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.

Le NguyenBy Le Nguyen
942