Record customer impact signals from Slack
Keep customer impact visible as a structured signal alongside your support work.
Trigger
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Action
Track events
Tool to track server-side customer events. Use when you have collected a batch of events and want to send them to Gleap via the /admin/track endpoint.
Why this helps
The effect an issue has on customers can fade from view once a technical fix takes over the conversation.
- Preserves customer impact for later review
- Adds a structured signal to issue discussions
- Helps keep the user effect alongside technical follow-up
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 record customer impact.
- 3Write one plain-language prompt asking Notis to track a Gleap event only when a channel message clearly describes customer impact, excluding unrelated or sensitive details.
- 4Select the Slack channel message trigger and a channel for run reports.
- 5Test with one real impact report and confirm the recorded event is relevant.
Questions about this workflow
What kind of message should be tracked?
Use the prompt to focus on clear statements about how a product issue affects customers.
Does the event replace a ticket?
No. Event tracking records a signal; a ticket can still be useful when the issue needs active investigation.
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.