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
The node interacts with the Telegram Bot API to perform various chat-related operations. Specifically, for the "Chats" resource and the "Decline Chat Join Request" operation, it allows a bot to decline a user's request to join a chat. This is useful in managing group or channel membership requests programmatically, such as automatically declining join requests based on custom criteria or workflows.
Practical examples:
- Automatically declining join requests from users who do not meet certain criteria.
- Integrating with external systems to moderate chat membership requests.
- Managing large groups by automating approval or decline of join requests.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier for the Telegram chat where the join request was made. |
| User ID | The unique identifier of the user whose join request is to be declined. |
| Options | Additional optional parameters as a JSON object to customize the operation's behavior. |
Output
The output is a JSON object representing the response from the Telegram Bot API for the decline join request action. It typically contains information about the success or failure of the operation.
No binary data output is involved in this operation.
Dependencies
- Requires an active Telegram Bot API token (provided via credentials).
- 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 requests to communicate with both the N8N Tools API and the Telegram Bot API.
Troubleshooting
- Invalid subscription or API key error: If the node throws an error indicating invalid subscription or API key, verify that the API key credential is correctly configured and active.
- Unknown operation error: Ensure the operation name matches exactly one of the supported operations; typos or unsupported operations will cause errors.
- Missing required parameters: The "Chat ID" and "User ID" are mandatory for this operation. Omitting them will result in errors.
- Telegram API errors: Errors returned from Telegram (e.g., insufficient permissions, invalid chat/user IDs) should be checked and resolved according to Telegram Bot API documentation.