Route BotPenguin conversation files to Telegram
Give customer provided files a clear path to your team's Telegram chat. Notis can forward supported files included in the incoming webhook data.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Send Document
Send general files (documents) to a telegram chat using the bot api.
Why this helps
Documents shared in chatbot conversations may wait unnoticed while the team checks other channels for work.
- Bring incoming customer files to the team's attention.
- Add supplied conversation context so a file is easier to identify.
- Reduce manual checking across chatbot and team messaging tools.
Setup
Build it in a few focused steps.
- 1Connect BotPenguin and Telegram once in the Notis portal.
- 2Create an automation in Automations, or tell Notis from any channel to create it.
- 3In one instruction, ask Notis to send a document to Telegram when a BotPenguin webhook includes a supported file, with a factual note from the supplied context.
- 4Select the Notis webhook trigger and choose where run reports should go.
- 5Test with one real webhook file and confirm that Telegram receives the expected document.
Questions about this workflow
Does this workflow find documents in BotPenguin on its own?
No. It handles file data delivered to the Notis webhook. Configure BotPenguin to send the relevant event and file information.
Which files can be sent?
The Telegram action supports general files, but successful delivery depends on the file representation and access information in the webhook payload.
What happens when the file is missing or unusable?
The instruction should skip sending a document and report the issue through the selected run report channel.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BotPenguin to Telegram. A trigger fires from one place; an action lands in another.
BotPenguin triggers
Telegram actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Answer Callback Query
Use this method to send answers to callback queries sent from inline keyboards. the answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Message
Delete a message, including service messages, with certain limitations.
Edit Message
Edit text messages sent by the bot.
Export Chat Invite Link
Generate a new primary invite link for a chat; any previously generated primary link is revoked. the bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
Get Chat Administrators
Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots.
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Connect any two apps with Notis in the middle.
BotPenguin and Telegram, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Telegram.