Actions72
- Messages Actions
- Bots Actions
- Updates Actions
- Chats Actions
- Get Chat
- Get Chat Administrators
- Get Chat Member
- Get Chat Member Count
- Leave Chat
- Set Chat Title
- Set Chat Description
- Set Chat Photo
- Delete Chat Photo
- Set Chat Permissions
- Export Chat Invite Link
- Create Chat Invite Link
- Edit Chat Invite Link
- Revoke Chat Invite Link
- Approve Chat Join Request
- Decline Chat Join Request
- Set Chat Administrator Custom Title
- Ban Chat Member
- Unban Chat Member
- Restrict Chat Member
- Promote Chat Member
- Set Chat Sticker Set
- Delete Chat Sticker Set
- Pin Chat Message
- Unpin Chat Message
- Unpin All Chat Messages
- Files Actions
- Inline Queries Actions
- Callback Queries Actions
Overview
This node integrates with the Telegram Bot API to perform various chat-related operations. Specifically, for the Chats resource and the Get Chat operation, it retrieves detailed information about a specific Telegram chat by its Chat ID. This is useful when you want to fetch metadata or status about a chat, such as group details, channel info, or private chat attributes.
Common scenarios include:
- Retrieving chat details to display or log information about a conversation.
- Using chat metadata to conditionally route messages or trigger workflows.
- Auditing or monitoring chat properties in Telegram bots.
Example: You have a Telegram bot that manages multiple group chats. Using this node, you can get the title, type, and other details of a particular group chat by providing its Chat ID.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier for the Telegram chat you want to retrieve information about. |
| Options | Additional options as a JSON object to customize the request (not used in Get Chat). |
Output
The output json field contains the full response from the Telegram Bot API's getChat method. This typically includes:
- Chat ID
- Type of chat (private, group, supergroup, channel)
- Title (for groups/channels)
- Username (if available)
- Description (if set)
- Other metadata like invite links, permissions, etc.
The structure directly reflects Telegram's chat object schema.
No binary data is output by this operation.
Dependencies
- Requires an active Telegram Bot API token credential configured in n8n.
- Requires a valid subscription and API key for the "N8N Tools API" service, which validates usage before forwarding requests to Telegram.
- The node uses HTTP POST requests to the N8N Tools API proxy endpoint, which then interacts with Telegram's API.
Troubleshooting
- Invalid subscription or API key error: If you see an error about invalid subscription or API key, verify your API credentials for the N8N Tools API service are correct and active.
- Unknown operation error: Ensure the operation parameter is correctly set to "getChat" for the Chats resource.
- Missing Chat ID: The Chat ID property is required; missing or incorrect IDs will cause errors.
- Telegram API errors: Errors returned from Telegram (e.g., chat not found) will be passed through. Check the Chat ID validity and bot permissions.