data.telegram.chat.list
List TelegramChat rows for a bot (UUID-only) — pick a saved chat instead of pasting a -100… numeric chat id
List TelegramChat rows for a bot (UUID-only).
Inputs:
- bot_uuid: Owning TelegramBot UUID (required; FieldSource → data.telegram.bot.list)
- limit / offset: pagination (clamped by the engine)
Outputs (terminal state_data):
- items / count / total / limit / offset
- error: str | None (only on failure)
Overview
| Property | Value |
|---|---|
| Workflow type | Atomic |
| Library | App-telegram |
| Version | 1.0 |
Input Schema
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
bot_uuid | uuid | Yes | — | Owning TelegramBot UUID |
limit | integer | No | 50 | Page size — hard-capped by the engine |
offset | integer | No | 0 | Pagination offset |
Output Schema
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
items | list | Yes | — | — |
count | integer | Yes | — | — |
total | integer | Yes | — | — |
limit | integer | Yes | — | — |
offset | integer | Yes | — | — |
error | string | No | — | — |
error_type | string | No | — | — |
States
| State | Initial | Terminal | Success | Auto-advance | Description |
|---|---|---|---|---|---|
done | Yes | Yes | Yes | — | — |
API Usage
bash
POST /api/workflows/start
Content-Type: application/json
{
"workflow_type": "data.telegram.chat.list",
"initial_data": {
"bot_uuid": "value"
}
}