Back to Catalog

Telegram bot for item multi select and saving to Postgres (Module "Checkbox")

AndrewAndrew
650 views
2/3/2026
Official Page

Who is this for?

This template is for developers and automation specialists looking to create a Telegram bot that enables users to select items from a predefined list and save their choices to a Postgres database.

What problem is this workflow solving?

It provides a simple and efficient way to collect structured user input via Telegram and store it in a Postgres database, useful for inventory selection, order systems, or preference tracking.

What this workflow does

  • Displays a list of selectable options from a Postgres shop_list table in Telegram
  • Saves the user’s selection back to the database
  • Automatically deletes messages at each step to keep the chat clean

Setup

1. Create the required tables in Postgres

  • Replace "n8n" in the provided SQL script with the appropriate schema name for your database
  • Run the script to create the shop_list table

2. Add necessary credentials in n8n

  • Telegram: Connect your Telegram bot using the Bot Token
  • Postgres: Add your Postgres DB credentials to allow the workflow to read/write data

How to customize this workflow to your needs

  • Modify the shop_list table to include your specific options.
  • Adjust the Telegram messages and logic to match your use case.

Telegram Bot for Item Multi-Select and Saving to Postgres

This n8n workflow provides a Telegram bot that allows users to select multiple items from a predefined list and then saves these selections to a PostgreSQL database. It's ideal for scenarios requiring user input for multiple choices, such as task assignments, preference settings, or inventory management, all managed through a conversational interface.

What it does

  1. Listens for Telegram Messages: The workflow is triggered by incoming messages to a configured Telegram bot.
  2. Initial Command Handling: It checks if the incoming message is a /start command.
    • If /start, it sends a welcome message and presents a list of items as inline keyboard buttons for multi-selection.
    • If not /start, it proceeds to process potential item selections.
  3. Processes Item Selections:
    • It identifies if the incoming message is a callback query (i.e., a user clicking an inline button).
    • It extracts the selected item and the user's current selections from the callback data.
    • It toggles the selection status of the clicked item (add if not selected, remove if already selected).
    • It reconstructs the inline keyboard with updated checkboxes reflecting the current selections.
    • It updates the Telegram message to reflect the new selection status.
  4. Handles "Save" Action:
    • If the user clicks the "Save" button, it extracts the final list of selected items.
    • It formats the selected items into a JSON string.
    • It inserts the user's chat ID and the JSON string of selected items into a PostgreSQL database table.
    • It sends a confirmation message to the user via Telegram.
  5. Handles "Cancel" Action:
    • If the user clicks the "Cancel" button, it clears the current selections and sends a cancellation message.

Prerequisites/Requirements

  • Telegram Bot: A Telegram bot token obtained from BotFather.
  • PostgreSQL Database: Access to a PostgreSQL database with a table configured to store the chat ID and selected items (e.g., a TEXT or JSONB column for items).
  • n8n Instance: A running n8n instance to host the workflow.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Telegram Trigger:
    • Edit the "Telegram Trigger" node.
    • Select or create a new Telegram API credential. You will need your Telegram Bot Token.
    • Ensure the "Update Type" is set to "Message" and "Callback Query" to capture both text messages and button clicks.
  3. Configure Telegram Node:
    • Edit all "Telegram" nodes in the workflow.
    • Select the same Telegram API credential used in the trigger.
  4. Configure PostgreSQL Node:
    • Edit the "Postgres" node.
    • Select or create a new PostgreSQL credential, providing your database host, port, database name, user, and password.
    • Update the "Table Name" and "Columns" in the "Postgres" node to match your database schema. The workflow expects to insert chat_id and selected_items (as a JSON string).
  5. Define Items:
    • The list of selectable items is currently hardcoded within the "Code" node (specifically in the part that generates the inline keyboard). You will need to modify this node to define your desired items.
  6. Activate the Workflow: Save and activate the workflow.

Once configured, send a /start command to your Telegram bot to begin interacting with it.

Related Templates

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

AI-powered code review with linting, red-marked corrections in Google Sheets & Slack

Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.

higashiyama By higashiyama
90