Smart Team Collaboration: Invite Contributors Automatically
Discussing a feature with a new contractor or partner in Linear? Notis watches for mentions and automatically invites them as a GitHub collaborator so they can access the repo.
Trigger
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).
Action
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.
Why this helps
Someone gets mentioned as joining the project in a Linear comment, but the GitHub invitation never happens. They ask for access separately or never get it, causing delays and frustration.
- Remove the step where someone has to manually send GitHub invitations
- Get contributors access immediately when they join the conversation
- Reduce onboarding friction and get people productive faster
- Keep team collaboration smooth across both tools
Setup
Build it in a few focused steps.
- 1Connect Linear and GitHub to Notis
- 2Create an automation: 'When a comment on a Linear issue mentions a GitHub username or email, send them an invitation to collaborate on the repository'
- 3Set trigger to 'Linear team comment created'
- 4Configure GitHub permission level in the prompt: 'grant write access' or 'grant read-only access'
- 5Test by commenting on a Linear issue with @newuser or their email and verify they receive a GitHub invitation
Questions about this workflow
How does Notis know which GitHub username to invite?
You can mention them by @username if you know their GitHub handle, or by email address. Notis looks both up and sends the right invitation.
What permission level should I grant by default?
Your prompt controls it: 'invite collaborators as maintainers' or 'invite contractors with read-only access'. Adjust based on role.
Can I prevent invitations for certain types of mentions?
Yes. Your automation might say 'only invite external emails, not internal team members' or 'only invite if they don't already have access'.
What if someone gets invited multiple times?
Notis is idempotent—inviting someone twice just confirms their existing access. GitHub silently ignores the second invitation.
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.