Feature Request Tracking: Linear to GitHub Labels
A product manager creates a feature request in Linear public team and Notis immediately adds a feature-request label to the GitHub issue, making it easy for engineers to find all requests in one view.
Trigger
Public Team Issue Created
Fires when a new issue is created in a Linear *public* team. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_CREATED`.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Feature requests live in Linear but get lost in GitHub's huge backlog of issues and PRs. Engineers never see the requests because they're not labeled or organized, leading to duplicate effort or missed opportunities.
- Make all feature requests visible in GitHub without extra filtering steps
- Help engineers see the scope of requested work alongside the codebase
- Reduce duplicate feature implementation by making existing requests discoverable
- Organize backlog visually by marking all requests with a consistent label
Setup
Build it in a few focused steps.
- 1Connect Linear and GitHub to Notis
- 2Create an automation: 'When a feature request is created in a public Linear team, add a feature-request label to the corresponding GitHub issue'
- 3Customize the label name if your team uses a different convention: 'use the enhancement or requested-feature label'
- 4Set trigger to 'Linear public team issue created'
- 5Test by creating a feature request in Linear and verifying it's labeled in GitHub within seconds
- 6Your team can now filter GitHub issues by feature-request label to see all requests in one view
Questions about this workflow
How do I distinguish feature requests from bugs or tasks in Linear?
Use a Linear label or issue type called 'Feature Request'. Your automation prompt can say 'only label issues with the feature-request label in Linear'.
Can I use a different label name per team?
Yes. Your automation can map to different labels: 'if from the Product team, use product-request; if from Engineering, use technical-improvement'.
Should I also add priority as a label?
Absolutely. Your automation can add multiple labels: 'add feature-request label, plus add priority-high or priority-low based on the Linear priority'.
Can GitHub team members request features through this automation?
Yes, create a reverse automation: 'When a GitHub issue is labeled with feature-request, create a matching Linear issue'.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to GitHub. A trigger fires from one place; an action lands in another.
Linear triggers
GitHub actions
Comment Received Trigger
Triggered when a comment is received.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Issue Created Trigger
Triggered when a new issue is created.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
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).
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
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.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user's token.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Linear and GitHub. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.