# Telegram - Workflow node | Docs - nodulz

Source: https://nodulz.com/docs/nodes/telegram

Language: en

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](/docs/credentials) (`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](/docs/credentials) 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

| Setting | Purpose and guidance |
| --- | --- |
| `webhookCredentialId`<br>Webhook secret | Select the same Telegram webhook credential in this trigger and the setWebhook action. The secret stays in the vault. |
| `files`<br>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.

```json
{
  "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](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)