Add a GitHub reviewer collaborator when a Jira review ticket is created
You pull in an outside reviewer, then realize they cannot even open the repo. When a review ticket is created in Jira, Notis adds that reviewer as a GitHub collaborator with the right access, so they can start reading code immediately.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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
Reviewers get named on a ticket but lack repo access, so the review stalls before it starts while you scramble to grant them in.
- Reviewers get repo access the moment they are pulled in
- Reviews start on time instead of stalling on access requests
- One less scramble when you need a fast second opinion
Setup
Build it in a few focused steps.
- 1Connect Jira and GitHub to Notis once from the portal.
- 2Open Automations in the portal and select New Automation.
- 3Write the instruction: when a review ticket is created in Jira, add the named reviewer as a collaborator on the repository with review-level access.
- 4Choose the New Issue trigger from Jira and pick a channel for run reports.
- 5Create a test review ticket and confirm the collaborator is added.
Questions about this workflow
Can I control their permission level?
Yes. Your instruction can set the access level for organization-owned repositories.
What if they are already a collaborator?
GitHub updates their permission instead of adding a duplicate, and Notis reports the outcome.
How does Notis know the repo?
It reads the repository from the ticket based on your plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to GitHub. A trigger fires from one place; an action lands in another.
Jira triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
New Project
Triggered when a new project is added in Jira
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
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.
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.
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.
Jira and GitHub, 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 GitHub.