How to Create a Telegram Bot with No Code — using BuildShip (2024)

# Why Telegram Bots Are the Ultimate Conversational Interface

Telegram has one of the cleanest and most developer-friendly bot platforms available today. With hundreds of millions of active users and rich client capabilities, bots on Telegram can handle everything from automated community moderation and customer support to personalized AI assistants and interactive games.

Traditionally, deploying a custom Telegram bot required configuring persistent servers or serverless webhook endpoints, managing SSL certificates, registering webhook URLs through Telegram's HTTP API, and manually handling JSON request parsing.

With BuildShip, you can build and launch a fully featured, AI-powered Telegram bot in minutes completely visually, without managing servers or writing boilerplate glue code.

# Step 1: Create Your Bot with BotFather

Every Telegram bot begins with @BotFather, Telegram's official bot creation tool:

1. Open Telegram and search for @BotFather (ensure it has the verified blue badge).
2. Send the /newbot command.
3. Choose a display name for your bot (e.g., My Assistant Bot).
4. Choose a unique username that ends in bot (e.g., my_assistant_robot).
5. BotFather will provide you with an HTTP API Token (format: 123456789:ABCdefGhIJKlmNoPQRsTUVwxyZ). Copy this token and store it securely—this key authenticates all requests to Telegram on behalf of your bot.

# Step 2: Configure the Telegram Bot Trigger in BuildShip

Now that you have your Bot API Token, head over to BuildShip:

1. Create a new workflow or remix the Telegram Bot Template.
2. Select the Telegram Bot Trigger as the entry point of your workflow.
3. Paste your Bot API Token into the trigger configuration.
4. When you ship or test the workflow, BuildShip automatically calls Telegram's setWebhook endpoint behind the scenes, routing all incoming user messages directly to your workflow execution environment.

Whenever a user sends a message, your workflow receives an event payload containing:

• chatId: The unique identifier for the user or group conversation.
• message: The raw text of the incoming message.
• from: Metadata about the sender (first name, username, user ID).

# Step 3: Injecting AI Intelligence with OpenAI

A standard chatbot that only responds with rigid regex rules feels robotic. By chaining an OpenAI GPT node, your bot gains natural language reasoning:

1. Add the OpenAI Text Generator node right after the Telegram trigger.
2. Connect the incoming message text to the prompt input.
3. Provide a custom systemPrompt defining your bot's behavior, tone, and constraints.

Because BuildShip supports dynamic expressions, you can also inject the user's name ({{trigger.from.first_name}}) into the prompt for a personalized greeting.

# Step 4: Dispatching Responses Back to Telegram

The final piece of the pipeline is sending the generated answer back to the user:

1. Add the Send Telegram Message node to the workflow.
2. Pass the chatId from the trigger into the chat_id field.
3. Pass the generated text output from the OpenAI node into the text field.
4. Set parse mode to Markdown or HTML if you want rich formatting like bold text, bullet points, or inline links.

Click Ship, and your bot is immediately live in Telegram! Open your bot's conversation in Telegram, send a message or /start, and watch the bot respond in real time.

# Expanding Your Bot: Memory, Tools, and Database Sync

Because BuildShip is an extensible backend builder, you aren't restricted to basic text replies:

• Conversational Memory: Connect a Firestore or Supabase node to store conversation history by chatId, allowing the bot to remember context across multiple messages.
• Audio & Media: Use Telegram's audio and photo action nodes to accept voice notes from users, transcribe them using Whisper, and send back audio responses.
• Webhook Integrations: Trigger backend actions like creating a Linear issue, submitting a form, or notifying your team in Slack based on user commands.

**Read the original tutorial on Medium →**