Telegram Group Insight Log

Monitor useful Telegram group messages, analyze them with AI, and append structured product/support insights to Google Sheets.

The user wants a practical group-monitoring workflow that turns Telegram community, support, or beta-test messages into an organized spreadsheet for review.

• Should the bot process only messages addressed to it, or every group message?
• What kinds of messages should be logged: product feedback, support issues, sales leads, moderation risks, or everything?
• Which spreadsheet columns should the team review later?
• Add the Telegram bot to the target group.
• If all group messages should be logged, disable privacy mode for the bot in BotFather.
• Connect Google Sheets, choose the spreadsheet and sheet tab, then map columns such as received_at, chat_title, sender_username, message_text, and ai_analysis.
• Review the AI prompt and tune the categories for the team's real workflow before using it in a busy group.

• Telegram group/supergroup MESSAGE trigger receives a group message
• Store message text, chat title, sender username, message id, and raw payload fields
• AI_ACTION analyzes the message for category, sentiment, priority, summary, and suggested action
• Google Sheets append-row module action writes the raw message and AI analysis to a spreadsheet
• Do not send a reply by default so normal group conversations are not spammed

Good to know

• Use trigger type MESSAGE with config.source.platform="telegram" and config.source.chatTypes=["group", "supergroup"].
• For group context as the main contact/session, set config.contextMapping from identities.chat.* so the contact is the group, not the sender user.
• If the workflow should catch every group message, set config.source.visibility="all" and disable Telegram BotFather privacy mode for the bot.
• If the workflow should process only addressed messages, set config.source.visibility="addressed" and let users mention the bot or use commands.
• Use the installed Google Sheets insert-row action through moduleActionRef when the Google Sheets module is installed.
• Keep spreadsheet, sheet tab, and final column selection in the module action form. The flow can provide semantic suggested fields that are mapped after setup.
• Do not reply to every group message unless the user explicitly asks for visible acknowledgements.

Keep in mind

• Do not use TELEGRAM_CHANNEL_POST, TELEGRAM_CHAT_MEMBER, CHAT_MEMBER, STARTING_STEP, or MESSAGE_LISTENER as trigger.type.
• Do not model the group sender user as the main contact when the requested workflow is group-level logging.
• Do not ask the user for spreadsheet IDs in chat when the Google Sheets module action form should handle setup.
• Do not add visible group acknowledgements by default; they create noise in busy chats.
• Do not claim every group message will be received unless privacy mode is disabled.