Instant GitHub Project Onboarding: Linked to Linear
Start a new project in Linear and Notis immediately creates a matching GitHub project, granting your team the exact access level they need without manual configuration.
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
Add or update team project permissions
Grants or updates a team's permissions ('read', 'write', or 'admin') for a specific project, which must exist within the specified organization and be linked to it.
Why this helps
New projects get created in Linear but the GitHub project setup gets forgotten or delayed. Teams end up tracking work in Linear while code lives orphaned in GitHub because nobody took time to set up access.
- Eliminate the forgotten GitHub project setup step
- Ensure team members have access on day one
- Reduce friction when starting new initiatives
- Keep project scope visible to engineers from the moment work begins
Setup
Build it in a few focused steps.
- 1Connect Linear and GitHub to Notis
- 2Create an automation: 'When a new Linear project is created, create a GitHub project and grant the project's team write permissions'
- 3Set trigger to 'Linear project created'
- 4Optionally customize: 'add the team's existing repository to the GitHub project automatically'
- 5Test by creating a new Linear project and verifying the GitHub project exists with team access
- 6Notis will report the GitHub project link so you can immediately share it
Questions about this workflow
How does Notis know which GitHub repositories to link?
You can specify in your automation prompt: 'add the frontend and backend repositories to the GitHub project' or 'ask me which repo when creating a new project'.
Can I control which team members get added?
Yes. Your prompt might say 'grant write access to engineers, read access to non-technical stakeholders' and Notis applies the right level based on roles.
What if team composition changes after the project is created?
Create a complementary automation for team updates: 'When a user is added to a Linear project, add them to the corresponding GitHub project with the same permissions'.
Is this only for new projects, or can I sync existing ones?
This automation triggers on new projects. For existing projects, run a one-time sync via Notis chat and it handles the whole backlog.
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.