Telegram TRIGGER
New Updates (Instant)
- Trigger
- Instant
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Telegram account, configure the source, and choose the webhook where your backend receives events.
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 deployed = await pd.triggers.deploy({
id: "telegram_bot_api-new-updates",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
telegram_bot_api: { authProvisionId: "apn_xxxxxxx" },
updateTypes: ["Update Types"],
},
webhookUrl: "https://example.com/webhooks/telegram-bot-api",
})
console.log(deployed.id)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
-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-new-updates",
"webhook_url": "https://example.com/webhooks/telegram-bot-api",
"configured_props": {
"telegram_bot_api": { "authProvisionId": "apn_xxxxxxx" },
"updateTypes": ["Update Types"]
}
}'MCP servers expose Telegram actions as on-demand tools.
New Updates (Instant) is an event source, so your application deploys it
with the Connect SDK or API and then either receives each event at a
webhook URL or retrieves events on demand with the trigger events API.MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.
SCHEMA
Configuration
These inputs define which events the source watches. Dynamic options are loaded from the connected account.
| Property | Type | Description |
|---|---|---|
updateTypes Update Types | string[] | Only emit events for the selected update types. Optional |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Telegram through Pipedream managed auth.
02
Deploy
Your backend deploys this source with that user's own configuration.
03
Webhook delivery
Every event is sent to the HTTP endpoint you choose when you deploy the source — as it happens.
OR
On-demand retrieval
No webhook required. Your app or agent can fetch recent events from the trigger events API.
REFERENCE
Trigger details
- Registry key
- telegram_bot_api-new-updates
- Version
- 0.1.8
- App
- Telegram
- Authentication
- API key
- Delivery
- Instant event
- Output
- Events emitted by Telegram.
- Source
- View on GitHub ↗