Telegram MTProto Client icon

Telegram MTProto Client

Use Telegram Client API with MTProto protocol

Actions13

Overview

This node enables interaction with Telegram using the MTProto protocol via a Telegram client API. Specifically, the Join Chat operation allows the user to join a Telegram chat or channel by providing its identifier (ID or username). This is useful for automating membership management in Telegram groups or channels, such as joining announcement channels, discussion groups, or any other Telegram community.

Practical examples include:

  • Automatically joining a specific Telegram channel when a workflow runs.
  • Managing memberships in multiple chats programmatically.
  • Integrating Telegram group joining as part of a larger automation process.

Properties

Name Meaning
Chat ID The unique identifier or username of the chat or channel to join. Examples: @username or -100xxxx.

Output

The output JSON object contains:

Field Description
success Boolean indicating if the join operation succeeded (true).
joined Boolean confirming that the chat was joined (true).
chatId The chat ID or username that was joined.

Example output JSON:

{
  "success": true,
  "joined": true,
  "chatId": "@examplechannel"
}

Dependencies

  • Requires an active Telegram client API connection authenticated with valid credentials including session data, API ID, and API hash.
  • The node uses the Telegram MTProto protocol via a bundled Telegram client SDK.
  • No additional external services are required beyond Telegram itself.
  • Proper n8n credential configuration for Telegram client API access is necessary.

Troubleshooting

  • No credentials provided: The node will throw an error if the Telegram client API credentials are missing or invalid. Ensure credentials are correctly set up in n8n.
  • Invalid Chat ID: If the chat ID or username is incorrect or inaccessible, the join operation may fail. Verify the chat/channel identifier is correct and accessible by your Telegram account.
  • Connection issues: Network problems or Telegram server issues can cause connection failures. Check network connectivity and retry later.
  • Permission restrictions: Some channels may restrict who can join or require approval. The node cannot bypass such restrictions.
  • Error disconnecting client: Errors during client disconnection are logged but do not stop execution; these usually do not affect the main operation.

Links and References

Discussion