Keep Botpress follow-up from getting lost in chat history
Get a manageable list of unresolved Botpress conversations to review, based on what the available history shows.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Send Message
Send a text message to a telegram chat using the bot api.
Why this helps
Unresolved requests can remain buried in conversation history while attention shifts to newer work.
- Surface unresolved conversations for human review.
- Include the reason each item appears to need follow-up.
- Avoid claiming a request is overdue without an established timing baseline.
Setup
Build it in a few focused steps.
- 1Connect Botpress and Telegram once in the Notis portal.
- 2Create an automation in Automations, or tell Notis in plain language from any channel.
- 3Describe the outcome: review available Botpress history for conversations that appear unresolved and send a concise follow-up list to Telegram.
- 4Choose a recurring Notis schedule and select where run reports should go.
- 5Test with one real history sample and verify each item still needs follow-up.
Questions about this workflow
Can it know how long a conversation has been waiting?
Only if timestamps are available in the Botpress information Notis can access. The workflow should not infer an age without that data.
Does this contact the Botpress user?
No. It sends a review list to Telegram using the Send Message action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botpress to Telegram. A trigger fires from one place; an action lands in another.
Botpress 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.
Botpress 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.