Overview
This node acts as a trigger for Telegram updates using the TelePilot API. It listens for various Telegram events (updates) and emits them as workflow triggers in n8n. This is useful for automating workflows based on real-time Telegram activity, such as new messages, chat updates, user status changes, or file downloads.
Common scenarios include:
- Triggering workflows when a new message arrives in a Telegram chat.
- Reacting to message edits or deletions.
- Monitoring chat title or photo changes.
- Responding to user status updates or group call events.
For example, you could use this node to automatically log new Telegram messages into a database or send notifications when specific chat events occur.
Properties
| Name | Meaning |
|---|---|
| Events | Select one or multiple Telegram update event types to listen for. Options include: |
| - "*" (all events) | |
| - NewMessage | |
| - MessageSendAcknowledged | |
| - MessageSendSucceeded | |
| - MessageSendFailed | |
| - MessageContent | |
| - MessageEdited | |
| - MessageIsPinned | |
| - MessageInteractionInfo | |
| - MessageContentOpened | |
| - MessageMentionRead | |
| - MessageUnreadReactions | |
| - MessageLiveLocationViewed | |
| - NewChat | |
| - ChatTitle Updated | |
| - ChatPhoto Updated | |
| - ChatPermissions Updated | |
| - ChatReadInbox | |
| - ChatReadOutbox | |
| - ChatActionBar | |
| - ChatAvailableReactions | |
| - ChatDraftMessage | |
| - ChatMessageSender | |
| - ChatMessageTtl | |
| - ChatNotificationSettings | |
| - ChatPendingJoinRequests | |
| - ChatReplyMarkup | |
| - ChatTheme | |
| - ChatVideoChat | |
| - ChatDefaultDisableNotification | |
| - ChatHasProtectedContent | |
| - ChatHasScheduledMessages | |
| - ChatIsBlocked | |
| - ChatIsMarkedAsUnread | |
| - ChatFilters | |
| - ChatOnlineMemberCount | |
| - Notification | |
| - NotificationGroup | |
| - ActiveNotifications | |
| - HavePendingNotifications | |
| - DeleteMessages | |
| - ChatAction | |
| - UserStatus | |
| - User | |
| - BasicGroup | |
| - Supergroup | |
| - SecretChat | |
| - UserFullInfo | |
| - BasicGroupFullInfo | |
| - SupergroupFullInfo | |
| - ServiceNotification | |
| - File | |
| - FileGenerationStart | |
| - FileGenerationStop | |
| - FileDownloads | |
| - FileAddedToDownloads | |
| - FileDownload | |
| - FileRemovedFromDownloads | |
| - Call | |
| - GroupCall | |
| - GroupCallParticipant | |
| - NewCallSignalingData | |
| - UserPrivacySettingRules | |
| - UnreadMessageCount | |
| - UnreadChatCount | |
| - Option | |
| - StickerSet | |
| - InstalledStickerSets | |
| - TrendingStickerSets | |
| - RecentStickers | |
| - FavoriteStickers | |
| - SavedAnimations | |
| - SavedNotificationSounds | |
| - SelectedBackground | |
| - ChatThemes | |
| - LanguagePackStrings | |
| - ConnectionState | |
| - TermsOfService | |
| - UsersNearby | |
| - AttachmentMenuBots | |
| - WebAppMessageSent | |
| - Reactions | |
| - DiceEmojis | |
| - AnimatedEmojiMessageClicked | |
| - AnimationSearchParameters | |
| - SuggestedActions | |
| - NewInlineQuery | |
| - NewChosenInlineResult | |
| - NewCallbackQuery | |
| - NewInlineCallbackQuery | |
| - NewShippingQuery | |
| - NewPreCheckoutQuery | |
| - NewCustomEvent | |
| - NewCustomQuery | |
| - Poll | |
| - PollAnswer | |
| - ChatMember | |
| - NewChatJoinRequest |
The default selected events are updateNewMessage and updateMessageContent.
Output
The node outputs JSON data representing the Telegram update event that triggered it. Each output item contains the full update object with all relevant details depending on the event type.
- The output JSON structure varies according to the event received but generally includes fields describing the event type, message content, chat information, user info, or other Telegram-specific data.
- The node does not output binary data.
Dependencies
- Requires an API key credential for the TelePilot Telegram API, including API ID, API hash, and phone number for authentication.
- Uses the TelePilot Node Connection Manager internally to manage client sessions and authentication.
- Requires network access to connect to the Telegram API via TelePilot.
- No additional environment variables are specified, but proper credential configuration in n8n is necessary.
Troubleshooting
- Not logged in error: If the Telegram account is not logged in, the node emits a message instructing to use a login node with phone number authentication first. Ensure the Telegram account credentials are correctly set up and authenticated.
- Timeout on manual trigger: When running the node manually, if no update is received within 30 seconds, the execution aborts with a timeout error. This is expected behavior; in active workflows, the node listens indefinitely.
- Connection errors: Network issues or invalid credentials may cause connection failures. Verify API credentials and network connectivity.
- No events received: Check that the selected events match the actual Telegram updates expected. Using "*" listens to all events.
Links and References
- TelePilot Login Guide — Instructions for authenticating your Telegram account with TelePilot.
- Telegram API documentation (general reference): https://core.telegram.org/api
- n8n Documentation on Trigger Nodes: https://docs.n8n.io/nodes/trigger-nodes/