Remove retracted BotPenguin updates from Telegram
When a source event explicitly withdraws a shared update, remove the corresponding bot message from Telegram so the team does not act on stale information.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Delete Message
Delete a message, including service messages, with certain limitations.
Why this helps
A correction can arrive after a team has already seen a Telegram update, leaving outdated guidance visible in the chat.
- Clear an explicitly retracted bot post from the chat.
- Reduce the chance of acting on an outdated customer update.
- Keep cleanup tied to a specific message reference in the webhook.
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 delete the identified Telegram bot message only when the BotPenguin webhook explicitly marks the shared update as retracted.
- 4Select the Notis webhook trigger and choose where run reports should go.
- 5Test with one real retraction payload and confirm the correct message is removed.
Questions about this workflow
Can Telegram delete any message?
Telegram deletion has limitations. The bot must have the necessary access, the message must be identifiable, and the platform must allow that deletion.
How does the workflow find the message?
The webhook must include a reference that identifies the Telegram chat and message. Without it, Notis cannot safely select a message to delete.
Will it delete a message for every correction?
Only if your instruction and payload clearly identify an explicit retraction. A correction that should remain visible should use an edit or follow-up message instead.
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.