Telegram task webhooks in Deskgram 2
Send Deskgram 2 events to your CRM, HTTP handler or automation service. Choose the destination, events and JSON fields, then inspect delivery results and errors in the webhook log.
Telegram task webhooks in Deskgram 2
Send Deskgram 2 events to your CRM, HTTP handler or automation service. Choose the destination, events and JSON fields, then inspect delivery results and errors in the webhook log.
Download Deskgram 2 PlansModule settings
Open Settings → Webhooks or the standalone module. Set the endpoint URL, events, module filter and enabled state. Delivery uses POST JSON; timeout is 3–60 seconds, default 15. Add headers such as Authorization and a secret when needed. X-Deskgram-Signature uses HMAC-SHA256 over the exact body; the secret is also sent in x-secret and X-Deskgram-Webhook-Secret for compatibility, so use HTTPS for a live endpoint. task.completed, task.failed and task.cancelled come through the task manager. message.sent, message.failed and lead.reply_received currently come from spam_pm, not every module. A lead reply is an incoming message, not a purchase. Standard deskgram JSON has schema_version, event, occurred_at and source; task events include task with ID, module, status, account count, times, params, statistics and result. Private-message events contain module, task, account, lead and message; contact fields depend on available data. short_result, crm_lead and custom provide mapped fields; missing values are omitted.
Check before running
The test button sends webhook.test without task, lead or message, so mapped business fields may be absent. HTTP 2xx marks delivery success, not completed CRM processing. Other HTTP statuses or connection errors trigger up to 3 attempts with waits of 2 and 4 seconds. Automatic retries keep one X-Deskgram-Delivery-Id; the receiver must handle duplicates. Manual retry is available for error only, creates a new ID and applies current endpoint settings and mapping to the saved source event; the outgoing JSON may change. There is no durable queue or automatic continuation after restart, and exactly-once delivery is not guaranteed. The log shows pending, retrying, success or error, attempt count, last HTTP status, response, error and times. Details include source_payload and request_payload; responses are saved up to 2000 characters. Automatic attempts update one record, manual retry creates another. Test the receiver and then a real event in your own task; an endpoint test alone does not verify business-event generation. Use MCP to control tasks; webhooks send notifications outward.
Related tasks and guides
Choose a related task or open the detailed guide. Linked Russian guides are marked accordingly.
Control Deskgram 2 through MCP Support Compare software