Telegram

Telegram Bot API integration for sending and receiving messages through your bot

The Telegram integration lets your agents send and receive messages through a Telegram bot — direct messages with users, groups, and supergroups the bot has been added to. It's a credentials container that powers the participant dispatcher; no agent-facing tools are exposed yet.

Prerequisites

You need a Telegram bot token:

Open a chat with @BotFather on Telegram.
Run /newbot and follow the prompts to create a new bot.
Copy the token BotFather hands back (looks like 123456789:ABCdefGHI…).
To let the bot read group messages, add it to the group as an admin (or disable BotFather's privacy mode with /setprivacy).

Setup

Open Integrations and select Telegram.
Click Add Integration Config.
Give the config a display name (e.g., "Telegram — Support Bot").
Choose Bot Token and paste the token from BotFather.
Save the config.

Each Telegram bot supports exactly one webhook URL. Fruxon assigns one webhook per Telegram config — once the config is saved, Fruxon calls Telegram's setWebhook against your bot so inbound messages reach the dispatcher.

Channels

Telegram exposes a single channel descriptor:

Channel	Description
`chat`	A Telegram conversation — direct message with a person, or a group/supergroup the bot has been added to.

Chat addresses are numeric chat ids:

Positive for user DMs (e.g. 123456789).
Negative for legacy groups.
-100… for supergroups (e.g. -1001234567890).

@username strings aren't accepted by the Bot API for outbound sends — use the numeric id.

Bind participants to a Telegram channel under Network → Participants to let your agents send messages to a user or group.

Triggers

Trigger	Description
`telegram.message.received`	Fires when the bot receives a message — from a user DM, from a group it's an admin of, or from a supergroup. Requires the Telegram webhook to be registered against this tenant's Fruxon ingress.

The trigger payload includes the standard inbound-message fields (payload.text, payload.from, payload.from_name, payload.conversation_name, payload.conversation_address, payload.session_id, payload.event_type) plus Telegram-specific fields:

payload.message_attributes.chat_id — chat id (positive for user DMs, -100… for supergroups, negative for legacy groups).
payload.message_attributes.message_id — per-chat message id. Combine with chat_id to address the message later.

Available Tools

No tools yet. This integration currently exists as a credentials container for the outbound message dispatcher. Tool support (send message, get bot info, etc.) will land in a follow-up.