Actions33
- Chat Actions
- Custom Request Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node integrates with Telegram via the TelePilot API, enabling automation and interaction with Telegram user accounts and chats. It supports a wide range of Telegram operations such as managing users, chats, messages, files, groups, and login sessions.
Specifically, for the User resource and the Create New Secret Chat operation, the node creates a new secret chat with a specified user by their user ID. This is useful when you want to start an encrypted private conversation programmatically.
Common scenarios include:
- Automating the creation of secret chats for secure communication.
- Integrating Telegram messaging workflows into broader automation pipelines.
- Managing Telegram user interactions without manual intervention.
Example: Automatically create a secret chat with a user after they register on your platform, enabling secure direct messaging.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Telegram user with whom to create the new secret chat. |
Output
The output is a JSON array containing the result of the invoked Telegram API method. For the "Create New Secret Chat" operation, the output JSON corresponds to the response from the Telegram API's createNewSecretChat method, which typically includes details about the newly created secret chat (such as chat ID and related metadata).
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the TelePilot Telegram API.
- The node depends on the TelePilotNodeConnectionManager service to manage Telegram client sessions.
- Proper Telegram API credentials (API ID, API Hash, phone number) must be configured in n8n credentials.
- The user must be logged in via the TelePilot login process before performing operations.
Troubleshooting
- Error: "Please login" — Indicates that the Telegram session is not authenticated. Resolve by running the login operation first using the ChatTrigger node or the login commands described in the documentation.
- Session closed or terminated errors — The Telegram client session may have expired or been closed. Re-login is required.
- Unauthorized errors — Usually caused by invalid or expired credentials; re-authenticate.
- If the node throws errors related to missing or invalid user IDs, ensure the User ID property is correctly set and corresponds to a valid Telegram user.
- Network or API rate limits may cause intermittent failures; retry logic or error handling can help mitigate.
Links and References
- TelePilot Documentation — Guide for login and usage.
- Telegram API Documentation — Official Telegram API reference.
- n8n Documentation — General information on creating and using custom nodes.