Actions33
- Chat Actions
- Custom Request Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
The node "Telegram CoPilot" integrates with the Telegram API to perform various Telegram-related actions programmatically. Specifically, for the Message resource and the Get Message Link Info operation, it retrieves detailed information about a Telegram message from a provided Telegram message URL.
This operation is useful when you have a Telegram message link (e.g., shared in chats or channels) and want to extract metadata or details about that message without manually opening Telegram. It can be used in automation workflows to analyze messages, track content, or trigger further actions based on message data.
Practical example:
You receive a Telegram message URL from a user or another system and want to fetch the message's content, sender info, or other metadata automatically within your workflow. Using this node operation, you input the URL, and it returns structured information about that message.
Properties
| Name | Meaning |
|---|---|
| Telegram Message URL | The full URL of the Telegram message to retrieve information about. Example: https://t.me/telepilotco/42 |
Output
The output is a JSON array where each item contains the response from the Telegram API for the requested message link info. The structure corresponds to the Telegram API's response for the getMessageLinkInfo method, which typically includes:
- Details about the message referenced by the URL, such as:
- Message ID
- Chat or channel information
- Sender information
- Message content and type
- Any associated media or attachments
No binary data output is indicated for this operation.
Dependencies
- Requires an active Telegram API credential configured in n8n, including necessary authentication tokens.
- Depends on the internal TelePilot client connection manager to handle Telegram API calls.
- The node expects the Telegram account to be logged in and authorized; otherwise, it will throw login-related errors.
- No external services beyond Telegram API are required.
Troubleshooting
Common issues:
- Not logged in: If the Telegram session is not authenticated, the node will fail with a message prompting to log in using the ChatTrigger node and follow the login guide.
- Invalid URL: Providing a malformed or incorrect Telegram message URL may cause the API call to fail or return empty results.
- Session closed or expired: If the Telegram client session has been closed or expired, the node will throw an error requiring re-login.
Error messages and resolutions:
"Please login: https://telepilot.co/login-howto": Indicates the Telegram session is not active. Resolve by performing login via the recommended ChatTrigger node and following the linked guide."A closed client cannot be reused, create a new Client": The session was terminated; mark the client as closed and re-login."Unauthorized": Authentication failed; re-authenticate the Telegram account.- Other Telegram API errors will be passed through; check the error message for specifics.
Links and References
- TelePilot Login Guide — Instructions for logging into Telegram via TelePilot nodes.
- Telegram API Documentation — Official Telegram API reference for methods like
getMessageLinkInfo.