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 via the N8N Tools Telegram service, enabling automation workflows to interact with Telegram bots. Specifically, for the Bots resource and the Get Me operation, it retrieves information about the bot itself — essentially returning the bot's profile details as recognized by Telegram.
Common scenarios where this is useful include:
- Verifying the identity of the bot in an automated workflow.
- Fetching bot metadata to confirm correct bot configuration.
- Debugging or monitoring bot status within a larger automation process.
For example, after setting up a Telegram bot, you might use this node operation to confirm the bot’s username, ID, and other profile details before proceeding with sending messages or handling updates.
Properties
| Name | Meaning |
|---|---|
| Options | Additional options as a JSON object; can be used to pass extra parameters if supported. |
Note: For the Bots - Get Me operation, no specific input parameters beyond optional "Options" are required.
Output
The output is a JSON object containing the bot's profile information as returned by the Telegram Bot API's getMe method. This typically includes fields such as:
id: The unique identifier for the bot.is_bot: Boolean indicating that the user is a bot.first_name: The bot's first name.username: The bot's username.- Other optional fields like
can_join_groups,can_read_all_group_messages, etc., depending on the bot's permissions and Telegram API version.
The node outputs this data under the json property of each item.
No binary data output is involved in this operation.
Dependencies
- Requires an active Telegram Bot API token configured as credentials in n8n.
- Uses the N8N Tools API service for validation and proxying requests to Telegram.
- Requires network access to both the N8N Tools API endpoint and Telegram API endpoints.
- The node expects the user to have a valid subscription or API key for the N8N Tools API service.
Troubleshooting
- Invalid subscription or API key error: If the node throws an error related to invalid subscription or API key, verify that the API key credential is correctly set up and active.
- Network errors: Ensure that your n8n instance has internet access to reach the N8N Tools API and Telegram servers.
- Unexpected response or empty output: Confirm that the Telegram bot token is valid and that the bot exists.
- JSON parsing errors: When providing additional options, ensure the JSON syntax is correct.