Telegram Message Destination

When to use this destination type

Choose TELEGRAM_MESSAGE when the receiver target is Telegram Bot API sendMessage. Destinations are outbound delivery targets: they do not decide whether a source request should be accepted, and they do not own connection filters or transformations. They own where the final delivery goes and how FastHook should authenticate, pace, disable, and inspect that delivery.

A destination can be reused by multiple connections when several source branches should feed the same receiver. Reuse keeps receiver capacity, credentials, and attempt evidence attached to one destination id.

FastHook dashboard fields

In the dashboard, create a destination, set Destination Type to TELEGRAM_MESSAGE, then fill the fields below.

API config fields

The REST API stores destination-specific behavior under config. Use PATCH for focused edits and PUT only when your request contains the full config you want to keep.

{
  "name": "ops-telegram-alerts",
  "type": "TELEGRAM_MESSAGE",
  "config": {
    "chat_id": "@ops_alerts",
    "text_template": "FastHook event {{event_id}}\n{{payload}}",
    "parse_mode": null,
    "disable_web_page_preview": true,
    "disable_notification": false,
    "auth_type": "TELEGRAM_BOT_TOKEN",
    "auth": {
      "bot_token": "123456789:your-telegram-bot-token"
    },
    "rate_limit": 1,
    "rate_limit_period": "second"
  }
}

curl -X POST "https://api.fasthook.io/v1/destinations" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "ops-telegram-alerts",
  "type": "TELEGRAM_MESSAGE",
  "config": {
    "chat_id": "@ops_alerts",
    "text_template": "FastHook event {{event_id}}\n{{payload}}",
    "parse_mode": null,
    "disable_web_page_preview": true,
    "disable_notification": false,
    "auth_type": "TELEGRAM_BOT_TOKEN",
    "auth": {
      "bot_token": "123456789:your-telegram-bot-token"
    },
    "rate_limit": 1,
    "rate_limit_period": "second"
  }
}'

Authentication

Destination authentication is outbound. It helps the receiver trust or accept FastHook delivery, and it is separate from source authentication that verifies the original webhook producer.

• Telegram bot token from BotFather
• Bot membership in the target chat, group, supergroup, or channel

HTTP methods and rate limit

This destination type uses the methods below for delivery attempts. Rate limits apply at the destination boundary, so every connection that targets the same destination shares that capacity.

Rate limit: Locked to 1 request per second.

Delivery behavior

• FastHook renders Telegram message templates per delivery and calls Telegram Bot API sendMessage.
• For groups, supergroups, and channels, add the bot to the target chat before sending. For channels, make the bot an administrator that can post messages.
• Use numeric chat IDs for private groups and supergroups; public channels can use @channelusername.
• Telegram Bot API responses with ok: false are treated as failed delivery attempts even when Telegram returns HTTP 200.
• Telegram Message destinations are locked to 1 request per second to avoid message bursts.

Setup checklist

1. Create a bot in BotFather and copy the bot token.
2. Add the bot to the Telegram chat, group, supergroup, or channel that should receive messages.
3. For channels, make the bot an administrator with permission to post messages.
4. Create a FastHook destination and choose TELEGRAM_MESSAGE as the destination type.
5. Set Chat ID, Message text, optional parse mode, notification flags, and bot token.
6. Connect only Telegram-worthy events through filters before routing to the destination.

Troubleshooting

Related docs

• Destinations
• Telegram source type
• Filter and route events
• Control throughput
• Telegram Bot API sendMessage
• BotFather
• API reference