Connect duplicate Gleap tickets from Telegram reports
When a repeated issue is confirmed, let Notis link the two existing Gleap tickets.
Trigger
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Action
Link a Ticket
Tool to link a ticket. Use when you need to connect two existing tickets after confirming both IDs exist. Example: Link a duplicate issue ticket to its original.
Why this helps
Related reports can stay scattered across separate records, making investigation and status harder to follow.
- Keep related issue records connected.
- Make the original investigation easier to locate.
- Reduce repeated review of the same problem.
Setup
Build it in a few focused steps.
- 1Connect Telegram and Gleap to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to link Gleap tickets when Telegram reports identify a confirmed duplicate.
- 3Provide one plain-language instruction requiring Notis to confirm both ticket IDs before linking them.
- 4Select New Message Received and choose a channel for run reports.
- 5Test with a Telegram report that clearly identifies two existing Gleap tickets.
Questions about this workflow
Will this link tickets based on a guess?
The prompt should require confirmed ticket IDs and a clear duplicate relationship before linking.
Does this create a ticket for a new report?
No. This workflow links two existing tickets when the report provides enough evidence.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to Gleap. A trigger fires from one place; an action lands in another.
Telegram triggers
Gleap actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive a Ticket
Tool to archive a ticket. Use after confirming the ticket ID and that the ticket is resolved. Call when moving tickets to history.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a Collection
Tool to create a help center collection. Use when adding a new organizational grouping in your Help Center.
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Create a new chat message
Tool to create a new chat message. Use when sending a message in an active chat session.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Create a new team
Tool to create a new team. Use when you have team details ready and want to assign tickets among members.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Create a new ticket
Tool to create a new ticket. Use when you have ticket details ready to open a support ticket.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Delete a User from a Project
Tool to remove a user from a project. Use when you need to revoke a user's access by their ID.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Get a Checklist
Tool to retrieve a specific engagement checklist by its ID. Use after obtaining a valid checklistId.
Get a Collection
Tool to retrieve a help center collection by ID. Use when you need to fetch specific collection details by its ID.
Connect any two apps with Notis in the middle.
Telegram and Gleap, 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 Gleap.