Starts like a script.
Grows like a system.

TeleFlow keeps the first command simple and the grown bot explicit: typed handlers, dependency injection, generated metadata, state, callbacks, long polling, webhooks, and direct Telegram Bot API access.

Get started Начать на русском GitHub

Program.cs

builder.Services.AddTelegramBot(options =>
{
    options.Token = token;
});

builder.Services.AddLongPolling();
builder.Services.AddTelegramHandlersFromAssembly(
    typeof(Program).Assembly);

public sealed class StartHandler
{
    [Command("start")]
    public Task Handle(
        MessageContext ctx,
        CancellationToken ct)
    {
        return ctx.Message.AnswerAsync(
            "Hello from TeleFlow.");
    }
}

</div>

NuGet packages Telegram chat Architecture Roadmap

Choose your path

One documentation site for different levels

First bot

Build a minimal long polling bot, add handlers, and understand the basic TeleFlow application model.

Real workflow

Walk through a support desk bot with state, callbacks, DI services, and admin actions.

Enterprise shape

Review architecture, deployment, versioning, diagnostics, performance, and production checklist notes.

Framework principles

Convenient does not have to mean hidden

TeleFlow uses normal C# handlers and normal .NET dependency injection. The recommended path generates handler metadata at build time and fails clearly when generated registration is missing.

Generated handler registration Direct Telegram Bot API client State and wizard flows Errors and diagnostics

Documentation map

Read in English or Russian

English documentation

Getting started, fundamentals, features, transports, advanced topics, enterprise notes, and reference.

Русская документация

Те же разделы на русском: старт, routing, callbacks, state, transports, enterprise и roadmap.

FilesExpand file tree

index.md

Latest commit

History