Telegram ACTION
List Updates
Retrieves a list of updates from the Telegram server. See the docs for more information
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Telegram account once, then configure and run List Updates from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "telegram_bot_api-list-updates",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
telegram_bot_api: { authProvisionId: "apn_xxxxxxx" },
offset: "Start offset (Update ID)",
limit: 10,
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "telegram_bot_api-list-updates",
"configured_props": {
"telegram_bot_api": { "authProvisionId": "apn_xxxxxxx" },
"offset": "Start offset (Update ID)",
"limit": 10
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "telegram_bot_api",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "telegram_bot_api-list-updates",
arguments: {
offset: "Start offset (Update ID)",
limit: 10,
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
offset Start offset (Update ID) | string | Enter the update ID <1, last update ID> you want to list from. Note: you can use this field to set your pagination - map last update ID from the result and increase this value by one to get next page. Optional |
limit Limit | integer | Limits the number of updates to be retrieved <1-100>. Optional |
autoPaging Confirm processed requests by increasing the offset in the Telegram server [auto-paging] | boolean | Check if to increasing the offset for the next request automatically. Caution: updates listed with auto-paging can be listed only once. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- telegram_bot_api-list-updates
- Version
- 0.0.8
- App
- Telegram
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗