Trigger Metronomes from inbound Telegram messages
/v1/metronomes/telegram/inboundWebhook endpoint for Telegram Bot API updates or normalized Telegram message payloads. Published workflows with Telegram trigger nodes match on their configured slash command and optional sender, chat, and message filters. If METRONOME_TELEGRAM_WEBHOOK_SECRET is configured, callers must provide the same value in the x-computer-agents-webhook-secret header or secret query parameter.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| secret | query | string | No | — |
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| x-computer-agents-webhook-secret | header | string | No | — |
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| message | object | No | Message text. |
| edited_message | object | No | — |
| channel_post | object | No | — |
| text | string | No | — |
| caption | string | No | — |
| chatId | string | No | — |
| fromUsername | string | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
| Field | Type | Required | Description |
|---|---|---|---|
| success | boolean | No | Whether the request succeeded. |
| object | string | No | — |
| matched_count | integer | No | — |
| data | object[] | No | — |