Run Telegram Bot API methods: messages, media, buttons, groups, payments and bot management.
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. Runtime : nodulz.
Credentials and prerequisites
Telegram bot (integration / telegram). Bot token created with @BotFather. Enables Telegram Bot API requests.
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
credentialId
string
""
-
webhookCredentialId
string
""
-
operation
string
"sendMessage"
-
parameters
record
{}
-
files
string
"{}"
-
Configuration help
webhookCredentialId Webhook secret
Select the same Telegram webhook credential in this trigger and the setWebhook action. The secret stays in the vault.
files Files to upload (JSON)
Object keyed by field or attachment name: each entry contains filename, base64 and optionally mimeType. Use attach://name in media objects. For example, a photo entry with filename and base64 for sendPhoto. Otherwise, provide a URL or file_id in the media field. Combined maximum: 50 MiB.
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
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.
Run Telegram Bot API methods: messages, media, buttons, groups, payments and bot management.
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. Runtime :nodulz.Credentials and prerequisites
integration/telegram). Bot token created with @BotFather. Enables Telegram Bot API requests.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.
credentialIdstring""webhookCredentialIdstring""operationstring"sendMessage"parametersrecord{}filesstring"{}"Configuration help
webhookCredentialIdWebhook secret
filesFiles to upload (JSON)
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "credentialId": "", "operation": "sendMessage", "parameters": {}, "files": "{}" }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.
See also : Expressions and data, Executions, Node catalog.