LaneHub

Lanes

A lane = one Telegram bot identity + its own API key. Agents call /<lane>/send, /<lane>/messages and /<lane>/feed with header X-Bridge-Token: <lane API key>.

➕ Add lane

Bot token (from @BotFather) — the only required field

Title (optional)

Slug / URL path (optional)

Default chat ID (optional)

Before creating: in @BotFather run /newbot, then /setprivacy → Disable (otherwise the bot won't see group messages), then add the bot to your group or channel. The chat will then appear under “seen chats” — click it to set as default.

Team

Set the project chat once — every new lane (including ones members create themselves) inherits it. Then invite teammates: each gets portal credentials by email (or as a copy-paste text) and connects their own bot in the member portal at /portal.

Project chat

📧 Email (SMTP) for invitation emails

SMTP host

Port

User / login

Password

From address

STARTTLS enabled

Stored in the hub database (same protection level as bot tokens). Clearing the host falls back to HUB_SMTP_* env vars, if set.

Name (optional)

Feed — the whole chat

auto-refresh

Admin login

Lanes

Team

Feed — the whole chat