Start Linear projects with customer context
A new project is a good time to check what customers have already reported. Notis can search Gleap using the available project details.
Trigger
Project Created
Fires when a new Linear project is created. Covers projects in both public and private teams — polls with the connected user's token, so visibility matches what the connected user can see in Linear.
Action
Search for Tickets
Tool to search for tickets. Use when needing to find tickets based on search criteria.
Why this helps
New initiatives can begin without a clear picture of related customer feedback, causing teams to rediscover known needs.
- Bring existing feedback into project planning.
- Reduce duplicate discovery work across teams.
- Give project owners a practical starting point for customer context.
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 relevant to a newly created Linear project and report the evidence.
- 4Choose the Linear project created trigger and select where run reports should go.
- 5Test with one real project and review the findings.
Questions about this workflow
Does this guarantee the project has customer demand?
No. It surfaces potentially relevant Gleap tickets. Review the results to judge how closely they relate to the project.
What information can Notis use for the search?
Ask it to use available project details and explain when the project context is too sparse for a useful search.
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.