Connect duplicate Gleap issues after triage
Keep duplicate reports connected after your team confirms the relationship.
Trigger
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
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 tickets can remain isolated, making it harder to see the full history and avoid parallel follow-up.
- Connects confirmed related issue records
- Keeps issue history easier to follow
- Reduces split follow-up across duplicate tickets
Setup
Build it in a few focused steps.
- 1Connect Slack and Gleap to Notis once in the portal.
- 2Create an automation or ask Notis conversationally to link confirmed duplicate issues.
- 3Use a plain-language prompt explaining that the team reacts only after confirming two Gleap tickets are duplicates, and instruct Notis to link those tickets.
- 4Select the Slack message reaction added trigger and a channel for run reports.
- 5Test with one Slack triage message containing two confirmed, valid Gleap ticket IDs.
Questions about this workflow
Can this decide by itself that tickets are duplicates?
The workflow should link tickets only after the team has confirmed the duplicate relationship and supplied or clearly identified both records.
What if a ticket ID is missing?
The prompt should direct Notis to report that the link could not be made and avoid guessing either ticket ID.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Slack to Gleap. A trigger fires from one place; an action lands in another.
Slack 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 Channel Created Trigger
Triggered when a new channel is created in Slack.
Create a new chat message
Tool to create a new chat message. Use when sending a message in an active chat session.
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Create a new team
Tool to create a new team. Use when you have team details ready and want to assign tickets among members.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
Create a new ticket
Tool to create a new ticket. Use when you have ticket details ready to open a support ticket.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
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.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
Get a Checklist
Tool to retrieve a specific engagement checklist by its ID. Use after obtaining a valid checklistId.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
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.
Slack 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.