Telegram Integration

Instant real-time webhook debugging

Configuration

Setup Guide

Forward every incoming webhook payload directly to your personal Telegram chat. Ideal for mobile debugging, CI/CD pipeline alerts, and rapid API testing without opening a desktop browser.

Start by messaging @BotFather on Telegram and run the /newbot command. Provide a public name like “WebhookLab Monitor” and a username ending in _bot, such as “wl_debug_assistant_bot”. Copy the generated HTTP API token (format: 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11). Next, locate your chat ID by sending a test message to @userinfobot or by checking the first payload from your webhook. Paste both the token and chat ID into the WebhookLab dashboard under Settings → Telegram Bridge. Enable “Forward Raw JSON” and “Parse Markdown” to format stack traces and request headers cleanly.

Use Cases

Configuration Examples

GitHub Push & PR Alerts

Route repository events to @wl_debug_assistant_bot with chat ID 892104337. WebhookLab automatically parses action, ref, and head_commit.id fields, sending a formatted message like “🟢 Push to main: 8f4a2c1 by @dev_marcus”. Configure rate limiting to 5 messages/minute to avoid Telegram API throttling.

Stripe Checkout & Payouts

Forward checkout.session.completed and payout.paid events to your team channel @logistics_ops_bot (ID: 104829192). Use the payload filter event.type == 'checkout.session.completed' and map data.object.amount_total to a bold inline notification. WebhookLab retries failed deliveries with exponential backoff up to 15 minutes.

Uptime & Error Tracking

Attach a cron-triggered webhook to your staging API endpoint. If the response status exceeds 299, WebhookLab pushes a red alert to your private chat with the full response.headers, latency_ms, and a truncated response.body. Set the bridge toggle to “Silent Mode” for off-hours notifications between 22:00 and 07:00 UTC.