Appearance
Telegram
Send messages, manage groups, and build bots with the Telegram Bot API.
| Detail | Value |
|---|---|
| Category | Communication |
| Base URL | https://api.telegram.org/bot{bot_token} |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | telegram |
Using Telegram in a workflow
- Go to Connections and click New Connection.
- Pick Telegram from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST /sendMessage | Send a text message |
GET /getUpdates | Get incoming updates |
GET /getMe | Get bot information |
POST /sendPhoto | Send a photo |
POST /setWebhook | Set webhook URL for updates |
GET /getChat | Get chat information |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /sendMessage
Send a text message
| Detail | Value |
|---|---|
| Operation ID | messaging.sendMessage |
| Method | POST |
| Path | /sendMessage |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
chat_id | string |
text | string |
parse_mode | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Telegram connection from the Connection dropdown.
- In the Operation dropdown, select
messaging.sendMessage. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Telegram API reference.
GET /getUpdates
Get incoming updates
| Detail | Value |
|---|---|
| Operation ID | messaging.getUpdates |
| Method | GET |
| Path | /getUpdates |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
offset | query | integer | No |
limit | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Telegram connection from the Connection dropdown.
- In the Operation dropdown, select
messaging.getUpdates. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Telegram API reference.
GET /getMe
Get bot information
| Detail | Value |
|---|---|
| Operation ID | messaging.getMe |
| Method | GET |
| Path | /getMe |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Telegram connection from the Connection dropdown.
- In the Operation dropdown, select
messaging.getMe. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Telegram API reference.
POST /sendPhoto
Send a photo
| Detail | Value |
|---|---|
| Operation ID | messaging.sendPhoto |
| Method | POST |
| Path | /sendPhoto |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
chat_id | string |
photo | string |
caption | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Telegram connection from the Connection dropdown.
- In the Operation dropdown, select
messaging.sendPhoto. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Telegram API reference.
POST /setWebhook
Set webhook URL for updates
| Detail | Value |
|---|---|
| Operation ID | messaging.setWebhook |
| Method | POST |
| Path | /setWebhook |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
url | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Telegram connection from the Connection dropdown.
- In the Operation dropdown, select
messaging.setWebhook. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Telegram API reference.
GET /getChat
Get chat information
| Detail | Value |
|---|---|
| Operation ID | messaging.getChat |
| Method | GET |
| Path | /getChat |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
chat_id | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Telegram connection from the Connection dropdown.
- In the Operation dropdown, select
messaging.getChat. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Telegram API reference.