Google Docs is where longer content gets written, and Telegram is a fast channel for sharing it with a chat or group. Connecting them in NoClick lets a workflow push doc content to Telegram and turn Telegram messages into document text. The Google Docs node creates documents and appends, inserts, or replaces text, while the Telegram node sends messages to chats and channels, copies and forwards messages, and reads chat information.
Yes. Use the Google Docs fetch-document operation to read the content, then use the Telegram send-message operation to deliver it to a chat or channel.
After the Google Docs node creates the document, pass its title and link into the Telegram send-message operation so a channel gets notified automatically.
Yes. When Telegram messages come into your workflow, use the Google Docs append-text operation to add each one to a document, building a running log.
The Telegram node uses a bot token from BotFather, and the bot must already be a member of any channel it posts to. Google Docs uses Google OAuth.
Telegram messages have a length cap, so for long documents, split the content into chunks in your workflow and call the send-message operation once per chunk.