Skip to content
Proud to collaborate with Microsoft for Startups

telegram.bot.get-webhook-info ​

Read a bot's current webhook configuration via Telegram Bot API (getWebhookInfo). Pure read — no DB writes, no message transmission. Input takes bot_uuid; the token is resolved from the TelegramBot row internally.

Call Telegram getWebhookInfo for a bot identified by bot_uuid.

PENDING (auto_advance=execute) → COMPLETED with webhook config ↘ FAILED on any error

Single-responsibility: one API call, no DB writes, no transmission.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-telegram
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
bot_uuiduuidYes—UUID of the TelegramBot row whose token will be used to call getWebhookInfo. The workflow resolves bot_uuid → bot_token internally.
workflow_run_idstringNo—Engine-stamped parent run id (DAG step target)

Output Schema ​

FieldTypeRequiredDefaultDescription
urlstringYes—Currently registered webhook URL, or an empty string when the bot is in long-polling mode (no active webhook).
has_webhookbooleanYes—Convenience flag: True when url is non-empty (webhook mode active).
has_custom_certificatebooleanNo—True if a self-signed certificate was supplied for the webhook.
pending_update_countintegerNo—Number of updates awaiting delivery.
webhook_ipstringNo—Currently used webhook IP; None when not set (Telegram getWebhookInfo.ip_address).
last_error_dateintegerNo—Unix time of the most recent webhook delivery error; None if none.
last_error_messagestringNo—Human-readable description of the most recent webhook delivery error.
max_connectionsintegerNo—Maximum allowed number of simultaneous HTTPS connections to the webhook.
allowed_updatesjsonNo—List of update types the bot is subscribed to; None means all (except chat_member).
failure_reasonstringNo—Engine-stamped human-readable failure reason
failure_typestringNo—Engine-stamped failure category
failed_actionstringNo—Engine-stamped action that raised
failed_at_statestringNo—Engine-stamped state when the workflow failed
failed_stepstringNo—Engine-stamped step name (DAG path)
failed_layerstringNo—Engine-stamped layer index (DAG path)
errorstringNo—Engine-stamped exception message
error_typestringNo—Engine-stamped exception class name

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—executeRead webhook config via Telegram Bot API
completedNoYesYes—Webhook config captured
failedNoYesNo—getWebhookInfo failed

State Diagram ​

Transitions ​

FromActionToDescription
pendingexecutecompleted—
* (any state)failfailed—

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "telegram.bot.get-webhook-info",
  "initial_data": {
    "bot_uuid": "value"
  }
}