Telegram event

Node catalog Triggers

On this page

Receive bot events by webhook: messages, commands, buttons, payments and members.

Usage and specifics

The action uses the bot token; the trigger uses a separate webhook secret. Publish and configure the bot HTTPS webhook. chat_id identifies the target chat. Custom mode exposes Bot API methods and parameters.

Technical type : telegram_trigger. Runtime : nodulz.

Credentials and prerequisites

Telegram webhook (integration / telegram_webhook). Secret containing 1 to 256 letters, numbers, _ or -. Select the same credential in the trigger and setWebhook action.

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`rateLimitEnabled`	`boolean`	-	-
`rateLimitMax`	`number`	-	-; > 0
`rateLimitWindowMs`	`number`	-	-; > 0
`allowedIps`	`array`	-	-; max 256
`blockedIps`	`array`	-	-; max 256
`credentialId`	`string`	`""`	-
`events`	`array`	`[]`	-
`chatId`	`string`	`""`	-
`command`	`string`	`""`	-
`testPayload`	`string`	`""`	-

Configuration help

events Events: Empty: all received events. Also configure allowed_updates in setWebhook: chat_member, message_reaction and message_reaction_count require explicit selection and suitable Telegram permissions.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "events": [],
  "chatId": "",
  "command": "",
  "testPayload": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.