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 Sarry
What does this workflow do? This workflow acts as the backend "brain" for a sophisticated AI Voice Interviewer. It receives a user's resume text and a target job description, then uses a Large Language Model (LLM) to conduct a realistic, voice-based interview. The workflow maintains conversation history to ask relevant follow-up questions, creating a dynamic and personalized interview practice experience. This template is designed to work with a simple HTML frontend that handles the voice-to-text and text-to-speech functionality. What services does this workflow use? Google Gemini:** This is the LLM used to generate intelligent interview questions. You can easily swap this out for other models like OpenAI. What credentials do you need to have? You will need one credential: A Google Gemini API Key. You can get one for free from the Google AI Studio. How to use this workflow This workflow is the backend and requires a frontend to interact with. Set up the Frontend: You can find the complete frontend code and setup instructions in this GitHub repository. Configure Credentials: In this n8n workflow, click on the "Google Gemini Chat Model" node and add your own Gemini API credential. Activate the Workflow: Make sure the workflow is saved and active. Connect Frontend to Backend: Click on the "Webhook" node and copy the Production URL. Paste this URL into the voice-interview.html page as instructed in the GitHub repository's README.md file. Start Interviewing: Fill out the form on the web page to begin your voice interview!
by KlickTipp
Community Node Disclaimer This workflow uses KlickTipp community nodes and works only on self-hosted n8n instances. Introduction Automate Eventbrite order and refund processing by syncing data directly to KlickTipp. Whenever a participant registers or requests a refund, their profile is updated with event details and tags—keeping your segmentation accurate and automated. Who’s it for Perfect for event organizers, digital marketers, and automation specialists using Eventbrite and KlickTipp who want to eliminate manual imports and keep contact data consistent. How it works Eventbrite Trigger captures order.placed and order.refunded events. Switch Node routes logic: 🟢 Order placed → Adds contact, fetches event data, and tags buyer. 🔴 Refunded → Adds refund tag and removes buyer tag. Enrichment stores event name, page URL, and end date in KlickTipp fields. Fee check applies extra segmentation for paid vs. free events. KlickTipp updates contacts automatically—no manual steps needed. Requirements Self-hosted n8n (community node support) Eventbrite** account (OAuth2) KlickTipp** account (API access) KlickTipp custom fields: Eventbrite | Event name Eventbrite | Start timestamp Eventbrite | Event page URL KlickTipp tags: Eventbrite | Buyer Eventbrite | Refundee Eventbrite | Registrant How to set up Connect accounts: Eventbrite (OAuth2) & KlickTipp (API). Map fields: Event name, date, and URL to KlickTipp custom fields. Update tag IDs: Replace with your own KlickTipp IDs. Test the flow: Place an order → verify tags → trigger a refund to test removal. > 💡 Tip: Enable auto tag removal in KlickTipp so Buyer tags are removed when Refundee tags are added. How to customize Adapt field mappings to match your KlickTipp setup. Adjust tag rules for different event types or ticket tiers. Extend for multiple events or recurring campaigns. Campaign expansion ideas Track attendance vs. no-shows using participation tags. Add VIP or ticket-type segmentation. Trigger follow-up automations for refundees or attendees. Connect to other tools for reminders, surveys, or upsells.
by System Admin
Tagged with: , , , ,
by System Admin
No description available
by System Admin
Tagged with: , , , ,
by Simos Mikelatos
Turn new Linear issues into automated AI coding sessions. When an issue is created, this workflow runs an AI coding agent (Claude Code, Cursor CLI, Gemini or Codex) on the task inside a CloudCLI cloud dev environment and posts the results back to Linear with a link to the live session so you can continue your work. How it works A Linear trigger fires on issue events and filters for newly created issues only. The issue title and description are composed into a prompt for the AI coding agent. CloudCLI runs the agent inside an isolated cloud container. The agent's output, VS Code and Cursor deep links, and an SSH resume command are posted back to Linear as a comment. Reviewers can open the environment in their preferred IDE or SSH in and run claude -r to resume the session from terminal. Set up steps Install the CloudCLI verified community node from the n8n nodes panel. Connect your Linear and CloudCLI API credentials. Select your target environment in the "Get Environment Details" node. Customize the prompt template in "Compose Agent Prompt" to match your codebase. How to customize Adjust the Linear Trigger's team filter or add an IF node to filter by label (e.g. auto-code). Enable "Create Pull Request" in the agent's options to auto-open a PR. Add a Slack node to notify your team when the agent completes. Replace the Linear trigger with Jira, GitHub Issues, or Asana.
by Simos Mikelatos
Turn new Jira tickets into automated AI coding sessions. When a ticket is created, this workflow runs an AI coding agent (Claude Code, Cursor CLI, or Codex) on the task inside a CloudCLI cloud dev environment and posts the results and the links to continue the AI coding session from mobile or an IDE, back to Jira. How it works A Jira trigger fires when a new issue is created. The ticket summary and description are composed into a prompt for the AI coding agent. CloudCLI runs the agent inside an isolated cloud container. The agent's output, VS Code and Cursor deep links, and an SSH resume command are posted back to Jira as a comment. Reviewers can open the environment in their preferred IDE or SSH in and run claude -r to resume the session from terminal. Set up steps Install the CloudCLI verified community node from the n8n nodes panel. Connect your Jira Cloud and CloudCLI API credentials. Select your target environment in the "Get Environment Details" node. Customize the prompt template in "Compose Agent Prompt" to match your codebase. Requirements Jira Cloud account CloudCLI account with API key (cloudcli.ai) A running CloudCLI environment with your repo cloned AI provider API key configured in your CloudCLI dashboard (e.g. Anthropic for Claude Code) How to customize Add an IF node to filter by label (e.g. auto-code) or issue type. Enable "Create Pull Request" in the agent's options to auto-open a PR. Add a Slack node to notify your team when the agent completes. Replace the Jira trigger with Linear, GitHub Issues, or Asana.
by System Admin
No description available
by System Admin
Tagged with: , , , ,