Use this action to specify a url and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, an HTTPS POST request will be sent to the specified url, containing a JSON-serialized Update object (https://core.telegram.org/bots/api/#update). In case of an unsuccessful request, we will give up after a reasonable amount of attempts. Returns True on success. If you’d like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL, e.g. https://www.example.com/<token>. Since nobody else knows your bot’s token, you can be pretty sure it’s from Telegram.

​
Basic Parameters

ParameterDescription
Allowed UpdatesA comma-separated list of the update types you want your bot to receive. For example, specify: message, edited_channel_post, callback_query to only receive updates of these types. See Update (https://core.telegram.org/bots/api/#update) for a complete list of available update types. Specify an empty list to receive all updates regardless of type (default). If not specified, the previous setting will be used.
Please note that this parameter doesn’t affect updates created before the call to the setWebhook, so unwanted updates may be received for a short period of time.
Drop Pending UpdatesWhether to drop all pending updates. Any webhook events not yet sent will also be deleted.
Target URLHTTPS url to send updates to. Use an empty string to remove webhook integration.

​
Advanced Parameters

ParameterDescription
IP AddressThe fixed IP address which will be used to send webhook requests instead of the IP address resolved through DNS.
Max ConnectionsMaximum allowed number of simultaneous HTTPS connections to the webhook for update delivery, 1-100. Defaults to 40. Use lower values to limit the load on your bot’s server and higher values to increase your bot’s throughput.
Secret TokenA secret token to be sent in a header “X-Telegram-Bot-Api-Secret-Token” in every webhook request, 1-256 characters. Only characters A-Z, a-z, 0-9, _ and - are allowed. The header is useful to ensure that the request comes from a webhook set by you.

​
Example Output

{
	"ok": true,
	"result": true,
	"description": "Webhook was set"
}

​
Workflow Library Example

Set Webhook with Telegram and Send Results Via Email
Workflow LibraryPreview this Workflow on desktop