Forward Bug Recorder reports into Telegram for investigation
When the original report matters, put it directly in front of the people who can investigate. Notis can forward available error report context into Telegram.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Forward Message
Forward messages of any kind. service messages can't be forwarded.
Why this helps
Copying reports between monitoring and chat interrupts investigation and can leave the team without the original context.
- Bring the report context into the team's investigation conversation.
- Cut manual copy and paste during triage.
- Make it easier for the team to respond from the place they coordinate work.
Setup
Build it in a few focused steps.
- 1Connect Bug Recorder and Telegram once in the Notis portal.
- 2Create an automation in Automations, or tell Notis in plain language from any channel.
- 3In one instruction, ask Notis to forward the available report message to the Telegram chat used for investigation.
- 4Choose notis_webhook as the trigger and select where run reports should go.
- 5Test with one real report and confirm the source message is forwardable.
Questions about this workflow
Can every error report be forwarded as an original message?
Only if the webhook payload or available context contains a forwardable Telegram message. Bug Recorder trigger events are not listed, so the webhook must supply the needed report context.
Can the workflow add a short note with the forwarded report?
This action forwards a message. If a separate explanatory note is needed, use a text message action in another workflow.
Does forwarding copy the entire Bug Recorder history?
No. It forwards the available message context for the current webhook run.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bug Recorder to Telegram. A trigger fires from one place; an action lands in another.
Bug Recorder 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.
Bug Recorder 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.