by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by Ruslan Elishev
🤖 Telegram Bot with Dynamic Multi-Level Menu System What This Workflow Does Ever wanted to build a Telegram bot with professional-looking menus that actually work? This n8n workflow creates an interactive bot with dynamic inline keyboards, multi-level navigation, and smart button routing - all without writing complex code from scratch. The bot features a clean separation between your menu structure and business logic. This means you can change your menus anytime without breaking the underlying functionality. Think of it like WordPress menus but for Telegram bots - you define the navigation, and the workflow handles everything else. Your bot will respond with personalized messages, remember user context, handle button clicks smoothly (no annoying loading spinners!), and route different actions to specialized handlers. Whether users are rating your service, checking their subscription status, or navigating through settings, everything just works. 🚀 Getting Started in 3 Minutes Step 1: Get Your Bot Token Head over to Telegram and chat with @BotFather. Create a new bot (or use an existing one) and grab that token. In the workflow, find the purple "Set Bot Token" node and replace [!!! YOUR_BOT_TOKEN_HERE !!!] with your actual token. Step 2: Activate the Magic Save the workflow, click on "Production" tab, and you'll see a webhook URL. Toggle the workflow to Active. That's it - your bot is live! Step 3: See It In Action Message your bot on Telegram. Type /start and watch your beautiful menu appear. Click around, explore the buttons - everything is already set up and working. 🎨 Making It Yours Want to Add Your Own Menus? Open the workflow and look for the sticky note titled "📖 COMPLETE GUIDE: ADDING MENUS & ACTIONS". I've written step-by-step instructions right there in the workflow. You'll find exact examples showing how to add a contact menu, subscription status checker, or whatever you need. The beauty is in the simplicity - menus are just text and buttons. No complicated logic mixed in. Check the "📚 REAL EXAMPLES" sticky note for copy-paste templates you can modify. Need Custom Actions? When a button needs to actually DO something (save data, call an API, send an email), that's where handlers come in. The workflow includes 7 pre-built handlers for common tasks like ratings, language switching, and analytics. Want to add your own? The "💡 ADDING HANDLERS" sticky note walks you through it. 💡 Why This Workflow Is Different Most Telegram bot tutorials have you mixing menu code with business logic, making changes a nightmare. This workflow separates everything cleanly. Your menus live in one place, your logic in another. It's like having a control panel for your bot. The workflow also solves a common n8n limitation - the native Telegram node doesn't support dynamic inline keyboards. Instead of giving up, this workflow uses HTTP requests directly to the Telegram API, giving you full control over every feature. 🔧 Pro Tips from the Trenches After building dozens of Telegram bots, here's what I've learned: Always include a "Back" button - users panic without an escape route Use emojis in your buttons - they make everything friendlier Test each menu path after changes - one typo can break navigation Keep action handlers focused - one handler, one job Hit a snag? Check the "🐛 TROUBLESHOOTING & TIPS" sticky note in the workflow. I've documented all the common "gotchas" and their fixes. 📦 What's Included This workflow comes with everything you need: Centralized menu configuration system Smart routing that automatically detects which button was pressed 7 ready-to-use action handlers (modify or replace as needed) Parallel processing for lightning-fast responses Built-in error handling with fallback menus Comprehensive documentation right in the workflow via sticky notes 🚀 Taking It Further Once you're comfortable with the basics, this architecture scales beautifully. Connect a database to remember user preferences. Integrate with your CRM to pull customer data. Add payment processing for a shopping bot. The modular design means you can enhance one part without touching the others. The workflow sticky notes contain advanced examples for multi-language support, user authentication, and API integrations. Everything is explained in plain English with code examples you can actually use. 🤝 One Last Thing This workflow started as a simple dynamic menu with rating workflow and evolved into something much more powerful through community feedback. If you build something cool with it, I'd love to hear about it. And if you get stuck, remember - all the answers are in those sticky notes. I spent way too much time making them ridiculously detailed so you wouldn't have to struggle like I did. Happy bot building! 🎯 Version: 1.0 - Centralized Menu System with Branching Author: Ruslan Elishev
by KlickTipp
Community Node Disclaimer: This workflow uses KlickTipp community nodes. Introduction This workflow creates a complete two-way synchronization between KlickTipp and Google Calendar. When a contact in KlickTipp is tagged, an event is automatically created in Google Calendar. If event status changes or if attendees respond, their RSVP status and event status are reflected in KlickTipp — keeping your contact database, campaigns, and event insights always up to date. Perfect for marketers, coaches, or event organizers who want to automatically send event invites and instantly capture participation status without manual updates. How it works Google Calendar → KlickTipp: This template keeps your KlickTipp list in sync with Google Calendar across the full event lifecycle. For each attendee, the workflow optionally filters out internal domains, then writes event details into KlickTipp custom fields. It watches your calendar for: Event Created* → creates/updates each attendee as a KlickTipp contact and adds the *event created/updated tag. Event Cancelled* → tags attendees with *event canceled. Event Updated* → routes attendees by *responseStatus** and tags them: accepted → event confirmed declined → event declined tentative → event considered KlickTipp → Google Calendar: Watches for a tag like “Send an event invitation via Google Calendar”. Creates an event in Google Calendar using mapped KlickTipp fields. Setup Instructions KlickTipp Preparation Prepare custom fields Google Calendar | event summary, data type: "Single line" Google Calendar | event description, data type: "Single line" Google Calendar | event location, data type: "Single line" Google Calendar | event start datetime, data type: "Datetime" Google Calendar | event end datetime, data type: "Datetime" Prepare tags: Google Calendar | event created/updated Google Calendar | event canceled Google Calendar | event declined Google Calendar | event confirmed Google Calendar | event considered Send an event invitation via Google Calendar Prepare outbound: Activation tag: Send an event invitation via Google Calendar Activation URL: webhook URL from trigger Credential Configuration Connect your Google Calendar account using Client ID and Client Secret from the Google Cloud. Authenticate your KlickTipp connection with username/password credentials (API access required). Customization Recommended poll frequency: every 1–5 minutes for near real-time updates. Adjust to your local timezone if necessary. Each trigger works independently, allowing partial deployments if only certain event types are needed. Ensure End > Start in your data. If you prefer a fixed duration, compute End from Start + minutes in a Date & Time node. If you want a Meet link, enable “Add Google Meet video conferencing” in the Calendar node instead of pasting a Calendar URL into Location.
by amudhan
Companion workflow for IF node docs
by Harshil Agrawal
No description available
by Harshil Agrawal
No description available
by Rahul Joshi
Description: This ready-to-deploy n8n automation template smartly detects and classifies files uploaded to a specified Google Drive folder based on MIME type. It automatically moves each file into its correct destination folder: Documents, PDFs, or Images — ensuring a clean and organized Drive, effortlessly. Perfect for remote teams, admins, educators, legal pros, and automation-focused operations, this workflow eliminates manual sorting and saves hours of repetitive work. What This Template Does (Step-by-Step) ⚙️Manual Trigger: Launch the workflow on demand using the "Execute Workflow" trigger. 📁 Search Files in Source Folder (Google Drive): Lists all files inside your chosen folder (e.g., "Uploads"). 🔁 Loop Over Files (SplitInBatches): Iterates through each file one-by-one to ensure reliability. 📥 Download File (Google Drive): Retrieves file metadata and MIME type required for filtering. 🧠 Smart File Type Detection via If Nodes application/json → Move to Documents folder application/pdf → Move to PDFs folder image/jpeg → Move to Images folder (Easily customizable to support additional types like PNG, DOCX, etc.) 📂 Move Files to Designated Folders: Uses Google Drive API to relocate each file to its proper location. 🔁 Loop Returns for Next File After each move, the loop picks the next file in queue. Key Features ⚙️ Google Drive API v3 Integration 🔐 OAuth2 for secure access 📄 MIME-type–based routing logic 🔁 Batch-safe with looping logic ✅ File properties are preserved 🔄 Auto-removal from source after sorting Required Integration Google Drive (OAuth2) Use Cases Auto-organize client uploads Separate scanned PDFs, images, or forms Route invoices, receipts, or contracts into folders Automatically sort uploaded assignments or resources Maintain structured cloud storage without manual intervention Why Use This Template? ✅ No-code deployment ✅ Saves hours of manual work ✅ Works across teams, departments, or shared Drives ✅ Easy to expand with more file types or routing rules ✅ Keeps your Drive clean, fast, and organized