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 My Name operation, it retrieves the current name of the bot as set in Telegram.
Common scenarios where this node is beneficial include:
- Automatically fetching and verifying the bot's display name within a workflow.
- Using the bot's name dynamically in messages or logs.
- Monitoring or auditing bot settings programmatically.
For example, a workflow could periodically check the bot's name to ensure it matches expected branding or update other systems with the current bot name.
Properties
| Name | Meaning |
|---|---|
| Options | Additional options as a JSON object. For the "Get My Name" operation, this can include an optional language_code to specify the language for the bot's name retrieval. |
Output
The node outputs a JSON object containing the response from the Telegram Bot API for the "Get My Name" operation. This typically includes the bot's name information, potentially localized according to the provided language code.
Example output structure (simplified):
{
"name": "BotDisplayName"
}
No binary data output is produced by this operation.
Dependencies
- Requires an active Telegram Bot API token configured as credentials in n8n.
- Uses the N8N Tools API service for validation before making Telegram API calls; thus, requires a valid subscription and API key for this service.
- The node expects proper configuration of these credentials within n8n to authenticate requests.
Troubleshooting
- Invalid subscription or API key error: If you receive an error indicating invalid subscription or API key, verify that your N8N Tools API credentials are correct and active.
- Unknown operation error: Ensure that the operation selected matches the resource; for example, "Get My Name" must be used with the "Bots" resource.
- Malformed JSON in Options: Since the "Options" property accepts JSON, ensure it is well-formed. Invalid JSON will cause parsing errors.
- API rate limits or connectivity issues: Network problems or Telegram API rate limits may cause failures; check network connectivity and consider retry logic.