--- title: "Telegram Integration" description: "Use Telegram bots to deliver alerts, documents, and media as part of operational workflows. 1 message trigger and 15 actions including text, audio, documents, photos, and location messages." url: https://flowrunner.ai/integrations/telegram date_modified: 2026-08-01T02:40:32-07:00 --- # Telegram [Communication](https://flowrunner.ai/integrations/category/communication-messaging) Use Telegram bots to deliver alerts, documents, and media as part of operational workflows. 1 message trigger and 15 actions including text, audio, documents, photos, and location messages. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 15 actions · Custom auth · available [Telegram website](https://telegram.org/) · Capability data verified 2026-08-04 1. Ops agent detects critical threshold breach in monitored metric 2. Agent sends structured alert to dedicated Telegram operations group 3. Alert includes threshold context, current value, and recommended action 4. Agent monitors group chat for response via On New Message 5. Agent acts on confirmed keywords from team response 6. High-impact actions confirmed with a second CONFIRM reply before execution ## What This Integration Enables Telegram integration gives agents a Telegram bot as an output and input channel. Agents send text messages, documents, photos, audio, and location data to Telegram chats and groups. The On New Message trigger activates workflows when messages arrive. For international teams and mobile-first operations, Telegram is a primary communication channel. ### Without FlowRunner **Desktop-only alerts**: Operations alerts require someone to be logged in to see and respond **No field document delivery**: Receiving supervisors wait for email or physically walk to a printer for labels **Separate document intake process**: Field teams scan documents and email them; someone monitors the inbox ### With FlowRunner **Mobile-first alert channel**: Critical ops alerts reach the team wherever they are, not just at their desks **Direct document delivery to phones**: ShipBob labels and reports sent directly to supervisor's phone via Send Document **Field document intake via Telegram**: Field teams drop scans in a Telegram chat; extraction and confirmation happen automatically ## Use Case Scenarios ### Operations Alert Channel An ops agent monitors critical system metrics. When a threshold is crossed, it sends a structured alert to a dedicated Telegram group used by the operations team: inventory below reorder point, payment system error, SLA at risk. The alert includes context and a recommended action. Team members respond in the group chat. The agent reads responses via On New Message and acts on keywords like "approved" or "investigate." ### Field Team Document Delivery A logistics agent processes warehouse receiving orders. When a WRO is confirmed and box labels are generated in ShipBob, the agent sends the label PDFs via Send Document to the receiving supervisor's Telegram. The supervisor receives and prints the labels from their phone. Document delivery to field staff does not require a desktop or email. ### Inbound Document Processing A field agent drops a scanned document in a Telegram chat. On New Message fires. The agent retrieves the file via Get File, passes it to Parseur for extraction, processes the extracted data, and sends a confirmation back in the same Telegram chat: "Document processed. \[N\] records extracted and added to the system." The field team has a complete document intake channel in their existing messaging app. ## Human-in-Loop Highlight When an agent sends a decision request via Telegram and receives a reply, it does not act on partial or ambiguous responses. It confirms the interpretation before proceeding: "You replied 'yes' to approve the shipment exception for Order #44221. Confirming: approve $340 replacement shipment to \[address\]. Reply CONFIRM to proceed." The human confirms explicitly. High-impact actions have a second confirmation step when operating through a conversational interface. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 15 actions ### Capabilities 15 - **Send Message** Sends a text message to a Telegram chat, group, or channel. Used for operational notifications and status updates. - **Send Document** Sends a file to a Telegram chat. Used to deliver reports, invoices, contracts, or any document that needs to reach a mobile recipient. - **Send Photo** Sends an image. Used for visual status updates, inspection photos, or image-based notifications. - **Send Audio** Sends an audio file. Used for voice memo delivery in workflows where audio content is generated or transferred. - **Send Location** Sends GPS coordinates. Used in logistics workflows: delivery location, warehouse coordinates, field team position. - **Send Sticker** Sends a Telegram sticker. Used for lightweight acknowledgment responses in bot interaction workflows. - **Edit Message Text** Modifies a previously sent message. Used to update a live status message as a workflow progresses rather than sending a new message for each update. - **Delete Message** Removes a sent message. Used in cleanup workflows after time-sensitive alerts are resolved. - **Forward Message** Forwards a message from one chat to another. Used in routing workflows where messages need to be redistributed. - **Get Chat Info** Retrieves metadata about a chat or group. Used in administrative and routing workflows. - **Get Chat Member** Returns information about a specific member of a chat. Used to verify membership before routing. - **Get Bot Info** Returns the bot's profile and configuration. Used in health monitoring workflows. - **Get File** Retrieves a file shared in a Telegram chat. Used when users share documents or images through Telegram that need to be processed by the workflow. - **Get Updates** Polls for new messages and events. Used in polling-based input workflows. - **Get Webhook Info** Returns the current webhook configuration. Used in administrative and debugging workflows. ## Triggers 1 triggers ### Event Triggers 1 - **On New Message** Fires when a new message arrives in a monitored Telegram chat. Used to kick off workflows based on inbound Telegram messages: a keyword triggers a specific response flow, a document drop triggers a processing workflow, a command message triggers an operational action. ## Frequently Asked Questions ### What can FlowRunner do with Telegram? FlowRunner agents can run Send Message, Send Photo, and Send Document in Telegram, plus 12 more actions. ### Does connecting Telegram to FlowRunner require OAuth? Telegram uses a custom authentication method to connect to FlowRunner. ### Can Telegram trigger a FlowRunner workflow automatically? Yes. Telegram supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Telegram?** This integration exposes Telegram to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/telegram. Site index: https://flowrunner.ai/llms.txt