Find customer reports linked to Linear issue updates
A change to a Linear issue can be a useful moment to check for related Gleap tickets and understand the customer context around the work.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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
Product updates can lose sight of the feedback that prompted them, leaving teams to search support history by hand.
- Surface related customer reports when an issue changes.
- Give product and support teams a shared starting point for follow-up.
- Cut down repeated manual ticket searches.
Setup
Build it in a few focused steps.
- 1Connect Linear and Gleap to Notis once in the portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, ask Notis to search Gleap for tickets related to the updated Linear issue and report the matches with context.
- 4Choose the Linear issue updated trigger and select where run reports should go.
- 5Test with one real issue update and review the search results.
Questions about this workflow
Will this workflow modify or link the tickets it finds?
No. It searches for tickets and reports the results. Linking tickets requires a separate action and instruction.
What should Notis search for?
Ask it to use available issue details such as the title, description, or relevant keywords, and to report uncertainty when matches are unclear.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Gleap. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
Create a new chat message
Tool to create a new chat message. Use when sending a message in an active chat session.
Issue Created Trigger
Triggered when a new issue is created.
Create a new team
Tool to create a new team. Use when you have team details ready and want to assign tickets among members.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Create a new ticket
Tool to create a new ticket. Use when you have ticket details ready to open a support ticket.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
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.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get a Checklist
Tool to retrieve a specific engagement checklist by its ID. Use after obtaining a valid checklistId.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
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.
Linear 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.