> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Send Telegram Message

Send a text message to a Telegram chat using a bot token. Supports Markdown formatting (bold, italic, code, links). Uses the same bot token configured for receiving Telegram messages. Ideal for: chat replies, alerts, notifications, automated responses to Telegram triggers.

![Send Telegram Message logo](https://ai-icon.b3.fun/logo/telegram-bot)
Catalog action Messaging telegram-bot

Send a text message to a Telegram chat using a bot token. Supports Markdown formatting (bold, italic, code, links). Uses the same bot token configured for receiving Telegram messages. Ideal for: chat replies, alerts, notifications, automated responses to Telegram triggers.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `send-telegram-message` |
| Category | Messaging |
| Connector | `telegram-bot` |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `messaging`, `telegram`, `notification`, `bot`, `chat`, `write` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `chatId` | `string \| number` | Yes | Telegram chat ID of a verified DM or group. |
| `text` | `string` | Yes | Message text to send. Supports Markdown: **bold**, _italic_, 'code', links \(max 4096 chars after HTML formatting\) |
| `disable_notification` | `boolean` | No | Send message silently \(no notification sound\) |
| `reply_to_message_id` | `string \| number` | No | Message ID to reply to \(creates a thread\) |
| `reply_markup` | `string` | No | JSON string for InlineKeyboardMarkup. Example: {"inline_keyboard":\[\[{"text":"Yes","callback_data":"yes"},{"text":"No","callback_data":"no"}\]\]} |
| `mode` | `string` | No | Action mode. "send" \(default\) sends a new message. "edit" edits an existing message \(requires message_id\). |
| `message_id` | `string \| number` | No | Message ID to edit \(required when mode is "edit"\) |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `messageId` | `number` | Yes | Unique message identifier of the sent message |
| `chatId` | `number` | Yes | Chat ID the message was sent to |

## Examples

**Workflow node**

```json
{
  "type": "send-telegram-message",
  "payload": {
    "chatId": "example-chatId",
    "text": "Workflow completed"
  },
  "children": [],
  "connector": {
    "type": "telegram-bot",
    "id": "conn_telegram_bot"
  }
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/send-telegram-message/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "chatId": "example-chatId",
    "text": "Workflow completed"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.