Actions56
- 袙褏芯写 Actions
- 袚褉褍锌锌邪 Actions
- 袣芯薪褌邪泻褌 Actions
- 袩芯写邪褉芯泻 Actions
- 袩芯谢褜蟹芯胁邪褌械谢褜 Actions
- 袩芯谢褜蟹芯胁邪褌械谢褜褋泻懈泄 蟹邪锌褉芯褋 Actions
- 小芯芯斜褖械薪懈械 Actions
- 肖邪泄谢 Actions
- 效邪褌 Actions
- 袩芯谢褍褔懈褌褜 褋锌懈褋芯泻 锌邪锌芯泻
- 袪械写邪泻褌懈褉芯胁邪褌褜 锌邪锌泻褍
- 袛芯斜邪胁懈褌褜 褔邪褌 胁 锌邪锌泻褍
- 校写邪谢懈褌褜 褔邪褌 懈蟹 锌邪锌泻懈
- 袛芯斜邪胁懈褌褜 褍褔邪褋褌薪懈泻芯胁 胁 褔邪褌
- 袟邪泻褉褘褌褜 褔邪褌
- 袨褌泻褉褘褌褜 褔邪褌
- 袨褌屑械褌懈褌褜 褔邪褌 泻邪泻 薪械锌褉芯褔懈褌邪薪薪褘泄
- 袨褌锌褉邪胁懈褌褜 写械泄褋褌胁懈械 褔邪褌邪
- 袩芯懈褋泻 锌褍斜谢懈褔薪芯谐芯 褔邪褌邪 (锌芯 懈屑械薪懈 锌芯谢褜蟹芯胁邪褌械谢褟)
- 小芯蟹写邪褌褜 斜懈蟹薪械褋-褋褋褘谢泻褍 褔邪褌邪
- 校写邪谢懈褌褜 斜懈蟹薪械褋-褋褋褘谢泻褍 褔邪褌邪
- 袩芯懈褋泻 锌褍斜谢懈褔薪褘褏 褔邪褌芯胁 (袩芯懈褋泻 胁 懈屑械薪懈, 蟹邪谐芯谢芯胁泻械)
- 袩芯谢褍褔懈褌褜 懈薪褎芯褉屑邪褑懈褞 芯 褋褋褘谢泻械 锌褉懈谐谢邪褕械薪懈褟 胁 褔邪褌
- 袩芯谢褍褔懈褌褜 懈褋褌芯褉懈褞 褔邪褌邪
- 袩芯谢褍褔懈褌褜 锌谢邪褌薪褘械 锌芯褋褌褘 懈蟹 褔邪褌邪
- 袩芯谢褍褔懈褌褜 褍褔邪褋褌薪懈泻芯胁 褔邪褌邪, 锌褉懈褋芯械写懈薪懈胁褕懈褏褋褟 锌芯 褋褋褘谢泻械 锌褉懈谐谢邪褕械薪懈褟
- 袩芯谢褍褔懈褌褜 懈薪褎芯褉屑邪褑懈褞 芯 褔邪褌械
- 袩芯谢褍褔懈褌褜 褔邪褌褘
- 袩褉懈褋芯械写懈薪懈褌褜褋褟 泻 褔邪褌褍
- 小芯蟹写邪褌褜 褋褍锌械褉谐褉褍锌锌褍 懈谢懈 泻邪薪邪谢
- 校写邪谢懈褌褜 褔邪褌
- 袩芯谢褍褔懈褌褜 褋锌懈褋芯泻 斜懈蟹薪械褋-褋褋褘谢芯泻
- 袟胁械蟹写褘 Actions
- 袠褋褌芯褉懈懈 Actions
小芯芯斜褖械薪懈械 → 袩芯谢褍褔懈褌褜 褋褋褘谢泻褍 薪邪 褋芯芯斜褖械薪懈械
AI-generatedOverview
This node operation interacts with Telegram chats to retrieve the chat history. It allows users to specify a chat ID, an optional starting message ID, and a limit on the number of messages to fetch. This is useful for scenarios where you want to analyze or archive chat conversations, monitor chat activity, or integrate chat data into other workflows.
Use Case Examples
- Fetch the last 100 messages from a specific Telegram chat for analysis.
- Retrieve chat history starting from a particular message ID to continue processing from a known point.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the Telegram chat from which to retrieve the history. |
| From Message ID | The message ID from which to start retrieving the chat history (optional). |
| Limit | The maximum number of messages to retrieve from the chat history. |
Output
JSON
messages- An array of messages retrieved from the specified chat history.total_count- The total number of messages retrieved.
Dependencies
- Requires Telegram API credentials including API ID, API hash, and phone number for authentication.
Troubleshooting
- Ensure the Telegram account is logged in and the session is active; otherwise, the node will throw a login error.
- If the chat ID is invalid or the chat is not found, the node will throw an error indicating the chat was not found.
- If the Telegram API returns permission errors, ensure the account has the necessary rights to access the chat history.
Links
- TelePilot Login Guide - Instructions on how to log in and authenticate the Telegram account for this node.