Handle repository access requests from a handoff
Keep a repository access request from getting lost in shift notes by sending it to Notis.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Access requests can sit in a handoff without reaching the person who manages repository permissions.
- Create a collaborator invitation from a clearly stated access request.
- Keep repository access requests close to the handoff that raised them.
- Reduce manual follow-up for routine collaboration requests.
Setup
Build it in a few focused steps.
- 1Connect 7shifts and GitHub once in the Notis portal.
- 2Create an automation in Automations > New Automation and give it a clear name.
- 3Tell Notis to add the named GitHub user as a collaborator on the repository specified in the handoff.
- 4Choose the webhook trigger and where run reports should go.
- 5Send one real access request to test the workflow.
Questions about this workflow
Will this grant access immediately?
GitHub may create an invitation that the user must accept. The repository owner must also have the required access to manage collaborators.
What should the handoff request include?
Include the repository owner and name, the GitHub username, and the requested access context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 7shifts to GitHub. A trigger fires from one place; an action lands in another.
7shifts 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.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
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.
7shifts 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.