Telegram bot starter template setup

Published 1 month ago

Created by

Victor Gold

Template description

Telegram Bot Starter template workflow

provides a foundational setup for creating powerful Telegram bots with n8n. It handles incoming messages, photos, files, and voice notes, making it an excellent starting point for developers looking to create bots for customer engagement, support, or interactive services.

Key Features:

Dynamic Message Handling: Respond to text messages, photos, files, and more.
Modular Design: Easily integrate additional workflows such as user registration, payment modules, or custom commands.
Error Handling: Ensure the bot gracefully manages errors and user inputs.

Who Can Use This Workflow?

Developers looking for a quick way to build and customize Telegram bots.
Businesses and service providers who need customer interaction automation.

Setup Instructions:

Replace Telegram credentials with your own API credentials.
Customize responses for different message types (text, photo, file).
If integrating with external services (like Google Sheets), update the necessary credentials and links.

Extensibility:

This workflow is the base for building any Telegram bot. Additional modules, such as a user registration module, payment integration, and user profile management, are available for easy connection to expand the bot’s functionality.

Use the Telegram user registration workflow →

UPDATES:

Aug 24:

Changed processing of system events: “new user” and ‘user who blocked bot’ events

Sep 24:

Improved message handler: Updated logic to handle various types of messages using Switch (text, photo, file, voice, and callback).
Payment processing: Added new nodes for sending invoices and handling payments via Telegram

Please reach out to Victor if you need further assistance with your n8n workflows and automations!

Share Template

More Building Blocks workflow templates

Creating an API endpoint

Task: Create a simple API endpoint using the Webhook and Respond to Webhook nodes Why: You can prototype or replace a backend process with a single workflow Main use cases: Replace backend logic with a workflow

Jonathan

Very quick quickstart

Want to learn the basics of n8n? Our comprehensive quick quickstart tutorial is here to guide you through the basics of n8n, step by step. Designed with beginners in mind, this tutorial provides a hands-on approach to learning n8n's basic functionalities.

Deborah

Pulling data from services that n8n doesn’t have a pre-built integration for

You still can use the app in a workflow even if we don’t have a node for that or the existing operation for that. With the HTTP Request node, it is possible to call any API point and use the incoming data in your workflow Main use cases: Connect with apps and services that n8n doesn’t have integration with Web scraping How it works This workflow can be divided into three branches, each serving a distinct purpose: 1.Splitting into Items (HTTP Request - Get Mock Albums): The workflow initiates with a manual trigger (On clicking 'execute'). It performs an HTTP request to retrieve mock albums data from "https://jsonplaceholder.typicode.com/albums." The obtained data is split into items using the Item Lists node, facilitating easier management. 2.Data Scraping (HTTP Request - Get Wikipedia Page and HTML Extract): Another branch of the workflow involves fetching a random Wikipedia page using an HTTP request to "https://en.wikipedia.org/wiki/Special:Random." The HTML Extract node extracts the article title from the fetched Wikipedia page. 3.Handling Pagination (The final branch deals with handling pagination for a GitHub API request): It sends an HTTP request to "https://api.github.com/users/that-one-tom/starred," with parameters like the page number and items per page dynamically set by the Set node. The workflow uses conditions (If - Are we finished?) to check if there are more pages to retrieve and increments the page number accordingly (Set - Increment Page). This process repeats until all pages are fetched, allowing for comprehensive data retrieval.